DeleteCustomLogSource
Removes a custom log source from Amazon Security Lake.
Request Syntax
DELETE /v1/logsources/custom?customSourceName=customSourceName
HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- customSourceName
-
The custom source name for the custom log source.
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"customDataLocation": "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.
- customDataLocation
-
The location of the partition in the Amazon S3 bucket for Security Lake.
Type: String
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
- BucketNotFoundException
-
Amazon Security Lake generally returns 404 errors if the requested object is missing from the bucket.
HTTP Status Code: 409
- ConflictSourceNamesException
-
There was a conflict when you attempted to modify a Security Lake source name.
HTTP Status Code: 400
- 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
- ValidationException
-
Your signing certificate could not be validated.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: