Interface LambdaCoreAsyncClient

All Superinterfaces:
AutoCloseable, AwsClient, SdkAutoCloseable, SdkClient
@Generated("software.amazon.awssdk:codegen") @SdkPublicApi @ThreadSafe public interface LambdaCoreAsyncClient extends AwsClient
Service client for accessing AWS Lambda Core 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.

AWS Lambda Core is a set of APIs for managing shared infrastructure resources used by AWS Lambda. The Lambda Core API provides operations for creating and managing network connectors that enable Lambda MicroVMs to access resources in your Amazon Virtual Private Cloud (Amazon VPC).

Network connectors provision elastic network interfaces (ENIs) in your VPC subnets, providing a managed network path from Lambda compute environments to private resources such as Amazon RDS databases, Amazon ElastiCache clusters, and internal APIs. You create a network connector once and attach it to one or more Lambda MicroVMs at run time.

  • Field Details

  • Method Details

    • createNetworkConnector

      default CompletableFuture<CreateNetworkConnectorResponse> createNetworkConnector(CreateNetworkConnectorRequest createNetworkConnectorRequest)

      Creates a network connector that enables Lambda compute resources to route outbound traffic through your Amazon VPC. The network connector provisions elastic network interfaces (ENIs) in the subnets you specify, providing a managed network path to private resources such as databases, caches, and internal APIs.

      This operation is asynchronous. The network connector starts in PENDING state while ENIs are provisioned in your VPC (provisioning typically takes up to 10 minutes). Use GetNetworkConnector to poll the connector state until it reaches ACTIVE. Once active, you can attach the connector to Lambda MicroVMs at run time using the egressNetworkConnectors parameter on RunMicroVm.

      This operation is idempotent when you provide a ClientToken — if you retry a request that completed successfully using the same client token, the operation returns the existing connector without creating a duplicate.

      Parameters:
      createNetworkConnectorRequest -
      Returns:
      A Java Future containing the result of the CreateNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • NetworkConnectorLimitExceededException The account has reached the maximum number of network connectors allowed. Delete unused connectors or request a limit increase through Service Quotas.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createNetworkConnector

      default CompletableFuture<CreateNetworkConnectorResponse> createNetworkConnector(Consumer<CreateNetworkConnectorRequest.Builder> createNetworkConnectorRequest)

      Creates a network connector that enables Lambda compute resources to route outbound traffic through your Amazon VPC. The network connector provisions elastic network interfaces (ENIs) in the subnets you specify, providing a managed network path to private resources such as databases, caches, and internal APIs.

      This operation is asynchronous. The network connector starts in PENDING state while ENIs are provisioned in your VPC (provisioning typically takes up to 10 minutes). Use GetNetworkConnector to poll the connector state until it reaches ACTIVE. Once active, you can attach the connector to Lambda MicroVMs at run time using the egressNetworkConnectors parameter on RunMicroVm.

      This operation is idempotent when you provide a ClientToken — if you retry a request that completed successfully using the same client token, the operation returns the existing connector without creating a duplicate.


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

      Parameters:
      createNetworkConnectorRequest - A Consumer that will call methods on CreateNetworkConnectorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • NetworkConnectorLimitExceededException The account has reached the maximum number of network connectors allowed. Delete unused connectors or request a limit increase through Service Quotas.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteNetworkConnector

      default CompletableFuture<DeleteNetworkConnectorResponse> deleteNetworkConnector(DeleteNetworkConnectorRequest deleteNetworkConnectorRequest)

      Initiates deletion of a network connector. The connector transitions to DELETING state while elastic network interfaces are cleaned up asynchronously. After deletion completes, subsequent calls to GetNetworkConnector return ResourceNotFoundException.

      This operation is idempotent — calling delete on a connector that is already deleting or has been deleted succeeds without error. You can delete connectors in ACTIVE or FAILED states. Before deleting a connector, ensure that no Lambda MicroVMs are using it, as they will lose VPC egress connectivity immediately.

      Parameters:
      deleteNetworkConnectorRequest -
      Returns:
      A Java Future containing the result of the DeleteNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteNetworkConnector

      default CompletableFuture<DeleteNetworkConnectorResponse> deleteNetworkConnector(Consumer<DeleteNetworkConnectorRequest.Builder> deleteNetworkConnectorRequest)

      Initiates deletion of a network connector. The connector transitions to DELETING state while elastic network interfaces are cleaned up asynchronously. After deletion completes, subsequent calls to GetNetworkConnector return ResourceNotFoundException.

      This operation is idempotent — calling delete on a connector that is already deleting or has been deleted succeeds without error. You can delete connectors in ACTIVE or FAILED states. Before deleting a connector, ensure that no Lambda MicroVMs are using it, as they will lose VPC egress connectivity immediately.


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

      Parameters:
      deleteNetworkConnectorRequest - A Consumer that will call methods on DeleteNetworkConnectorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getNetworkConnector

      default CompletableFuture<GetNetworkConnectorResponse> getNetworkConnector(GetNetworkConnectorRequest getNetworkConnectorRequest)

      Retrieves the current configuration, state, and metadata of a network connector. The Identifier parameter accepts the connector ID, name, or full ARN. Use this operation to poll connector state after creation or update, or to inspect the current VPC configuration and any failure reasons.

      The response includes the full connector configuration, current state, and — if the connector has been updated — the LastUpdateStatus and LastUpdateStatusReasonCode fields that indicate whether the most recent update succeeded or failed.

      Parameters:
      getNetworkConnectorRequest -
      Returns:
      A Java Future containing the result of the GetNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getNetworkConnector

      default CompletableFuture<GetNetworkConnectorResponse> getNetworkConnector(Consumer<GetNetworkConnectorRequest.Builder> getNetworkConnectorRequest)

      Retrieves the current configuration, state, and metadata of a network connector. The Identifier parameter accepts the connector ID, name, or full ARN. Use this operation to poll connector state after creation or update, or to inspect the current VPC configuration and any failure reasons.

      The response includes the full connector configuration, current state, and — if the connector has been updated — the LastUpdateStatus and LastUpdateStatusReasonCode fields that indicate whether the most recent update succeeded or failed.


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

      Parameters:
      getNetworkConnectorRequest - A Consumer that will call methods on GetNetworkConnectorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listNetworkConnectors

      default CompletableFuture<ListNetworkConnectorsResponse> listNetworkConnectors(ListNetworkConnectorsRequest listNetworkConnectorsRequest)

      Returns a paginated list of network connectors in your account for the current Region. You can optionally filter results by connector state. Use the Marker parameter from a previous response to retrieve the next page of results.

      Each item in the response includes the connector ARN, name, ID, type, current state, and last modified timestamp. To retrieve full configuration details for a specific connector, use GetNetworkConnector.

      Parameters:
      listNetworkConnectorsRequest -
      Returns:
      A Java Future containing the result of the ListNetworkConnectors 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listNetworkConnectors

      default CompletableFuture<ListNetworkConnectorsResponse> listNetworkConnectors(Consumer<ListNetworkConnectorsRequest.Builder> listNetworkConnectorsRequest)

      Returns a paginated list of network connectors in your account for the current Region. You can optionally filter results by connector state. Use the Marker parameter from a previous response to retrieve the next page of results.

      Each item in the response includes the connector ARN, name, ID, type, current state, and last modified timestamp. To retrieve full configuration details for a specific connector, use GetNetworkConnector.


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

      Parameters:
      listNetworkConnectorsRequest - A Consumer that will call methods on ListNetworkConnectorsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListNetworkConnectors 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listNetworkConnectorsPaginator

      default ListNetworkConnectorsPublisher listNetworkConnectorsPaginator(ListNetworkConnectorsRequest listNetworkConnectorsRequest)

      This is a variant of listNetworkConnectors(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsRequest) 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.lambdacore.paginators.ListNetworkConnectorsPublisher publisher = client.listNetworkConnectorsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.lambdacore.paginators.ListNetworkConnectorsPublisher publisher = client.listNetworkConnectorsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsResponse 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 MaxItems 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 listNetworkConnectors(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsRequest) operation.

      Parameters:
      listNetworkConnectorsRequest -
      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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listNetworkConnectorsPaginator

      default ListNetworkConnectorsPublisher listNetworkConnectorsPaginator(Consumer<ListNetworkConnectorsRequest.Builder> listNetworkConnectorsRequest)

      This is a variant of listNetworkConnectors(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsRequest) 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.lambdacore.paginators.ListNetworkConnectorsPublisher publisher = client.listNetworkConnectorsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.lambdacore.paginators.ListNetworkConnectorsPublisher publisher = client.listNetworkConnectorsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsResponse 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 MaxItems 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 listNetworkConnectors(software.amazon.awssdk.services.lambdacore.model.ListNetworkConnectorsRequest) operation.


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

      Parameters:
      listNetworkConnectorsRequest - A Consumer that will call methods on ListNetworkConnectorsRequest.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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateNetworkConnector

      default CompletableFuture<UpdateNetworkConnectorResponse> updateNetworkConnector(UpdateNetworkConnectorRequest updateNetworkConnectorRequest)

      Updates the VPC configuration or operator role of an existing network connector. You can modify the subnet IDs, security group IDs, network protocol, or operator role. The connector must be in ACTIVE state to accept updates.

      This operation is asynchronous. The connector remains in ACTIVE state during the update — existing workloads that reference this connector are not disrupted. Use GetNetworkConnector to monitor the LastUpdateStatus field, which transitions through InProgress to Successful or Failed. If the update fails, the LastUpdateStatusReasonCode field provides a specific error code for troubleshooting. This operation is idempotent when you provide a ClientToken .

      Parameters:
      updateNetworkConnectorRequest -
      Returns:
      A Java Future containing the result of the UpdateNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateNetworkConnector

      default CompletableFuture<UpdateNetworkConnectorResponse> updateNetworkConnector(Consumer<UpdateNetworkConnectorRequest.Builder> updateNetworkConnectorRequest)

      Updates the VPC configuration or operator role of an existing network connector. You can modify the subnet IDs, security group IDs, network protocol, or operator role. The connector must be in ACTIVE state to accept updates.

      This operation is asynchronous. The connector remains in ACTIVE state during the update — existing workloads that reference this connector are not disrupted. Use GetNetworkConnector to monitor the LastUpdateStatus field, which transitions through InProgress to Successful or Failed. If the update fails, the LastUpdateStatusReasonCode field provides a specific error code for troubleshooting. This operation is idempotent when you provide a ClientToken .


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

      Parameters:
      updateNetworkConnectorRequest - A Consumer that will call methods on UpdateNetworkConnectorRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateNetworkConnector 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.
      • InvalidParameterValueException One of the parameters in the request is not valid. Check the error message for details about which parameter failed validation.
      • ResourceConflictException The request could not be completed due to a conflict with the current state of the resource. For example, attempting to update a connector that is not in ACTIVE state.
      • ServiceException An internal service error occurred. Retry the request with exponential backoff.
      • TooManyRequestsException The request was throttled due to exceeding the allowed request rate. Retry the request after a brief wait using exponential backoff.
      • ResourceNotFoundException The specified network connector does not exist. Verify the identifier (ID, name, or ARN) and Region.
      • 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.
      • LambdaCoreException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • serviceClientConfiguration

      default LambdaCoreServiceClientConfiguration 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 LambdaCoreAsyncClient create()
      Create a LambdaCoreAsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.

    • builder

      static LambdaCoreAsyncClientBuilder builder()
      Create a builder that can be used to configure and create a LambdaCoreAsyncClient.