Amazon Security Lake API Guide
Amazon Security Lake API Guide
Amazon's trademarks and trade dress may not be used in connection with any product or service
that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any
manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are
the property of their respective owners, who may or may not be affiliated with, connected to, or
sponsored by Amazon.
Amazon Security Lake API Reference
Table of Contents
Welcome ........................................................................................................................................... 1
Actions .............................................................................................................................................. 2
CreateAwsLogSource .................................................................................................................................... 4
Request Syntax ........................................................................................................................................ 4
URI Request Parameters ........................................................................................................................ 4
Request Body ........................................................................................................................................... 4
Response Syntax ...................................................................................................................................... 5
Response Elements ................................................................................................................................. 5
Errors .......................................................................................................................................................... 5
See Also ..................................................................................................................................................... 7
CreateCustomLogSource ............................................................................................................................. 8
Request Syntax ........................................................................................................................................ 8
URI Request Parameters ........................................................................................................................ 8
Request Body ........................................................................................................................................... 8
Response Syntax ................................................................................................................................... 10
Response Elements ............................................................................................................................... 10
Errors ....................................................................................................................................................... 10
See Also .................................................................................................................................................. 12
CreateDataLake ........................................................................................................................................... 14
Request Syntax ...................................................................................................................................... 14
URI Request Parameters ...................................................................................................................... 15
Request Body ......................................................................................................................................... 15
Response Syntax ................................................................................................................................... 16
Response Elements ............................................................................................................................... 17
Errors ....................................................................................................................................................... 17
See Also .................................................................................................................................................. 19
CreateDataLakeExceptionSubscription ................................................................................................... 20
Request Syntax ...................................................................................................................................... 20
URI Request Parameters ...................................................................................................................... 20
Request Body ......................................................................................................................................... 20
Response Syntax ................................................................................................................................... 21
Response Elements ............................................................................................................................... 21
Errors ....................................................................................................................................................... 21
See Also .................................................................................................................................................. 23
CreateDataLakeOrganizationConfiguration .......................................................................................... 24
Request Syntax ...................................................................................................................................... 24
URI Request Parameters ...................................................................................................................... 24
Request Body ......................................................................................................................................... 24
Response Syntax ................................................................................................................................... 25
Response Elements ............................................................................................................................... 25
Errors ....................................................................................................................................................... 25
See Also .................................................................................................................................................. 27
CreateSubscriber ......................................................................................................................................... 28
Request Syntax ...................................................................................................................................... 28
URI Request Parameters ...................................................................................................................... 28
Request Body ......................................................................................................................................... 28
Response Syntax ................................................................................................................................... 30
Response Elements ............................................................................................................................... 30
Errors ....................................................................................................................................................... 31
See Also .................................................................................................................................................. 32
CreateSubscriberNotification ................................................................................................................... 34
Request Syntax ...................................................................................................................................... 34
URI Request Parameters ...................................................................................................................... 34
Request Body ......................................................................................................................................... 34
Response Syntax ................................................................................................................................... 35
Response Elements ............................................................................................................................... 35
Errors ....................................................................................................................................................... 35
See Also .................................................................................................................................................. 37
DeleteAwsLogSource ................................................................................................................................. 38
Request Syntax ...................................................................................................................................... 38
URI Request Parameters ...................................................................................................................... 38
Request Body ......................................................................................................................................... 38
Response Syntax ................................................................................................................................... 39
Response Elements ............................................................................................................................... 39
Errors ....................................................................................................................................................... 39
See Also .................................................................................................................................................. 41
DeleteCustomLogSource ........................................................................................................................... 42
Request Syntax ...................................................................................................................................... 42
URI Request Parameters ...................................................................................................................... 42
Request Body ......................................................................................................................................... 42
DeleteSubscriberNotification ................................................................................................................... 61
Request Syntax ...................................................................................................................................... 61
URI Request Parameters ...................................................................................................................... 61
Request Body ......................................................................................................................................... 61
Response Syntax ................................................................................................................................... 61
Response Elements ............................................................................................................................... 61
Errors ....................................................................................................................................................... 61
See Also .................................................................................................................................................. 63
DeregisterDataLakeDelegatedAdministrator ........................................................................................ 65
Request Syntax ...................................................................................................................................... 65
URI Request Parameters ...................................................................................................................... 65
Request Body ......................................................................................................................................... 65
Response Syntax ................................................................................................................................... 65
Response Elements ............................................................................................................................... 65
Errors ....................................................................................................................................................... 65
See Also .................................................................................................................................................. 67
GetDataLakeExceptionSubscription ........................................................................................................ 68
Request Syntax ...................................................................................................................................... 68
URI Request Parameters ...................................................................................................................... 68
Request Body ......................................................................................................................................... 68
Response Syntax ................................................................................................................................... 68
Response Elements ............................................................................................................................... 68
Errors ....................................................................................................................................................... 69
See Also .................................................................................................................................................. 71
GetDataLakeOrganizationConfiguration ................................................................................................ 72
Request Syntax ...................................................................................................................................... 72
URI Request Parameters ...................................................................................................................... 72
Request Body ......................................................................................................................................... 72
Response Syntax ................................................................................................................................... 72
Response Elements ............................................................................................................................... 72
Errors ....................................................................................................................................................... 73
See Also .................................................................................................................................................. 75
GetDataLakeSources .................................................................................................................................. 76
Request Syntax ...................................................................................................................................... 76
URI Request Parameters ...................................................................................................................... 76
Request Body ......................................................................................................................................... 76
Welcome
Amazon Security Lake is a fully managed security data lake service. You can use Security Lake to
automatically centralize security data from cloud, on-premises, and custom sources into a data lake
that's stored in your AWS account. AWS Organizations is an account management service that lets
you consolidate multiple AWS accounts into an organization that you create and centrally manage.
With Organizations, you can create member accounts and invite existing accounts to join your
organization. Security Lake helps you analyze security data for a more complete understanding of
your security posture across the entire organization. It can also help you improve the protection of
your workloads, applications, and data.
The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and you retain
ownership over your data.
Amazon Security Lake integrates with AWS CloudTrail, a service that provides a record of actions
taken by a user, role, or an AWS service. In Security Lake, CloudTrail captures API calls for Security
Lake as events. The calls captured include calls from the Security Lake console and code calls to the
Security Lake API operations. If you create a trail, you can enable continuous delivery of CloudTrail
events to an Amazon S3 bucket, including events for Security Lake. If you don't configure a trail,
you can still view the most recent events in the CloudTrail console in Event history. Using the
information collected by CloudTrail you can determine the request that was made to Security Lake,
the IP address from which the request was made, who made the request, when it was made, and
additional details. To learn more about Security Lake information in CloudTrail, see the Amazon
Security Lake User Guide.
Security Lake automates the collection of security-related log and event data from integrated AWS
services and third-party services. It also helps you manage the lifecycle of data with customizable
retention and replication settings. Security Lake converts ingested data into Apache Parquet
format and a standard open-source schema called the Open Cybersecurity Schema Framework
(OCSF).
Other AWS services and third-party services can subscribe to the data that's stored in Security Lake
for incident response and security data analytics.
Actions
The following actions are supported:
• CreateAwsLogSource
• CreateCustomLogSource
• CreateDataLake
• CreateDataLakeExceptionSubscription
• CreateDataLakeOrganizationConfiguration
• CreateSubscriber
• CreateSubscriberNotification
• DeleteAwsLogSource
• DeleteCustomLogSource
• DeleteDataLake
• DeleteDataLakeExceptionSubscription
• DeleteDataLakeOrganizationConfiguration
• DeleteSubscriber
• DeleteSubscriberNotification
• DeregisterDataLakeDelegatedAdministrator
• GetDataLakeExceptionSubscription
• GetDataLakeOrganizationConfiguration
• GetDataLakeSources
• GetSubscriber
• ListDataLakeExceptions
• ListDataLakes
• ListLogSources
• ListSubscribers
• ListTagsForResource
• RegisterDataLakeDelegatedAdministrator
• TagResource
• UntagResource
• UpdateDataLake
• UpdateDataLakeExceptionSubscription
• UpdateSubscriber
• UpdateSubscriberNotification
CreateAwsLogSource
Adds a natively supported AWS service as an Amazon Security Lake source. Enables source types
for member accounts in required AWS Regions, based on the parameters you specify. You can
choose any source type in any Region for either accounts that are part of a trusted organization or
standalone accounts. Once you add an AWS service as a source, Security Lake starts collecting logs
and events from it.
You can use this API only to enable natively supported AWS services as a source. Use
CreateCustomLogSource to enable data collection from a custom source.
Request Syntax
{
"sources": [
{
"accounts": [ "string" ],
"regions": [ "string" ],
"sourceName": "string",
"sourceVersion": "string"
}
]
}
Request Body
sources
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.
failed
Lists all accounts in which enabling a natively supported AWS service as a Security Lake source
failed. The failure occurred as these accounts are not part of an organization.
Pattern: [0-9]{12}
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CreateCustomLogSource
Adds a third-party custom source in Amazon Security Lake, from the AWS Region where you want
to create a custom source. Security Lake can collect logs and events from third-party custom
sources. After creating the appropriate IAM role to invoke AWS Glue crawler, use this API to add a
custom source name in Security Lake. This operation creates a partition in the Amazon S3 bucket
for Security Lake as the target location for log files from the custom source. In addition, this
operation also creates an associated AWS Glue table and an AWS Glue crawler.
Request Syntax
{
"configuration": {
"crawlerConfiguration": {
"roleArn": "string"
},
"providerIdentity": {
"externalId": "string",
"principal": "string"
}
},
"eventClasses": [ "string" ],
"sourceName": "string",
"sourceVersion": "string"
}
Request Body
configuration
Required: Yes
eventClasses
The Open Cybersecurity Schema Framework (OCSF) event classes which describes the type of
data that the custom source will send to Security Lake. For the list of supported event classes,
see the Amazon Security Lake User Guide.
Pattern: [A-Z\_0-9]*
Required: No
sourceName
Specify the name for a third-party custom source. This must be a Regionally unique value.
The sourceName you enter here, is used in the LogProviderRole name which follows
the convention AmazonSecurityLake-Provider-{name of the custom source}-
{region}. You must use a CustomLogSource name that is shorter than or equal to 20
characters. This ensures that the LogProviderRole name is below the 64 character limit.
Type: String
Pattern: [\w\-\_\:\.]*
Required: Yes
sourceVersion
Specify the source version for the third-party custom source, to limit log collection to a specific
version of custom data source.
Type: String
Pattern: [A-Za-z0-9\-\.\_]*
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"source": {
"attributes": {
"crawlerArn": "string",
"databaseArn": "string",
"tableArn": "string"
},
"provider": {
"location": "string",
"roleArn": "string"
},
"sourceName": "string",
"sourceVersion": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
source
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceType
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CreateDataLake
Initializes an Amazon Security Lake instance with the provided (or default) configuration. You
can enable Security Lake in AWS Regions with customized settings before enabling log collection
in Regions. To specify particular Regions, configure these Regions using the configurations
parameter. If you have already enabled Security Lake in a Region when you call this command, the
command will update the Region if you provide new configuration parameters. If you have not
already enabled Security Lake in the Region when you call this API, it will set up the data lake in
the Region with the specified configurations.
When you enable Security Lake, it starts ingesting security data after the CreateAwsLogSource
call and after you create subscribers using the CreateSubscriber API. This includes ingesting
security data from sources, storing data, and making data accessible to subscribers. Security Lake
also enables all the existing settings and resources that it stores or maintains for your AWS account
in the current Region, including security log and event data. For more information, see the Amazon
Security Lake User Guide.
Request Syntax
{
"configurations": [
{
"encryptionConfiguration": {
"kmsKeyId": "string"
},
"lifecycleConfiguration": {
"expiration": {
"days": number
},
"transitions": [
{
"days": number,
"storageClass": "string"
}
]
},
"region": "string",
"replicationConfiguration": {
"regions": [ "string" ],
"roleArn": "string"
}
}
],
"metaStoreManagerRoleArn": "string",
"tags": [
{
"key": "string",
"value": "string"
}
]
}
Request Body
configurations
Specify the Region or Regions that will contribute data to the rollup region.
Required: Yes
metaStoreManagerRoleArn
The Amazon Resource Name (ARN) used to create and update the AWS Glue table. This table
contains partitions generated by the ingestion and normalization of AWS log sources and
custom sources.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: Yes
tags
An array of objects, one for each tag to associate with the data lake configuration. For each tag,
you must specify both a tag key and a tag value. A tag value cannot be null, but it can be an
empty string.
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"dataLakes": [
{
"createStatus": "string",
"dataLakeArn": "string",
"encryptionConfiguration": {
"kmsKeyId": "string"
},
"lifecycleConfiguration": {
"expiration": {
"days": number
},
"transitions": [
{
"days": number,
"storageClass": "string"
}
]
},
"region": "string",
"replicationConfiguration": {
"regions": [ "string" ],
"roleArn": "string"
},
"s3BucketArn": "string",
"updateStatus": {
"exception": {
"code": "string",
"reason": "string"
},
"requestId": "string",
"status": "string"
}
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
dataLakes
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
BadRequestException
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
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
{
"exceptionTimeToLive": number,
"notificationEndpoint": "string",
"subscriptionProtocol": "string"
}
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
Required: No
notificationEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: Yes
subscriptionProtocol
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CreateDataLakeOrganizationConfiguration
Automatically enables Amazon Security Lake for new member accounts in your organization.
Security Lake is not automatically enabled for any existing member accounts in your organization.
This operation merges the new data lake organization configuration with the existing configuration
for Security Lake in your organization. If you want to create a new data lake organization
configuration, you must delete the existing one using DeleteDataLakeOrganizationConfiguration.
Request Syntax
{
"autoEnableNewAccount": [
{
"region": "string",
"sources": [
{
"sourceName": "string",
"sourceVersion": "string"
}
]
}
]
}
Request Body
The request accepts the following data in JSON format.
autoEnableNewAccount
Enable Security Lake with the specified configuration settings, to begin collecting security data
for new accounts in your organization.
Required: No
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CreateSubscriber
Creates a subscriber for accounts that are already enabled in Amazon Security Lake. You can create
a subscriber with access to data in the current AWS Region.
Request Syntax
{
"accessTypes": [ "string" ],
"sources": [
{ ... }
],
"subscriberDescription": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string",
"tags": [
{
"key": "string",
"value": "string"
}
]
}
Request Body
The request accepts the following data in JSON format.
accessTypes
Required: No
sources
The supported AWS services from which logs and events are collected. Security Lake supports
log and event collection for natively supported AWS services.
Required: Yes
subscriberDescription
Type: String
Pattern: [\\\w\s\-_:/,.@=+]*
Required: No
subscriberIdentity
Required: Yes
subscriberName
Type: String
Required: Yes
tags
An array of objects, one for each tag to associate with the subscriber. For each tag, you must
specify both a tag key and a tag value. A tag value cannot be null, but it can be an empty string.
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"subscriber": {
"accessTypes": [ "string" ],
"createdAt": "string",
"resourceShareArn": "string",
"resourceShareName": "string",
"roleArn": "string",
"s3BucketArn": "string",
"sources": [
{ ... }
],
"subscriberArn": "string",
"subscriberDescription": "string",
"subscriberEndpoint": "string",
"subscriberId": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string",
"subscriberStatus": "string",
"updatedAt": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
subscriber
Retrieve information about the subscriber created using the CreateSubscriber API.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CreateSubscriberNotification
Notifies the subscriber when new data is written to the data lake for the sources that the subscriber
consumes in Security Lake. You can create only one subscriber notification per subscriber.
Request Syntax
{
"configuration": { ... }
}
subscriberId
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
configuration
Specify the configuration using which you want to create the subscriber notification.
Note: This object is a Union. Only one member of this object can be specified or returned.
Required: Yes
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"subscriberEndpoint": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
subscriberEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
BadRequestException
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteAwsLogSource
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
{
"sources": [
{
"accounts": [ "string" ],
"regions": [ "string" ],
"sourceName": "string",
"sourceVersion": "string"
}
]
}
Request Body
sources
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.
failed
Deletion of the AWS sources failed as the account is not a part of the organization.
Pattern: [0-9]{12}
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteCustomLogSource
Removes a custom log source from Amazon Security Lake, to stop sending data from the custom
source to Security Lake.
Request Syntax
sourceName
The source name of custom log source that you want to delete.
Pattern: [\w\-\_\:\.]*
Required: Yes
sourceVersion
The source version for the third-party custom source. You can limit the custom source removal
to the specified source version.
Pattern: [A-Za-z0-9\-\.\_]*
Request Body
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
InternalServerException
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteDataLake
When you disable Amazon Security Lake from your account, Security Lake is disabled in all AWS
Regions and it stops collecting data from your sources. Also, this API automatically takes steps to
remove the account from Security Lake. However, Security Lake retains all of your existing settings
and the resources that it created in your AWS account in the current AWS Region.
The DeleteDataLake operation does not delete the data that is stored in your Amazon S3 bucket,
which is owned by your AWS account. For more information, see the Amazon Security Lake User
Guide.
Request Syntax
{
"regions": [ "string" ]
}
Request Body
regions
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
resourceType
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteDataLakeExceptionSubscription
Deletes the specified notification subscription in Amazon Security Lake for the organization you
specify.
Request Syntax
Request Body
The request does not have a request body.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteDataLakeOrganizationConfiguration
Turns off automatic enablement of Amazon Security Lake for member accounts that are added
to an organization in AWS Organizations. Only the delegated Security Lake administrator for an
organization can perform this operation. If the delegated Security Lake administrator performs this
operation, new member accounts won't automatically contribute data to the data lake.
Request Syntax
{
"autoEnableNewAccount": [
{
"region": "string",
"sources": [
{
"sourceName": "string",
"sourceVersion": "string"
}
]
}
]
}
Request Body
autoEnableNewAccount
Turns off automatic enablement of Security Lake for member accounts that are added to an
organization.
Required: No
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteSubscriber
Deletes the subscription permission and all notification settings for accounts that are already
enabled in Amazon Security Lake. When you run DeleteSubscriber, the subscriber will no
longer consume data from Security Lake and the subscriber is removed. This operation deletes the
subscriber and removes access to data in the current AWS Region.
Request Syntax
subscriberId
A value created by Security Lake that uniquely identifies your DeleteSubscriber API request.
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceName
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeleteSubscriberNotification
Deletes the specified subscription notification in Amazon Security Lake for the organization you
specify.
Request Syntax
subscriberId
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceName
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DeregisterDataLakeDelegatedAdministrator
Deletes the Amazon Security Lake delegated administrator account for the organization. This
API can only be called by the organization management account. The organization management
account cannot be the delegated administrator account.
Request Syntax
Request Body
The request does not have a request body.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
GetDataLakeExceptionSubscription
Retrieves the protocol and endpoint that were provided when subscribing to Amazon SNS topics
for exception notifications.
Request Syntax
Request Body
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"exceptionTimeToLive": number,
"notificationEndpoint": "string",
"subscriptionProtocol": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
exceptionTimeToLive
The expiration period and time-to-live (TTL). It is the duration of time until which the exception
message remains.
Type: Long
notificationEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
subscriptionProtocol
Type: String
Pattern: [a-z\-]*
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
serviceCode
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
GetDataLakeOrganizationConfiguration
Retrieves the configuration that will be automatically set up for accounts added to the organization
after the organization has onboarded to Amazon Security Lake. This API does not take input
parameters.
Request Syntax
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"autoEnableNewAccount": [
{
"region": "string",
"sources": [
{
"sourceName": "string",
"sourceVersion": "string"
}
]
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
autoEnableNewAccount
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
resourceType
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
GetDataLakeSources
Retrieves a snapshot of the current Region, including whether Amazon Security Lake is enabled for
those accounts and which sources Security Lake is collecting data from.
Request Syntax
{
"accounts": [ "string" ],
"maxResults": number,
"nextToken": "string"
}
Request Body
accounts
The AWS account ID for which a static snapshot of the current AWS Region, including enabled
accounts and log sources, is retrieved.
Pattern: [0-9]{12}
Required: No
maxResults
The maximum limit of accounts for which the static snapshot of the current Region, including
enabled accounts and log sources, is retrieved.
Type: Integer
Required: No
nextToken
Lists 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
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"dataLakeArn": "string",
"dataLakeSources": [
{
"account": "string",
"eventClasses": [ "string" ],
"sourceName": "string",
"sourceStatuses": [
{
"resource": "string",
"status": "string"
}
]
}
],
"nextToken": "string"
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
dataLakeArn
The Amazon Resource Name (ARN) created by you to provide to the subscriber. For more
information about ARNs and how to use them in policies, see the Amazon Security Lake User
Guide.
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
dataLakeSources
Lists 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
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceName
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
GetSubscriber
Retrieves the subscription information for the specified subscription ID. You can get information
about a specific subscriber.
Request Syntax
subscriberId
A value created by Amazon Security Lake that uniquely identifies your GetSubscriber API
request.
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"subscriber": {
"accessTypes": [ "string" ],
"createdAt": "string",
"resourceShareArn": "string",
"resourceShareName": "string",
"roleArn": "string",
"s3BucketArn": "string",
"sources": [
{ ... }
],
"subscriberArn": "string",
"subscriberDescription": "string",
"subscriberEndpoint": "string",
"subscriberId": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string",
"subscriberStatus": "string",
"updatedAt": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
subscriber
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
ListDataLakeExceptions
Lists the Amazon Security Lake exceptions that you can use to find the source of problems and fix
them.
Request Syntax
{
"maxResults": number,
"nextToken": "string",
"regions": [ "string" ]
}
Request Body
The request accepts the following data in JSON format.
maxResults
Type: Integer
Required: No
nextToken
Lists 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
Required: No
regions
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"exceptions": [
{
"exception": "string",
"region": "string",
"remediation": "string",
"timestamp": "string"
}
],
"nextToken": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
exceptions
Lists 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
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
BadRequestException
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
serviceCode
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
ListDataLakes
Retrieves the Amazon Security Lake configuration object for the specified AWS Regions. You can
use this operation to determine whether Security Lake is enabled for a Region.
Request Syntax
regions
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Request Body
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"dataLakes": [
{
"createStatus": "string",
"dataLakeArn": "string",
"encryptionConfiguration": {
"kmsKeyId": "string"
},
"lifecycleConfiguration": {
"expiration": {
"days": number
},
"transitions": [
{
"days": number,
"storageClass": "string"
}
]
},
"region": "string",
"replicationConfiguration": {
"regions": [ "string" ],
"roleArn": "string"
},
"s3BucketArn": "string",
"updateStatus": {
"exception": {
"code": "string",
"reason": "string"
},
"requestId": "string",
"status": "string"
}
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
dataLakes
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceName
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
ListLogSources
Retrieves the log sources.
Request Syntax
{
"accounts": [ "string" ],
"maxResults": number,
"nextToken": "string",
"regions": [ "string" ],
"sources": [
{ ... }
]
}
Request Body
accounts
The list of AWS accounts for which log sources are displayed.
Pattern: [0-9]{12}
Required: No
maxResults
The maximum number of accounts for which the log sources are displayed.
Type: Integer
Required: No
nextToken
If nextToken is returned, there are more results available. You can repeat the call using the
returned token to retrieve the next page.
Type: String
Required: No
regions
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: No
sources
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"nextToken": "string",
"sources": [
{
"account": "string",
"region": "string",
"sources": [
{ ... }
]
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
nextToken
If nextToken is returned, there are more results available. You can repeat the call using the
returned token to retrieve the next page.
Type: String
The list of log sources in your organization that send data to the data lake.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
ListSubscribers
Lists all subscribers for the specific Amazon Security Lake account ID. You can retrieve a list of
subscriptions associated with a specific organization or AWS account.
Request Syntax
maxResults
If nextToken is returned, there are more results available. You can repeat the call using the
returned token to retrieve the next page.
Request Body
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"nextToken": "string",
"subscribers": [
{
"accessTypes": [ "string" ],
"createdAt": "string",
"resourceShareArn": "string",
"resourceShareName": "string",
"roleArn": "string",
"s3BucketArn": "string",
"sources": [
{ ... }
],
"subscriberArn": "string",
"subscriberDescription": "string",
"subscriberEndpoint": "string",
"subscriberId": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string",
"subscriberStatus": "string",
"updatedAt": "string"
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
nextToken
If nextToken is returned, there are more results available. You can repeat the call using the
returned token to retrieve the next page.
Type: String
The subscribers available for the specified Security Lake account ID.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
ListTagsForResource
Retrieves the tags (keys and values) that are associated with an Amazon Security Lake resource: a
subscriber, or the data lake configuration for your AWS account in a particular AWS Region.
Request Syntax
resourceArn
The Amazon Resource Name (ARN) of the Amazon Security Lake resource for which you want to
retrieve the tags.
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"tags": [
{
"key": "string",
"value": "string"
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
tags
An array of objects, one for each tag (key and value) that’s associated with the Amazon Security
Lake resource.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
serviceCode
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
RegisterDataLakeDelegatedAdministrator
Designates the Amazon Security Lake delegated administrator account for the organization. This
API can only be called by the organization management account. The organization management
account cannot be the delegated administrator account.
Request Syntax
{
"accountId": "string"
}
Request Body
The request accepts the following data in JSON format.
accountId
Type: String
Pattern: [\\\w\-_:/.@=+]*
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
TagResource
Adds or updates one or more tags that are associated with an Amazon Security Lake resource: a
subscriber, or the data lake configuration for your AWS account in a particular AWS Region. A tag
is a label that you can define and associate with AWS resources. Each tag consists of a required
tag key and an associated tag value. A tag key is a general label that acts as a category for a
more specific tag value. A tag value acts as a descriptor for a tag key. Tags can help you identify,
categorize, and manage resources in different ways, such as by owner, environment, or other
criteria. For more information, see Tagging Amazon Security Lake resources in the Amazon Security
Lake User Guide.
Request Syntax
{
"tags": [
{
"key": "string",
"value": "string"
}
]
}
resourceArn
The Amazon Resource Name (ARN) of the Amazon Security Lake resource to add or update the
tags for.
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: Yes
Request Body
The request accepts the following data in JSON format.
tags
An array of objects, one for each tag (key and value) to associate with the Amazon Security Lake
resource. For each tag, you must specify both a tag key and a tag value. A tag value cannot be
null, but it can be an empty string.
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
BadRequestException
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
UntagResource
Removes one or more tags (keys and values) from an Amazon Security Lake resource: a subscriber,
or the data lake configuration for your AWS account in a particular AWS Region.
Request Syntax
resourceArn
The Amazon Resource Name (ARN) of the Amazon Security Lake resource to remove one or
more tags from.
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: Yes
tagKeys
A list of one or more tag keys. For each value in the list, specify the tag key for a tag to remove
from the Amazon Security Lake resource.
Required: Yes
Request Body
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
resourceType
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
UpdateDataLake
You can use UpdateDataLake to specify where to store your security data, how it should be
encrypted at rest and for how long. You can add a Rollup Region to consolidate data from multiple
AWS Regions, replace default encryption (SSE-S3) with Customer Manged Key, or specify transition
and expiration actions through storage Lifecycle management. The UpdateDataLake API works
as an "upsert" operation that performs an insert if the specified item or record does not exist, or
an update if it already exists. Security Lake securely stores your data at rest using AWS encryption
solutions. For more details, see Data protection in Amazon Security Lake.
For example, omitting the key encryptionConfiguration from a Region that is included in
an update call that currently uses KMS will leave that Region's KMS key in place, but specifying
encryptionConfiguration: {kmsKeyId: 'S3_MANAGED_KEY'} for that same Region will
reset the key to S3-managed.
For more details about lifecycle management and how to update retention settings for one or
more Regions after enabling Security Lake, see the Amazon Security Lake User Guide.
Request Syntax
{
"configurations": [
{
"encryptionConfiguration": {
"kmsKeyId": "string"
},
"lifecycleConfiguration": {
"expiration": {
"days": number
},
"transitions": [
{
"days": number,
"storageClass": "string"
}
]
},
"region": "string",
"replicationConfiguration": {
"regions": [ "string" ],
"roleArn": "string"
}
}
],
"metaStoreManagerRoleArn": "string"
}
Request Body
The request accepts the following data in JSON format.
configurations
Specifies the Region or Regions that will contribute data to the rollup region.
Required: Yes
metaStoreManagerRoleArn
The Amazon Resource Name (ARN) used to create and update the AWS Glue table. This table
contains partitions generated by the ingestion and normalization of AWS log sources and
custom sources.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"dataLakes": [
{
"createStatus": "string",
"dataLakeArn": "string",
"encryptionConfiguration": {
"kmsKeyId": "string"
},
"lifecycleConfiguration": {
"expiration": {
"days": number
},
"transitions": [
{
"days": number,
"storageClass": "string"
}
]
},
"region": "string",
"replicationConfiguration": {
"regions": [ "string" ],
"roleArn": "string"
},
"s3BucketArn": "string",
"updateStatus": {
"exception": {
"code": "string",
"reason": "string"
},
"requestId": "string",
"status": "string"
}
}
]
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
dataLakes
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
UpdateDataLakeExceptionSubscription
Updates the specified notification subscription in Amazon Security Lake for the organization you
specify.
Request Syntax
{
"exceptionTimeToLive": number,
"notificationEndpoint": "string",
"subscriptionProtocol": "string"
}
Request Body
The request accepts the following data in JSON format.
exceptionTimeToLive
The time-to-live (TTL) for the exception message to remain. It is the duration of time until
which the exception message remains.
Type: Long
Required: No
notificationEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: Yes
subscriptionProtocol
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
UpdateSubscriber
Updates an existing subscription for the given Amazon Security Lake account ID. You can update a
subscriber by changing the sources that the subscriber consumes data from.
Request Syntax
{
"sources": [
{ ... }
],
"subscriberDescription": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string"
}
subscriberId
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
sources
The supported AWS services from which logs and events are collected. For the list of supported
AWS services, see the Amazon Security Lake User Guide.
Required: No
subscriberDescription
Type: String
Pattern: [\\\w\s\-_:/,.@=+]*
Required: No
subscriberIdentity
Required: No
subscriberName
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: No
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"subscriber": {
"accessTypes": [ "string" ],
"createdAt": "string",
"resourceShareArn": "string",
"resourceShareName": "string",
"roleArn": "string",
"s3BucketArn": "string",
"sources": [
{ ... }
],
"subscriberArn": "string",
"subscriberDescription": "string",
"subscriberEndpoint": "string",
"subscriberId": "string",
"subscriberIdentity": {
"externalId": "string",
"principal": "string"
},
"subscriberName": "string",
"subscriberStatus": "string",
"updatedAt": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
subscriber
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
resourceName
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
UpdateSubscriberNotification
Updates an existing notification method for the subscription (SQS or HTTPs endpoint) or switches
the notification subscription endpoint for a subscriber.
Request Syntax
{
"configuration": { ... }
}
subscriberId
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
Request Body
configuration
Note: This object is a Union. Only one member of this object can be specified or returned.
Required: Yes
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"subscriberEndpoint": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
subscriberEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
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.
errorCode
A coded string to provide more information about the access denied exception. You can use
the error code to check the exception type.
BadRequestException
The request is malformed or contains an error such as an invalid parameter value or a missing
required parameter.
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.
resourceName
Internal service exceptions are sometimes caused by transient issues. Before you start
troubleshooting, perform the operation again.
quotaCode
That the rate of requests to Security Lake is exceeding the request quotas for your AWS
account.
retryAfterSeconds
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
Data Types
The Amazon Security Lake API contains several data types that various actions use. This section
describes each data type in detail.
Note
The order of each element in a data type structure is not guaranteed. Applications should
not assume a particular order.
• AwsIdentity
• AwsLogSourceConfiguration
• AwsLogSourceResource
• CustomLogSourceAttributes
• CustomLogSourceConfiguration
• CustomLogSourceCrawlerConfiguration
• CustomLogSourceProvider
• CustomLogSourceResource
• DataLakeAutoEnableNewAccountConfiguration
• DataLakeConfiguration
• DataLakeEncryptionConfiguration
• DataLakeException
• DataLakeLifecycleConfiguration
• DataLakeLifecycleExpiration
• DataLakeLifecycleTransition
• DataLakeReplicationConfiguration
• DataLakeResource
• DataLakeSource
• DataLakeSourceStatus
• DataLakeUpdateException
• DataLakeUpdateStatus
• HttpsNotificationConfiguration
• LogSource
• LogSourceResource
• NotificationConfiguration
• SqsNotificationConfiguration
• SubscriberResource
• Tag
AwsIdentity
The AWS identity.
Contents
externalId
The external ID used to establish trust relationship with the AWS identity.
Type: String
Pattern: [\w+=,.@:\/-]*
Required: Yes
principal
Type: String
Pattern: ([0-9]{12}|[a-z0-9\.\-]*\.(amazonaws|amazon)\.com)
Required: Yes
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
AwsLogSourceConfiguration
To add a natively-supported AWS service as a log source, use these parameters to specify the
configuration settings for the log source.
Contents
regions
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: Yes
sourceName
Type: String
Required: Yes
accounts
Specify the AWS account information where you want to enable Security Lake.
Pattern: [0-9]{12}
Required: No
sourceVersion
Type: String
Pattern: (latest|[0-9]\.[0-9])
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
AwsLogSourceResource
Amazon Security Lake can collect logs and events from natively-supported AWS services.
Contents
sourceName
The name for a AWS source. This must be a Regionally unique value.
Type: String
Required: No
sourceVersion
The version for a AWS source. This must be a Regionally unique value.
Type: String
Pattern: (latest|[0-9]\.[0-9])
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CustomLogSourceAttributes
The attributes of a third-party custom source.
Contents
crawlerArn
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: No
databaseArn
The ARN of the AWS Glue database where results are written, such as:
arn:aws:daylight:us-east-1::database/sometable/*.
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: No
tableArn
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CustomLogSourceConfiguration
The configuration used for the third-party custom source.
Contents
crawlerConfiguration
The configuration used for the Glue Crawler for a third-party custom source.
Required: Yes
providerIdentity
The identity of the log provider for the third-party custom source.
Required: Yes
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CustomLogSourceCrawlerConfiguration
The configuration used for the Glue Crawler for a third-party custom source.
Contents
roleArn
The Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role to
be used by the AWS Glue crawler. The recommended IAM policies are:
• The managed policy AWSGlueServiceRole
• A custom policy granting access to your Amazon S3 Data Lake
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: Yes
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CustomLogSourceProvider
The details of the log provider for a third-party custom source.
Contents
location
The location of the partition in the Amazon S3 bucket for Security Lake.
Type: String
Pattern: s3[an]?://[a-z0-9][\.\-a-z0-9]{1,61}[a-z0-9](/[^/].*)+
Required: No
roleArn
The ARN of the IAM role to be used by the entity putting logs into your custom source partition.
Security Lake will apply the correct access policies to this role, but you must first manually
create the trust policy for this role. The IAM role name must start with the text 'Security Lake'.
The IAM role must trust the logProviderAccountId to assume the role.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
CustomLogSourceResource
Amazon Security Lake can collect logs and events from third-party custom sources.
Contents
attributes
Required: No
provider
Required: No
sourceName
The name for a third-party custom source. This must be a Regionally unique value.
Type: String
Pattern: [\w\-\_\:\.]*
Required: No
sourceVersion
The version for a third-party custom source. This must be a Regionally unique value.
Type: String
Pattern: [A-Za-z0-9\-\.\_]*
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeAutoEnableNewAccountConfiguration
Automatically enable new organization accounts as member accounts from an Amazon Security
Lake administrator account.
Contents
region
Type: String
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: Yes
sources
Required: Yes
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeConfiguration
Provides details of Amazon Security Lake object.
Contents
region
Type: String
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: Yes
encryptionConfiguration
Required: No
lifecycleConfiguration
Required: No
replicationConfiguration
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeEncryptionConfiguration
Provides encryption details of Amazon Security Lake object.
Contents
kmsKeyId
The identifier of KMS encryption key used by Amazon Security Lake to encrypt the Security
Lake object.
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeException
The details for an Amazon Security Lake exception.
Contents
exception
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: No
region
Type: String
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: No
remediation
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: No
timestamp
This error can occur if you configure the wrong timestamp format, or if the subset of entries
used for validation had errors or missing values.
Type: Timestamp
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeLifecycleConfiguration
Provides lifecycle details of Amazon Security Lake object.
Contents
expiration
Required: No
transitions
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeLifecycleExpiration
Provide expiration lifecycle details of Amazon Security Lake object.
Contents
days
Number of days before data expires in the Amazon Security Lake object.
Type: Integer
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeLifecycleTransition
Provide transition lifecycle details of Amazon Security Lake object.
Contents
days
Number of days before data transitions to a different S3 Storage Class in the Amazon Security
Lake object.
Type: Integer
Required: No
storageClass
The range of storage classes that you can choose from based on the data access, resiliency, and
cost requirements of your workloads.
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeReplicationConfiguration
Provides replication details for objects stored in the Amazon Security Lake data lake.
Contents
regions
Specifies one or more centralized rollup Regions. The AWS Region specified in the region
parameter of the CreateDataLake or UpdateDataLake operations contributes data to the
rollup Region or Regions specified in this parameter.
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: No
roleArn
Replication settings for the Amazon S3 buckets. This parameter uses the AWS Identity and
Access Management (IAM) role you created that is managed by Security Lake, to ensure the
replication setting is correct.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeResource
Provides details of Amazon Security Lake object.
Contents
dataLakeArn
The Amazon Resource Name (ARN) created by you to provide to the subscriber. For more
information about ARNs and how to use them in policies, see the Amazon Security Lake User
Guide.
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: Yes
region
Type: String
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: Yes
createStatus
Retrieves the status of the CreateDatalake API call for an account in Amazon Security Lake.
Type: String
Required: No
encryptionConfiguration
Required: No
lifecycleConfiguration
Required: No
replicationConfiguration
Required: No
s3BucketArn
Type: String
Required: No
updateStatus
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeSource
Amazon Security Lake collects logs and events from supported AWS services and custom sources.
For the list of supported AWS services, see the Amazon Security Lake User Guide.
Contents
account
The ID of the Security Lake account for which logs are collected.
Type: String
Required: No
eventClasses
The Open Cybersecurity Schema Framework (OCSF) event classes describes the type of data
that the custom source will send to Security Lake. For the list of supported event classes, see
Supported OCSF Event classes in the Amazon Security Lake User Guide.
Pattern: [A-Z\_0-9]*
Required: No
sourceName
The supported AWS services from which logs and events are collected. Amazon Security Lake
supports log and event collection for natively supported AWS services.
Type: String
Required: No
sourceStatuses
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeSourceStatus
Retrieves the Logs status for the Amazon Security Lake account.
Contents
resource
Defines path the stored logs are available which has information on your systems, applications,
and services.
Type: String
Required: No
status
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeUpdateException
The details of the last UpdateDataLake or DeleteDataLake API request which failed.
Contents
code
The reason code for the exception of the last UpdateDataLake or DeleteDataLake API
request.
Type: String
Required: No
reason
The reason for the exception of the last UpdateDataLakeor DeleteDataLake API request.
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
DataLakeUpdateStatus
The status of the last UpdateDataLake or DeleteDataLake API request. This is set to Completed
after the configuration is updated, or removed if deletion of the data lake is successful.
Contents
exception
The details of the last UpdateDataLakeor DeleteDataLake API request which failed.
Required: No
requestId
Type: String
Required: No
status
The status of the last UpdateDataLake or DeleteDataLake API request that was requested.
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
HttpsNotificationConfiguration
The configurations used for HTTPS subscriber notification.
Contents
endpoint
The subscription endpoint in Security Lake. If you prefer notification with an HTTPs endpoint,
populate this field.
Type: String
Pattern: https?://.+
Required: Yes
targetRoleArn
The Amazon Resource Name (ARN) of the EventBridge API destinations IAM role that you
created. For more information about ARNs and how to use them in policies, see Managing data
access and AWS Managed Policies in the Amazon Security Lake User Guide.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: Yes
authorizationApiKeyName
Type: String
Required: No
authorizationApiKeyValue
Type: String
Required: No
httpMethod
Type: String
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
LogSource
Amazon Security Lake can collect logs and events from natively-supported AWS services and
custom sources.
Contents
account
Type: String
Pattern: [0-9]{12}
Required: No
region
Type: String
Pattern: (us(-gov)?|af|ap|ca|eu|me|sa)-(central|north|(north(?:east|west))|
south|south(?:east|west)|east|west)-\d+
Required: No
sources
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
LogSourceResource
The supported source types from which logs and events are collected in Amazon Security Lake. For
a list of supported AWS services, see the Amazon Security Lake User Guide.
Contents
Important
This data type is a UNION, so only one of the following members can be specified when
used or returned.
awsLogSource
Amazon Security Lake supports log and event collection for natively supported AWS services.
For more information, see the Amazon Security Lake User Guide.
Required: No
customLogSource
Amazon Security Lake supports custom source types. For more information, see the Amazon
Security Lake User Guide.
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
NotificationConfiguration
Specify the configurations you want to use for subscriber notification to notify the subscriber when
new data is written to the data lake for sources that the subscriber consumes in Security Lake.
Contents
Important
This data type is a UNION, so only one of the following members can be specified when
used or returned.
httpsNotificationConfiguration
Required: No
sqsNotificationConfiguration
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
SqsNotificationConfiguration
The configurations used for EventBridge subscriber notification.
Contents
The members of this exception structure are context-dependent.
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
SubscriberResource
Provides details about the Amazon Security Lake account subscription. Subscribers are notified of
new objects for a source as the data is written to your Amazon S3 bucket for Security Lake.
Contents
sources
Amazon Security Lake supports log and event collection for natively supported AWS services.
For more information, see the Amazon Security Lake User Guide.
Required: Yes
subscriberArn
Type: String
Pattern: arn:(aws|aws-us-gov|aws-cn):securitylake:[A-Za-z0-9_/.\-]{0,63}:
[A-Za-z0-9_/.\-]{0,63}:[A-Za-z0-9][A-Za-z0-9_/.\-]{0,127}
Required: Yes
subscriberId
Type: String
Pattern: [a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}
Required: Yes
subscriberIdentity
Required: Yes
subscriberName
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: Yes
accessTypes
You can choose to notify subscribers of new objects with an Amazon Simple Queue Service
(Amazon SQS) queue or through messaging to an HTTPS endpoint provided by the subscriber.
Subscribers can consume data by directly querying AWS Lake Formation tables in your
Amazon S3 bucket through services like Amazon Athena. This subscription type is defined as
LAKEFORMATION.
Required: No
createdAt
Type: Timestamp
Required: No
resourceShareArn
The Amazon Resource Name (ARN) which uniquely defines the AWS RAM resource share. Before
accepting the RAM resource share invitation, you can view details related to the RAM resource
share.
This field is available only for Lake Formation subscribers created after March 8, 2023.
Type: String
Required: No
resourceShareName
Type: String
Pattern: LakeFormation(?:-V[0-9]+)-([a-zA-Z0-9]+)-([\\\w\-_:/.@=+]*)
Required: No
roleArn
The Amazon Resource Name (ARN) specifying the role of the subscriber.
Type: String
Pattern: arn:(aws[a-zA-Z-]*)?:iam::\d{12}:role/?[a-zA-Z_0-9+=,.@\-_/]+
Required: No
s3BucketArn
Type: String
Required: No
subscriberDescription
The subscriber descriptions for a subscriber account. The description for a subscriber includes
subscriberName, accountID, externalID, and subscriberId.
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: No
subscriberEndpoint
Type: String
Pattern: [\\\w\-_:/.@=+]*
Required: No
subscriberStatus
Type: String
Required: No
updatedAt
The date and time when the subscriber was last updated.
Type: Timestamp
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
Tag
A tag is a label that you can define and associate with AWS resources, including certain types of
Amazon Security Lake resources. Tags can help you identify, categorize, and manage resources in
different ways, such as by owner, environment, or other criteria. You can associate tags with the
following types of Security Lake resources: subscribers, and the data lake configuration for your
AWS account in individual AWS Regions.
A resource can have up to 50 tags. Each tag consists of a required tag key and an associated tag
value. A tag key is a general label that acts as a category for a more specific tag value. Each tag key
must be unique and it can have only one tag value. A tag value acts as a descriptor for a tag key.
Tag keys and values are case sensitive. They can contain letters, numbers, spaces, or the following
symbols: _ . : / = + @ -
For more information, see Tagging Amazon Security Lake resources in the Amazon Security Lake
User Guide.
Contents
key
The name of the tag. This is a general label that acts as a category for a more specific tag value
(value).
Type: String
Required: Yes
value
The value that’s associated with the specified tag key (key). This value acts as a descriptor for
the tag key. A tag value cannot be null, but it can be an empty string.
Type: String
Required: Yes
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the
following:
Common Parameters
The following list contains the parameters that all actions use for signing Signature Version 4
requests with a query string. Any action-specific parameters are listed in the topic for that action.
For more information about Signature Version 4, see Signing AWS API requests in the IAM User
Guide.
Action
Type: string
Required: Yes
Version
The API version that the request is written for, expressed in the format YYYY-MM-DD.
Type: string
Required: Yes
X-Amz-Algorithm
The hash algorithm that you used to create the request signature.
Condition: Specify this parameter when you include authentication information in a query
string instead of in the HTTP authorization header.
Type: string
Required: Conditional
X-Amz-Credential
The credential scope value, which is a string that includes your access key, the date, the region
you are targeting, the service you are requesting, and a termination string ("aws4_request").
The value is expressed in the following format: access_key/YYYYMMDD/region/service/
aws4_request.
For more information, see Create a signed AWS API request in the IAM User Guide.
Condition: Specify this parameter when you include authentication information in a query
string instead of in the HTTP authorization header.
Type: string
Required: Conditional
X-Amz-Date
The date that is used to create the signature. The format must be ISO 8601 basic format
(YYYYMMDD'T'HHMMSS'Z'). For example, the following date time is a valid X-Amz-Date value:
20120325T120000Z.
Condition: X-Amz-Date is optional for all requests; it can be used to override the date used for
signing requests. If the Date header is specified in the ISO 8601 basic format, X-Amz-Date is not
required. When X-Amz-Date is used, it always overrides the value of the Date header. For more
information, see Elements of an AWS API request signature in the IAM User Guide.
Type: string
Required: Conditional
X-Amz-Security-Token
The temporary security token that was obtained through a call to AWS Security Token Service
(AWS STS). For a list of services that support temporary security credentials from AWS STS, see
AWS services that work with IAM in the IAM User Guide.
Condition: If you're using temporary security credentials from AWS STS, you must include the
security token.
Type: string
Required: Conditional
X-Amz-Signature
Specifies the hex-encoded signature that was calculated from the string to sign and the derived
signing key.
Condition: Specify this parameter when you include authentication information in a query
string instead of in the HTTP authorization header.
Type: string
Required: Conditional
X-Amz-SignedHeaders
Specifies all the HTTP headers that were included as part of the canonical request. For more
information about specifying signed headers, see Create a signed AWS API request in the IAM
User Guide.
Condition: Specify this parameter when you include authentication information in a query
string instead of in the HTTP authorization header.
Type: string
Required: Conditional
Common Errors
This section lists the errors common to the API actions of all AWS services. For errors specific to an
API action for this service, see the topic for that API action.
AccessDeniedException
The request processing has failed because of an unknown error, exception or failure.
Problems with the request at the HTTP level, e.g. we can't decompress the body according to
the decompression algorithm specified by the content-encoding.
Convenient exception that can be used when a request is aborted before a reply is sent back
(e.g. client closed connection).
Problems with the request at the HTTP level. The request entity is too large.
The request reached the service more than 15 minutes after the date stamp on the request or
more than 15 minutes after the request expiration date (such as for pre-signed URLs), or the
date stamp on the request is more than 15 minutes in the future.
Problems with the request at the HTTP level. Reading the Request timed out.
The X.509 certificate or AWS access key ID provided does not exist in our records.
UnknownOperationException
The action or operation requested is invalid. Verify that the action is typed correctly.