Request Syntax URI Request Parameters Request Body Response Syntax Response Elements Errors See Also

ListDatalakeExceptions

Lists the Amazon Security Lake exceptions that you can use to find the source of problems and fix them.

Request Syntax


POST /v1/datalake/exceptions HTTP/1.1
Content-type: application/json

{
   "maxFailures": number,
   "nextToken": "string",
   "regionSet": [ "string" ]
}

URI Request Parameters

The request does not use any URI parameters.

Request Body

The request accepts the following data in JSON format.

maxFailures

List the maximum number of failures in Security Lake.

Type: Integer

Required: No

nextToken

List if there are more results available. The value of nextToken is a unique pagination token for each page. Repeat the call using the returned token to retrieve the next page. Keep all other arguments unchanged.

Each pagination token expires after 24 hours. Using an expired pagination token will return an HTTP 400 InvalidToken error.

Type: String

Pattern: ^[\\\w\-_:/.@=+]*$

Required: No

regionSet

List the AWS Regions from which exceptions are retrieved.

Type: Array of strings

Required: No

Response Syntax


HTTP/1.1 200
Content-type: application/json

{
   "nextToken": "string",
   "nonRetryableFailures": [ 
      { 
         "failures": [ 
            { 
               "exceptionMessage": "string",
               "remediation": "string",
               "timestamp": number
            }
         ],
         "region": "string"
      }
   ]
}

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

nextToken

Each pagination token expires after 24 hours. Using an expired pagination token will return an HTTP 400 InvalidToken error.

Type: String

Pattern: ^[\\\w\-_:/.@=+]*$

nonRetryableFailures

Lists the failures that cannot be retried in the current Region.

Type: Array of FailuresResponse objects

Errors

For information about the errors that are common to all actions, see Common Errors.

AccessDeniedException

You do not have sufficient access to perform this action. Access denied errors appear when Amazon Security Lake explicitly or implicitly denies an authorization request. An explicit denial occurs when a policy contains a Deny statement for the specific AWS action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.

HTTP Status Code: 403

AccountNotFoundException

Amazon Security Lake cannot find an AWS account with the accountID that you specified, or the account whose credentials you used to make this request isn't a member of an organization.

HTTP Status Code: 403

InternalServerException

Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.

HTTP Status Code: 500

ValidationException

Your signing certificate could not be validated.

HTTP Status Code: 400