Macie2 / Client / exceptions / UnprocessableEntityException

UnprocessableEntityException

class Macie2.Client.exceptions.UnprocessableEntityException

Provides information about an error that occurred due to an unprocessable entity.

Example

try:
  ...
except client.exceptions.UnprocessableEntityException as e:
  print(e.response)

response

The parsed error response. All exceptions have a top level Error key that provides normalized access to common exception atrributes. All other keys are specific to this service or exception class.

Syntax

{
    'message': 'string',
    'Error': {
        'Code': 'string',
        'Message': 'string'
    }
}

Structure

• (dict) –

  Provides information about an error that occurred due to an unprocessable entity.

  • message (string) –

    The type of error that occurred and prevented Amazon Macie from retrieving occurrences of sensitive data reported by the finding. Possible values are:

    • ACCOUNT_NOT_IN_ORGANIZATION - The affected account isn’t currently part of your organization. Or the account is part of your organization but Macie isn’t currently enabled for the account. You’re not allowed to access the affected S3 object by using Macie.

    • INVALID_CLASSIFICATION_RESULT - There isn’t a corresponding sensitive data discovery result for the finding. Or the corresponding sensitive data discovery result isn’t available in the current Amazon Web Services Region, is malformed or corrupted, or uses an unsupported storage format. Macie can’t verify the location of the sensitive data to retrieve.

    • INVALID_RESULT_SIGNATURE - The corresponding sensitive data discovery result is stored in an S3 object that wasn’t signed by Macie. Macie can’t verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can’t verify the location of the sensitive data to retrieve.

    • MEMBER_ROLE_TOO_PERMISSIVE - The trust or permissions policy for the IAM role in the affected member account doesn’t meet Macie requirements for restricting access to the role. Or the role’s trust policy doesn’t specify the correct external ID for your organization. Macie can’t assume the role to retrieve the sensitive data.

    • MISSING_GET_MEMBER_PERMISSION - You’re not allowed to retrieve information about the association between your account and the affected account. Macie can’t determine whether you’re allowed to access the affected S3 object as the delegated Macie administrator for the affected account.

    • OBJECT_EXCEEDS_SIZE_QUOTA - The storage size of the affected S3 object exceeds the size quota for retrieving occurrences of sensitive data from this type of file.

    • OBJECT_UNAVAILABLE - The affected S3 object isn’t available. The object was renamed, moved, deleted, or changed after Macie created the finding. Or the object is encrypted with an KMS key that’s currently disabled.

    • RESULT_NOT_SIGNED - The corresponding sensitive data discovery result is stored in an S3 object that hasn’t been signed. Macie can’t verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can’t verify the location of the sensitive data to retrieve.

    • ROLE_TOO_PERMISSIVE - Your account is configured to retrieve occurrences of sensitive data by using an IAM role whose trust or permissions policy doesn’t meet Macie requirements for restricting access to the role. Macie can’t assume the role to retrieve the sensitive data.

    • UNSUPPORTED_FINDING_TYPE - The specified finding isn’t a sensitive data finding.

    • UNSUPPORTED_OBJECT_TYPE - The affected S3 object uses a file or storage format that Macie doesn’t support for retrieving occurrences of sensitive data.

  • Error (dict) – Normalized access to common exception attributes.

    • Code (string) – An identifier specifying the exception type.

    • Message (string) – A descriptive message explaining why the exception occured.