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

CreateDataLakeExceptionSubscription

Creates the specified notification subscription in Amazon Security Lake for the organization you specify. The notification subscription is created for exceptions that cannot be resolved by Security Lake automatically.

Request Syntax


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

{
   "exceptionTimeToLive": number,
   "notificationEndpoint": "string",
   "subscriptionProtocol": "string"
}

URI Request Parameters

The request does not use any URI parameters.

Request Body

The request accepts the following data in JSON format.

exceptionTimeToLive

The expiration period and time-to-live (TTL). It is the duration of time until which the exception message remains.

Type: Long

Valid Range: Minimum value of 1.

Required: No

notificationEndpoint

The AWS account where you want to receive exception notifications.

Type: String

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

Required: Yes

subscriptionProtocol

The subscription protocol to which exception notifications are posted.

Type: String

Pattern: ^[a-z\-]*$

Required: Yes

Response Syntax


HTTP/1.1 200

Response Elements

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

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

BadRequestException

The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.

HTTP Status Code: 400

ConflictException

Occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.

HTTP Status Code: 409

InternalServerException

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

HTTP Status Code: 500

ResourceNotFoundException

The resource could not be found.

HTTP Status Code: 404

ThrottlingException

The limit on the number of requests per second was exceeded.

HTTP Status Code: 429