Package software.amazon.awssdk.services.securitylake

Interface SecurityLakeAsyncClient

All Superinterfaces:
AutoCloseable, AwsClient, SdkAutoCloseable, SdkClient
@Generated("software.amazon.awssdk:codegen") @ThreadSafe public interface SecurityLakeAsyncClient extends AwsClient
Service client for accessing Amazon Security Lake asynchronously. This can be created using the static builder() method.The asynchronous client performs non-blocking I/O when configured with any SdkAsyncHttpClient supported in the SDK. However, full non-blocking is not guaranteed as the async client may perform blocking calls in some cases such as credentials retrieval and endpoint discovery as part of the async API call.

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 Amazon Web Services account. Amazon Web Services Organizations is an account management service that lets you consolidate multiple Amazon Web Services 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 CloudTrail, a service that provides a record of actions taken by a user, role, or an Amazon Web Services 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 Amazon Web 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 Amazon Web Services and third-party services can subscribe to the data that's stored in Security Lake for incident response and security data analytics.

  • Field Details

  • Method Details

    • createAwsLogSource

      default CompletableFuture<CreateAwsLogSourceResponse> createAwsLogSource(CreateAwsLogSourceRequest createAwsLogSourceRequest)

      Adds a natively supported Amazon Web Service as an Amazon Security Lake source. Enables source types for member accounts in required Amazon Web Services 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 Amazon Web Service as a source, Security Lake starts collecting logs and events from it.

      You can use this API only to enable natively supported Amazon Web Services as a source. Use CreateCustomLogSource to enable data collection from a custom source.

      Parameters:
      createAwsLogSourceRequest -
      Returns:
      A Java Future containing the result of the CreateAwsLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createAwsLogSource

      default CompletableFuture<CreateAwsLogSourceResponse> createAwsLogSource(Consumer<CreateAwsLogSourceRequest.Builder> createAwsLogSourceRequest)

      Adds a natively supported Amazon Web Service as an Amazon Security Lake source. Enables source types for member accounts in required Amazon Web Services 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 Amazon Web Service as a source, Security Lake starts collecting logs and events from it.

      You can use this API only to enable natively supported Amazon Web Services as a source. Use CreateCustomLogSource to enable data collection from a custom source.


      This is a convenience which creates an instance of the CreateAwsLogSourceRequest.Builder avoiding the need to create one manually via CreateAwsLogSourceRequest.builder()

      Parameters:
      createAwsLogSourceRequest - A Consumer that will call methods on CreateAwsLogSourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateAwsLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createCustomLogSource

      default CompletableFuture<CreateCustomLogSourceResponse> createCustomLogSource(CreateCustomLogSourceRequest createCustomLogSourceRequest)

      Adds a third-party custom source in Amazon Security Lake, from the Amazon Web Services 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 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 Glue table and an Glue crawler.

      Parameters:
      createCustomLogSourceRequest -
      Returns:
      A Java Future containing the result of the CreateCustomLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createCustomLogSource

      default CompletableFuture<CreateCustomLogSourceResponse> createCustomLogSource(Consumer<CreateCustomLogSourceRequest.Builder> createCustomLogSourceRequest)

      Adds a third-party custom source in Amazon Security Lake, from the Amazon Web Services 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 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 Glue table and an Glue crawler.


      This is a convenience which creates an instance of the CreateCustomLogSourceRequest.Builder avoiding the need to create one manually via CreateCustomLogSourceRequest.builder()

      Parameters:
      createCustomLogSourceRequest - A Consumer that will call methods on CreateCustomLogSourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateCustomLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLake

      default CompletableFuture<CreateDataLakeResponse> createDataLake(CreateDataLakeRequest createDataLakeRequest)

      Initializes an Amazon Security Lake instance with the provided (or default) configuration. You can enable Security Lake in Amazon Web Services 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. 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 Amazon Web Services account in the current Region, including security log and event data. For more information, see the Amazon Security Lake User Guide.

      Parameters:
      createDataLakeRequest -
      Returns:
      A Java Future containing the result of the CreateDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLake

      default CompletableFuture<CreateDataLakeResponse> createDataLake(Consumer<CreateDataLakeRequest.Builder> createDataLakeRequest)

      Initializes an Amazon Security Lake instance with the provided (or default) configuration. You can enable Security Lake in Amazon Web Services 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. 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 Amazon Web Services account in the current Region, including security log and event data. For more information, see the Amazon Security Lake User Guide.


      This is a convenience which creates an instance of the CreateDataLakeRequest.Builder avoiding the need to create one manually via CreateDataLakeRequest.builder()

      Parameters:
      createDataLakeRequest - A Consumer that will call methods on CreateDataLakeRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLakeExceptionSubscription

      default CompletableFuture<CreateDataLakeExceptionSubscriptionResponse> createDataLakeExceptionSubscription(CreateDataLakeExceptionSubscriptionRequest createDataLakeExceptionSubscriptionRequest)

      Creates the specified notification subscription in Amazon Security Lake for the organization you specify.

      Parameters:
      createDataLakeExceptionSubscriptionRequest -
      Returns:
      A Java Future containing the result of the CreateDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLakeExceptionSubscription

      default CompletableFuture<CreateDataLakeExceptionSubscriptionResponse> createDataLakeExceptionSubscription(Consumer<CreateDataLakeExceptionSubscriptionRequest.Builder> createDataLakeExceptionSubscriptionRequest)

      Creates the specified notification subscription in Amazon Security Lake for the organization you specify.


      This is a convenience which creates an instance of the CreateDataLakeExceptionSubscriptionRequest.Builder avoiding the need to create one manually via CreateDataLakeExceptionSubscriptionRequest.builder()

      Parameters:
      createDataLakeExceptionSubscriptionRequest - A Consumer that will call methods on CreateDataLakeExceptionSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLakeOrganizationConfiguration

      default CompletableFuture<CreateDataLakeOrganizationConfigurationResponse> createDataLakeOrganizationConfiguration(CreateDataLakeOrganizationConfigurationRequest createDataLakeOrganizationConfigurationRequest)

      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.

      Parameters:
      createDataLakeOrganizationConfigurationRequest -
      Returns:
      A Java Future containing the result of the CreateDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDataLakeOrganizationConfiguration

      default CompletableFuture<CreateDataLakeOrganizationConfigurationResponse> createDataLakeOrganizationConfiguration(Consumer<CreateDataLakeOrganizationConfigurationRequest.Builder> createDataLakeOrganizationConfigurationRequest)

      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 is a convenience which creates an instance of the CreateDataLakeOrganizationConfigurationRequest.Builder avoiding the need to create one manually via CreateDataLakeOrganizationConfigurationRequest.builder()

      Parameters:
      createDataLakeOrganizationConfigurationRequest - A Consumer that will call methods on CreateDataLakeOrganizationConfigurationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createSubscriber

      default CompletableFuture<CreateSubscriberResponse> createSubscriber(CreateSubscriberRequest createSubscriberRequest)

      Creates a subscription permission for accounts that are already enabled in Amazon Security Lake. You can create a subscriber with access to data in the current Amazon Web Services Region.

      Parameters:
      createSubscriberRequest -
      Returns:
      A Java Future containing the result of the CreateSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createSubscriber

      default CompletableFuture<CreateSubscriberResponse> createSubscriber(Consumer<CreateSubscriberRequest.Builder> createSubscriberRequest)

      Creates a subscription permission for accounts that are already enabled in Amazon Security Lake. You can create a subscriber with access to data in the current Amazon Web Services Region.


      This is a convenience which creates an instance of the CreateSubscriberRequest.Builder avoiding the need to create one manually via CreateSubscriberRequest.builder()

      Parameters:
      createSubscriberRequest - A Consumer that will call methods on CreateSubscriberRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createSubscriberNotification

      default CompletableFuture<CreateSubscriberNotificationResponse> createSubscriberNotification(CreateSubscriberNotificationRequest createSubscriberNotificationRequest)

      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.

      Parameters:
      createSubscriberNotificationRequest -
      Returns:
      A Java Future containing the result of the CreateSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createSubscriberNotification

      default CompletableFuture<CreateSubscriberNotificationResponse> createSubscriberNotification(Consumer<CreateSubscriberNotificationRequest.Builder> createSubscriberNotificationRequest)

      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.


      This is a convenience which creates an instance of the CreateSubscriberNotificationRequest.Builder avoiding the need to create one manually via CreateSubscriberNotificationRequest.builder()

      Parameters:
      createSubscriberNotificationRequest - A Consumer that will call methods on CreateSubscriberNotificationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteAwsLogSource

      default CompletableFuture<DeleteAwsLogSourceResponse> deleteAwsLogSource(DeleteAwsLogSourceRequest deleteAwsLogSourceRequest)

      Removes a natively supported Amazon Web 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 Amazon Web Services Region for either accounts that are part of a trusted organization or standalone accounts.

      Parameters:
      deleteAwsLogSourceRequest -
      Returns:
      A Java Future containing the result of the DeleteAwsLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteAwsLogSource

      default CompletableFuture<DeleteAwsLogSourceResponse> deleteAwsLogSource(Consumer<DeleteAwsLogSourceRequest.Builder> deleteAwsLogSourceRequest)

      Removes a natively supported Amazon Web 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 Amazon Web Services Region for either accounts that are part of a trusted organization or standalone accounts.


      This is a convenience which creates an instance of the DeleteAwsLogSourceRequest.Builder avoiding the need to create one manually via DeleteAwsLogSourceRequest.builder()

      Parameters:
      deleteAwsLogSourceRequest - A Consumer that will call methods on DeleteAwsLogSourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteAwsLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteCustomLogSource

      default CompletableFuture<DeleteCustomLogSourceResponse> deleteCustomLogSource(DeleteCustomLogSourceRequest deleteCustomLogSourceRequest)

      Removes a custom log source from Amazon Security Lake, to stop sending data from the custom source to Security Lake.

      Parameters:
      deleteCustomLogSourceRequest -
      Returns:
      A Java Future containing the result of the DeleteCustomLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteCustomLogSource

      default CompletableFuture<DeleteCustomLogSourceResponse> deleteCustomLogSource(Consumer<DeleteCustomLogSourceRequest.Builder> deleteCustomLogSourceRequest)

      Removes a custom log source from Amazon Security Lake, to stop sending data from the custom source to Security Lake.


      This is a convenience which creates an instance of the DeleteCustomLogSourceRequest.Builder avoiding the need to create one manually via DeleteCustomLogSourceRequest.builder()

      Parameters:
      deleteCustomLogSourceRequest - A Consumer that will call methods on DeleteCustomLogSourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteCustomLogSource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLake

      default CompletableFuture<DeleteDataLakeResponse> deleteDataLake(DeleteDataLakeRequest deleteDataLakeRequest)

      When you disable Amazon Security Lake from your account, Security Lake is disabled in all Amazon Web Services 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 Amazon Web Services account in the current Amazon Web Services Region.

      The DeleteDataLake operation does not delete the data that is stored in your Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.

      Parameters:
      deleteDataLakeRequest -
      Returns:
      A Java Future containing the result of the DeleteDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLake

      default CompletableFuture<DeleteDataLakeResponse> deleteDataLake(Consumer<DeleteDataLakeRequest.Builder> deleteDataLakeRequest)

      When you disable Amazon Security Lake from your account, Security Lake is disabled in all Amazon Web Services 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 Amazon Web Services account in the current Amazon Web Services Region.

      The DeleteDataLake operation does not delete the data that is stored in your Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.


      This is a convenience which creates an instance of the DeleteDataLakeRequest.Builder avoiding the need to create one manually via DeleteDataLakeRequest.builder()

      Parameters:
      deleteDataLakeRequest - A Consumer that will call methods on DeleteDataLakeRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLakeExceptionSubscription

      default CompletableFuture<DeleteDataLakeExceptionSubscriptionResponse> deleteDataLakeExceptionSubscription(DeleteDataLakeExceptionSubscriptionRequest deleteDataLakeExceptionSubscriptionRequest)

      Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.

      Parameters:
      deleteDataLakeExceptionSubscriptionRequest -
      Returns:
      A Java Future containing the result of the DeleteDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLakeExceptionSubscription

      default CompletableFuture<DeleteDataLakeExceptionSubscriptionResponse> deleteDataLakeExceptionSubscription(Consumer<DeleteDataLakeExceptionSubscriptionRequest.Builder> deleteDataLakeExceptionSubscriptionRequest)

      Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.


      This is a convenience which creates an instance of the DeleteDataLakeExceptionSubscriptionRequest.Builder avoiding the need to create one manually via DeleteDataLakeExceptionSubscriptionRequest.builder()

      Parameters:
      deleteDataLakeExceptionSubscriptionRequest - A Consumer that will call methods on DeleteDataLakeExceptionSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLakeOrganizationConfiguration

      default CompletableFuture<DeleteDataLakeOrganizationConfigurationResponse> deleteDataLakeOrganizationConfiguration(DeleteDataLakeOrganizationConfigurationRequest deleteDataLakeOrganizationConfigurationRequest)

      Turns off automatic enablement of Amazon Security Lake for member accounts that are added to an organization in 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.

      Parameters:
      deleteDataLakeOrganizationConfigurationRequest -
      Returns:
      A Java Future containing the result of the DeleteDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDataLakeOrganizationConfiguration

      default CompletableFuture<DeleteDataLakeOrganizationConfigurationResponse> deleteDataLakeOrganizationConfiguration(Consumer<DeleteDataLakeOrganizationConfigurationRequest.Builder> deleteDataLakeOrganizationConfigurationRequest)

      Turns off automatic enablement of Amazon Security Lake for member accounts that are added to an organization in 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.


      This is a convenience which creates an instance of the DeleteDataLakeOrganizationConfigurationRequest.Builder avoiding the need to create one manually via DeleteDataLakeOrganizationConfigurationRequest.builder()

      Parameters:
      deleteDataLakeOrganizationConfigurationRequest - A Consumer that will call methods on DeleteDataLakeOrganizationConfigurationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteSubscriber

      default CompletableFuture<DeleteSubscriberResponse> deleteSubscriber(DeleteSubscriberRequest deleteSubscriberRequest)

      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 Amazon Web Services Region.

      Parameters:
      deleteSubscriberRequest -
      Returns:
      A Java Future containing the result of the DeleteSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteSubscriber

      default CompletableFuture<DeleteSubscriberResponse> deleteSubscriber(Consumer<DeleteSubscriberRequest.Builder> deleteSubscriberRequest)

      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 Amazon Web Services Region.


      This is a convenience which creates an instance of the DeleteSubscriberRequest.Builder avoiding the need to create one manually via DeleteSubscriberRequest.builder()

      Parameters:
      deleteSubscriberRequest - A Consumer that will call methods on DeleteSubscriberRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteSubscriberNotification

      default CompletableFuture<DeleteSubscriberNotificationResponse> deleteSubscriberNotification(DeleteSubscriberNotificationRequest deleteSubscriberNotificationRequest)

      Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.

      Parameters:
      deleteSubscriberNotificationRequest -
      Returns:
      A Java Future containing the result of the DeleteSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteSubscriberNotification

      default CompletableFuture<DeleteSubscriberNotificationResponse> deleteSubscriberNotification(Consumer<DeleteSubscriberNotificationRequest.Builder> deleteSubscriberNotificationRequest)

      Deletes the specified notification subscription in Amazon Security Lake for the organization you specify.


      This is a convenience which creates an instance of the DeleteSubscriberNotificationRequest.Builder avoiding the need to create one manually via DeleteSubscriberNotificationRequest.builder()

      Parameters:
      deleteSubscriberNotificationRequest - A Consumer that will call methods on DeleteSubscriberNotificationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deregisterDataLakeDelegatedAdministrator

      default CompletableFuture<DeregisterDataLakeDelegatedAdministratorResponse> deregisterDataLakeDelegatedAdministrator(DeregisterDataLakeDelegatedAdministratorRequest deregisterDataLakeDelegatedAdministratorRequest)

      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.

      Parameters:
      deregisterDataLakeDelegatedAdministratorRequest -
      Returns:
      A Java Future containing the result of the DeregisterDataLakeDelegatedAdministrator operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deregisterDataLakeDelegatedAdministrator

      default CompletableFuture<DeregisterDataLakeDelegatedAdministratorResponse> deregisterDataLakeDelegatedAdministrator(Consumer<DeregisterDataLakeDelegatedAdministratorRequest.Builder> deregisterDataLakeDelegatedAdministratorRequest)

      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.


      This is a convenience which creates an instance of the DeregisterDataLakeDelegatedAdministratorRequest.Builder avoiding the need to create one manually via DeregisterDataLakeDelegatedAdministratorRequest.builder()

      Parameters:
      deregisterDataLakeDelegatedAdministratorRequest - A Consumer that will call methods on DeregisterDataLakeDelegatedAdministratorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeregisterDataLakeDelegatedAdministrator operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeExceptionSubscription

      default CompletableFuture<GetDataLakeExceptionSubscriptionResponse> getDataLakeExceptionSubscription(GetDataLakeExceptionSubscriptionRequest getDataLakeExceptionSubscriptionRequest)

      Retrieves the details of exception notifications for the account in Amazon Security Lake.

      Parameters:
      getDataLakeExceptionSubscriptionRequest -
      Returns:
      A Java Future containing the result of the GetDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeExceptionSubscription

      default CompletableFuture<GetDataLakeExceptionSubscriptionResponse> getDataLakeExceptionSubscription(Consumer<GetDataLakeExceptionSubscriptionRequest.Builder> getDataLakeExceptionSubscriptionRequest)

      Retrieves the details of exception notifications for the account in Amazon Security Lake.


      This is a convenience which creates an instance of the GetDataLakeExceptionSubscriptionRequest.Builder avoiding the need to create one manually via GetDataLakeExceptionSubscriptionRequest.builder()

      Parameters:
      getDataLakeExceptionSubscriptionRequest - A Consumer that will call methods on GetDataLakeExceptionSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeOrganizationConfiguration

      default CompletableFuture<GetDataLakeOrganizationConfigurationResponse> getDataLakeOrganizationConfiguration(GetDataLakeOrganizationConfigurationRequest getDataLakeOrganizationConfigurationRequest)

      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.

      Parameters:
      getDataLakeOrganizationConfigurationRequest -
      Returns:
      A Java Future containing the result of the GetDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeOrganizationConfiguration

      default CompletableFuture<GetDataLakeOrganizationConfigurationResponse> getDataLakeOrganizationConfiguration(Consumer<GetDataLakeOrganizationConfigurationRequest.Builder> getDataLakeOrganizationConfigurationRequest)

      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.


      This is a convenience which creates an instance of the GetDataLakeOrganizationConfigurationRequest.Builder avoiding the need to create one manually via GetDataLakeOrganizationConfigurationRequest.builder()

      Parameters:
      getDataLakeOrganizationConfigurationRequest - A Consumer that will call methods on GetDataLakeOrganizationConfigurationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetDataLakeOrganizationConfiguration operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeSources

      default CompletableFuture<GetDataLakeSourcesResponse> getDataLakeSources(GetDataLakeSourcesRequest getDataLakeSourcesRequest)

      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.

      Parameters:
      getDataLakeSourcesRequest -
      Returns:
      A Java Future containing the result of the GetDataLakeSources operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeSources

      default CompletableFuture<GetDataLakeSourcesResponse> getDataLakeSources(Consumer<GetDataLakeSourcesRequest.Builder> getDataLakeSourcesRequest)

      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.


      This is a convenience which creates an instance of the GetDataLakeSourcesRequest.Builder avoiding the need to create one manually via GetDataLakeSourcesRequest.builder()

      Parameters:
      getDataLakeSourcesRequest - A Consumer that will call methods on GetDataLakeSourcesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetDataLakeSources operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeSourcesPaginator

      default GetDataLakeSourcesPublisher getDataLakeSourcesPaginator(GetDataLakeSourcesRequest getDataLakeSourcesRequest)

      This is a variant of getDataLakeSources(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.GetDataLakeSourcesPublisher publisher = client.getDataLakeSourcesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.GetDataLakeSourcesPublisher publisher = client.getDataLakeSourcesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getDataLakeSources(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesRequest) operation.

      Parameters:
      getDataLakeSourcesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDataLakeSourcesPaginator

      default GetDataLakeSourcesPublisher getDataLakeSourcesPaginator(Consumer<GetDataLakeSourcesRequest.Builder> getDataLakeSourcesRequest)

      This is a variant of getDataLakeSources(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.GetDataLakeSourcesPublisher publisher = client.getDataLakeSourcesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.GetDataLakeSourcesPublisher publisher = client.getDataLakeSourcesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getDataLakeSources(software.amazon.awssdk.services.securitylake.model.GetDataLakeSourcesRequest) operation.


      This is a convenience which creates an instance of the GetDataLakeSourcesRequest.Builder avoiding the need to create one manually via GetDataLakeSourcesRequest.builder()

      Parameters:
      getDataLakeSourcesRequest - A Consumer that will call methods on GetDataLakeSourcesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getSubscriber

      default CompletableFuture<GetSubscriberResponse> getSubscriber(GetSubscriberRequest getSubscriberRequest)

      Retrieves the subscription information for the specified subscription ID. You can get information about a specific subscriber.

      Parameters:
      getSubscriberRequest -
      Returns:
      A Java Future containing the result of the GetSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getSubscriber

      default CompletableFuture<GetSubscriberResponse> getSubscriber(Consumer<GetSubscriberRequest.Builder> getSubscriberRequest)

      Retrieves the subscription information for the specified subscription ID. You can get information about a specific subscriber.


      This is a convenience which creates an instance of the GetSubscriberRequest.Builder avoiding the need to create one manually via GetSubscriberRequest.builder()

      Parameters:
      getSubscriberRequest - A Consumer that will call methods on GetSubscriberRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakeExceptions

      default CompletableFuture<ListDataLakeExceptionsResponse> listDataLakeExceptions(ListDataLakeExceptionsRequest listDataLakeExceptionsRequest)

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

      Parameters:
      listDataLakeExceptionsRequest -
      Returns:
      A Java Future containing the result of the ListDataLakeExceptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakeExceptions

      default CompletableFuture<ListDataLakeExceptionsResponse> listDataLakeExceptions(Consumer<ListDataLakeExceptionsRequest.Builder> listDataLakeExceptionsRequest)

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


      This is a convenience which creates an instance of the ListDataLakeExceptionsRequest.Builder avoiding the need to create one manually via ListDataLakeExceptionsRequest.builder()

      Parameters:
      listDataLakeExceptionsRequest - A Consumer that will call methods on ListDataLakeExceptionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListDataLakeExceptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakeExceptionsPaginator

      default ListDataLakeExceptionsPublisher listDataLakeExceptionsPaginator(ListDataLakeExceptionsRequest listDataLakeExceptionsRequest)

      This is a variant of listDataLakeExceptions(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListDataLakeExceptionsPublisher publisher = client.listDataLakeExceptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListDataLakeExceptionsPublisher publisher = client.listDataLakeExceptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listDataLakeExceptions(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsRequest) operation.

      Parameters:
      listDataLakeExceptionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakeExceptionsPaginator

      default ListDataLakeExceptionsPublisher listDataLakeExceptionsPaginator(Consumer<ListDataLakeExceptionsRequest.Builder> listDataLakeExceptionsRequest)

      This is a variant of listDataLakeExceptions(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListDataLakeExceptionsPublisher publisher = client.listDataLakeExceptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListDataLakeExceptionsPublisher publisher = client.listDataLakeExceptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listDataLakeExceptions(software.amazon.awssdk.services.securitylake.model.ListDataLakeExceptionsRequest) operation.


      This is a convenience which creates an instance of the ListDataLakeExceptionsRequest.Builder avoiding the need to create one manually via ListDataLakeExceptionsRequest.builder()

      Parameters:
      listDataLakeExceptionsRequest - A Consumer that will call methods on ListDataLakeExceptionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakes

      default CompletableFuture<ListDataLakesResponse> listDataLakes(ListDataLakesRequest listDataLakesRequest)

      Retrieves the Amazon Security Lake configuration object for the specified Amazon Web Services Regions. You can use this operation to determine whether Security Lake is enabled for a Region.

      Parameters:
      listDataLakesRequest -
      Returns:
      A Java Future containing the result of the ListDataLakes operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listDataLakes

      default CompletableFuture<ListDataLakesResponse> listDataLakes(Consumer<ListDataLakesRequest.Builder> listDataLakesRequest)

      Retrieves the Amazon Security Lake configuration object for the specified Amazon Web Services Regions. You can use this operation to determine whether Security Lake is enabled for a Region.


      This is a convenience which creates an instance of the ListDataLakesRequest.Builder avoiding the need to create one manually via ListDataLakesRequest.builder()

      Parameters:
      listDataLakesRequest - A Consumer that will call methods on ListDataLakesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListDataLakes operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listLogSources

      default CompletableFuture<ListLogSourcesResponse> listLogSources(ListLogSourcesRequest listLogSourcesRequest)

      Retrieves the log sources in the current Amazon Web Services Region.

      Parameters:
      listLogSourcesRequest -
      Returns:
      A Java Future containing the result of the ListLogSources operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listLogSources

      default CompletableFuture<ListLogSourcesResponse> listLogSources(Consumer<ListLogSourcesRequest.Builder> listLogSourcesRequest)

      Retrieves the log sources in the current Amazon Web Services Region.


      This is a convenience which creates an instance of the ListLogSourcesRequest.Builder avoiding the need to create one manually via ListLogSourcesRequest.builder()

      Parameters:
      listLogSourcesRequest - A Consumer that will call methods on ListLogSourcesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListLogSources operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listLogSourcesPaginator

      default ListLogSourcesPublisher listLogSourcesPaginator(ListLogSourcesRequest listLogSourcesRequest)

      This is a variant of listLogSources(software.amazon.awssdk.services.securitylake.model.ListLogSourcesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListLogSourcesPublisher publisher = client.listLogSourcesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListLogSourcesPublisher publisher = client.listLogSourcesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListLogSourcesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListLogSourcesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listLogSources(software.amazon.awssdk.services.securitylake.model.ListLogSourcesRequest) operation.

      Parameters:
      listLogSourcesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listLogSourcesPaginator

      default ListLogSourcesPublisher listLogSourcesPaginator(Consumer<ListLogSourcesRequest.Builder> listLogSourcesRequest)

      This is a variant of listLogSources(software.amazon.awssdk.services.securitylake.model.ListLogSourcesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListLogSourcesPublisher publisher = client.listLogSourcesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListLogSourcesPublisher publisher = client.listLogSourcesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListLogSourcesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListLogSourcesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listLogSources(software.amazon.awssdk.services.securitylake.model.ListLogSourcesRequest) operation.


      This is a convenience which creates an instance of the ListLogSourcesRequest.Builder avoiding the need to create one manually via ListLogSourcesRequest.builder()

      Parameters:
      listLogSourcesRequest - A Consumer that will call methods on ListLogSourcesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listSubscribers

      default CompletableFuture<ListSubscribersResponse> listSubscribers(ListSubscribersRequest listSubscribersRequest)

      List all subscribers for the specific Amazon Security Lake account ID. You can retrieve a list of subscriptions associated with a specific organization or Amazon Web Services account.

      Parameters:
      listSubscribersRequest -
      Returns:
      A Java Future containing the result of the ListSubscribers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listSubscribers

      default CompletableFuture<ListSubscribersResponse> listSubscribers(Consumer<ListSubscribersRequest.Builder> listSubscribersRequest)

      List all subscribers for the specific Amazon Security Lake account ID. You can retrieve a list of subscriptions associated with a specific organization or Amazon Web Services account.


      This is a convenience which creates an instance of the ListSubscribersRequest.Builder avoiding the need to create one manually via ListSubscribersRequest.builder()

      Parameters:
      listSubscribersRequest - A Consumer that will call methods on ListSubscribersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListSubscribers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listSubscribersPaginator

      default ListSubscribersPublisher listSubscribersPaginator(ListSubscribersRequest listSubscribersRequest)

      This is a variant of listSubscribers(software.amazon.awssdk.services.securitylake.model.ListSubscribersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListSubscribersPublisher publisher = client.listSubscribersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListSubscribersPublisher publisher = client.listSubscribersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListSubscribersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListSubscribersResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listSubscribers(software.amazon.awssdk.services.securitylake.model.ListSubscribersRequest) operation.

      Parameters:
      listSubscribersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listSubscribersPaginator

      default ListSubscribersPublisher listSubscribersPaginator(Consumer<ListSubscribersRequest.Builder> listSubscribersRequest)

      This is a variant of listSubscribers(software.amazon.awssdk.services.securitylake.model.ListSubscribersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.securitylake.paginators.ListSubscribersPublisher publisher = client.listSubscribersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.securitylake.paginators.ListSubscribersPublisher publisher = client.listSubscribersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.securitylake.model.ListSubscribersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.securitylake.model.ListSubscribersResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listSubscribers(software.amazon.awssdk.services.securitylake.model.ListSubscribersRequest) operation.


      This is a convenience which creates an instance of the ListSubscribersRequest.Builder avoiding the need to create one manually via ListSubscribersRequest.builder()

      Parameters:
      listSubscribersRequest - A Consumer that will call methods on ListSubscribersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)

      Retrieves the tags (keys and values) that are associated with an Amazon Security Lake resource: a subscriber, or the data lake configuration for your Amazon Web Services account in a particular Amazon Web Services Region.

      Parameters:
      listTagsForResourceRequest -
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)

      Retrieves the tags (keys and values) that are associated with an Amazon Security Lake resource: a subscriber, or the data lake configuration for your Amazon Web Services account in a particular Amazon Web Services Region.


      This is a convenience which creates an instance of the ListTagsForResourceRequest.Builder avoiding the need to create one manually via ListTagsForResourceRequest.builder()

      Parameters:
      listTagsForResourceRequest - A Consumer that will call methods on ListTagsForResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • registerDataLakeDelegatedAdministrator

      default CompletableFuture<RegisterDataLakeDelegatedAdministratorResponse> registerDataLakeDelegatedAdministrator(RegisterDataLakeDelegatedAdministratorRequest registerDataLakeDelegatedAdministratorRequest)

      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.

      Parameters:
      registerDataLakeDelegatedAdministratorRequest -
      Returns:
      A Java Future containing the result of the RegisterDataLakeDelegatedAdministrator operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • registerDataLakeDelegatedAdministrator

      default CompletableFuture<RegisterDataLakeDelegatedAdministratorResponse> registerDataLakeDelegatedAdministrator(Consumer<RegisterDataLakeDelegatedAdministratorRequest.Builder> registerDataLakeDelegatedAdministratorRequest)

      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.


      This is a convenience which creates an instance of the RegisterDataLakeDelegatedAdministratorRequest.Builder avoiding the need to create one manually via RegisterDataLakeDelegatedAdministratorRequest.builder()

      Parameters:
      registerDataLakeDelegatedAdministratorRequest - A Consumer that will call methods on RegisterDataLakeDelegatedAdministratorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RegisterDataLakeDelegatedAdministrator operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(TagResourceRequest tagResourceRequest)

      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 Amazon Web Services account in a particular Amazon Web Services Region. A tag is a label that you can define and associate with Amazon Web Services 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.

      Parameters:
      tagResourceRequest -
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(Consumer<TagResourceRequest.Builder> tagResourceRequest)

      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 Amazon Web Services account in a particular Amazon Web Services Region. A tag is a label that you can define and associate with Amazon Web Services 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.


      This is a convenience which creates an instance of the TagResourceRequest.Builder avoiding the need to create one manually via TagResourceRequest.builder()

      Parameters:
      tagResourceRequest - A Consumer that will call methods on TagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(UntagResourceRequest untagResourceRequest)

      Removes one or more tags (keys and values) from an Amazon Security Lake resource: a subscriber, or the data lake configuration for your Amazon Web Services account in a particular Amazon Web Services Region.

      Parameters:
      untagResourceRequest -
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(Consumer<UntagResourceRequest.Builder> untagResourceRequest)

      Removes one or more tags (keys and values) from an Amazon Security Lake resource: a subscriber, or the data lake configuration for your Amazon Web Services account in a particular Amazon Web Services Region.


      This is a convenience which creates an instance of the UntagResourceRequest.Builder avoiding the need to create one manually via UntagResourceRequest.builder()

      Parameters:
      untagResourceRequest - A Consumer that will call methods on UntagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDataLake

      default CompletableFuture<UpdateDataLakeResponse> updateDataLake(UpdateDataLakeRequest updateDataLakeRequest)

      Specifies where to store your security data and for how long. You can add a rollup Region to consolidate data from multiple Amazon Web Services Regions.

      Parameters:
      updateDataLakeRequest -
      Returns:
      A Java Future containing the result of the UpdateDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDataLake

      default CompletableFuture<UpdateDataLakeResponse> updateDataLake(Consumer<UpdateDataLakeRequest.Builder> updateDataLakeRequest)

      Specifies where to store your security data and for how long. You can add a rollup Region to consolidate data from multiple Amazon Web Services Regions.


      This is a convenience which creates an instance of the UpdateDataLakeRequest.Builder avoiding the need to create one manually via UpdateDataLakeRequest.builder()

      Parameters:
      updateDataLakeRequest - A Consumer that will call methods on UpdateDataLakeRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateDataLake operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDataLakeExceptionSubscription

      default CompletableFuture<UpdateDataLakeExceptionSubscriptionResponse> updateDataLakeExceptionSubscription(UpdateDataLakeExceptionSubscriptionRequest updateDataLakeExceptionSubscriptionRequest)

      Updates the specified notification subscription in Amazon Security Lake for the organization you specify.

      Parameters:
      updateDataLakeExceptionSubscriptionRequest -
      Returns:
      A Java Future containing the result of the UpdateDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDataLakeExceptionSubscription

      default CompletableFuture<UpdateDataLakeExceptionSubscriptionResponse> updateDataLakeExceptionSubscription(Consumer<UpdateDataLakeExceptionSubscriptionRequest.Builder> updateDataLakeExceptionSubscriptionRequest)

      Updates the specified notification subscription in Amazon Security Lake for the organization you specify.


      This is a convenience which creates an instance of the UpdateDataLakeExceptionSubscriptionRequest.Builder avoiding the need to create one manually via UpdateDataLakeExceptionSubscriptionRequest.builder()

      Parameters:
      updateDataLakeExceptionSubscriptionRequest - A Consumer that will call methods on UpdateDataLakeExceptionSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateDataLakeExceptionSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateSubscriber

      default CompletableFuture<UpdateSubscriberResponse> updateSubscriber(UpdateSubscriberRequest updateSubscriberRequest)

      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.

      Parameters:
      updateSubscriberRequest -
      Returns:
      A Java Future containing the result of the UpdateSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateSubscriber

      default CompletableFuture<UpdateSubscriberResponse> updateSubscriber(Consumer<UpdateSubscriberRequest.Builder> updateSubscriberRequest)

      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.


      This is a convenience which creates an instance of the UpdateSubscriberRequest.Builder avoiding the need to create one manually via UpdateSubscriberRequest.builder()

      Parameters:
      updateSubscriberRequest - A Consumer that will call methods on UpdateSubscriberRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateSubscriber operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateSubscriberNotification

      default CompletableFuture<UpdateSubscriberNotificationResponse> updateSubscriberNotification(UpdateSubscriberNotificationRequest updateSubscriberNotificationRequest)

      Updates an existing notification method for the subscription (SQS or HTTPs endpoint) or switches the notification subscription endpoint for a subscriber.

      Parameters:
      updateSubscriberNotificationRequest -
      Returns:
      A Java Future containing the result of the UpdateSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateSubscriberNotification

      default CompletableFuture<UpdateSubscriberNotificationResponse> updateSubscriberNotification(Consumer<UpdateSubscriberNotificationRequest.Builder> updateSubscriberNotificationRequest)

      Updates an existing notification method for the subscription (SQS or HTTPs endpoint) or switches the notification subscription endpoint for a subscriber.


      This is a convenience which creates an instance of the UpdateSubscriberNotificationRequest.Builder avoiding the need to create one manually via UpdateSubscriberNotificationRequest.builder()

      Parameters:
      updateSubscriberNotificationRequest - A Consumer that will call methods on UpdateSubscriberNotificationRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateSubscriberNotification operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • BadRequestException The request is malformed or contains an error such as an invalid parameter value or a missing required parameter.
      • ResourceNotFoundException The resource could not be found.
      • InternalServerException Internal service exceptions are sometimes caused by transient issues. Before you start troubleshooting, perform the operation again.
      • 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 Amazon Web Services action. An implicit denial occurs when there is no applicable Deny statement and also no applicable Allow statement.
      • 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.
      • ThrottlingException The limit on the number of requests per second was exceeded.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • SecurityLakeException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • serviceClientConfiguration

      default SecurityLakeServiceClientConfiguration serviceClientConfiguration()
      Description copied from interface: SdkClient
      The SDK service client configuration exposes client settings to the user, e.g., ClientOverrideConfiguration
      Specified by:
      serviceClientConfiguration in interface AwsClient
      Specified by:
      serviceClientConfiguration in interface SdkClient
      Returns:
      SdkServiceClientConfiguration

    • create

      static SecurityLakeAsyncClient create()
      Create a SecurityLakeAsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.

    • builder

      static SecurityLakeAsyncClientBuilder builder()
      Create a builder that can be used to configure and create a SecurityLakeAsyncClient.