check_no_new_access
async
¶
check_no_new_access(
new_policy_document: AccessCheckPolicyDocument,
existing_policy_document: AccessCheckPolicyDocument,
policy_type: AccessCheckPolicyType,
*,
config_overrides: Optional[AsyncAccessAnalyzerClientConfig] = None,
) -> CheckNoNewAccessResponse
Checks whether new access is allowed for an updated policy when compared to the existing policy.
You can find examples for reference policies and learn how to set up and run a custom policy check for new access in the IAM Access Analyzer custom policy checks samples repository on GitHub. The reference policies in this repository are meant to be passed to the existingPolicyDocument request parameter.
Parameters:
-
new_policy_document(AccessCheckPolicyDocument) –The JSON policy document to use as the content for the updated policy.
-
existing_policy_document(AccessCheckPolicyDocument) –The JSON policy document to use as the content for the existing policy.
-
policy_type(AccessCheckPolicyType) –The type of policy to compare. Identity policies grant permissions to IAM principals. Identity policies include managed and inline policies for IAM roles, users, and groups.
Resource policies grant permissions on Amazon Web Services resources. Resource policies include trust policies for IAM roles and bucket policies for Amazon S3 buckets. You can provide a generic input such as identity policy or resource policy or a specific input such as managed policy or Amazon S3 bucket policy.
Raises:
-
AccessDeniedException–You do not have sufficient access to perform this action.
-
InternalServerException–Internal server error.
-
InvalidParameterException–The specified parameter is invalid.
-
ThrottlingException–Throttling limit exceeded error.
-
UnprocessableEntityException–The specified entity could not be processed.
-
ValidationException–Validation exception error.
-
UnknownServiceError–The service returned an error code this client does not model.