DeleteAwsLogSource - Amazon Security Lake


Removes a natively supported AWS service as an Amazon Security Lake source. You can remove a source for one or more Regions. When you remove the source, Security Lake stops collecting data from that source in the specified Regions and accounts, and subscribers can no longer consume new data from the source. However, subscribers can still consume data that Security Lake collected from the source before removal.

You can choose any source type in any AWS Region for either accounts that are part of a trusted organization or standalone accounts.

Request Syntax

POST /v1/datalake/logsources/aws/delete HTTP/1.1 Content-type: application/json { "sources": [ { "accounts": [ "string" ], "regions": [ "string" ], "sourceName": "string", "sourceVersion": "string" } ] }

URI Request Parameters

The request does not use any URI parameters.

Request Body

The request accepts the following data in JSON format.


Specify the natively-supported AWS service to remove as a source in Security Lake.

Type: Array of AwsLogSourceConfiguration objects

Array Members: Minimum number of 1 item. Maximum number of 50 items.

Required: Yes

Response Syntax

HTTP/1.1 200 Content-type: application/json { "failed": [ "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.


Deletion of the AWS sources failed as the account is not a part of the organization.

Type: Array of strings

Length Constraints: Fixed length of 12.

Pattern: ^[0-9]{12}$


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


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


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

HTTP Status Code: 400


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


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

HTTP Status Code: 500


The resource could not be found.

HTTP Status Code: 404


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

HTTP Status Code: 429

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: