View Source AWS.LambdaCore (aws-elixir v1.0.13)

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.

Link to this section Summary

Functions

Creates a network connector that enables Lambda compute resources to route outbound traffic through your Amazon VPC.

Initiates deletion of a network connector.

Retrieves the current configuration, state, and metadata of a network connector.

Returns a paginated list of network connectors in your account for the current Region.

Updates the VPC configuration or operator role of an existing network connector.

Link to this section Functions

Link to this function

create_network_connector(client, input, options \\ [])

View Source

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.

Link to this function

delete_network_connector(client, identifier, input, options \\ [])

View Source

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.

Link to this function

get_network_connector(client, identifier, options \\ [])

View Source

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.

Link to this function

list_network_connectors(client, marker \\ nil, max_items \\ nil, state \\ nil, options \\ [])

View Source

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.

Link to this function

update_network_connector(client, identifier, input, options \\ [])

View Source

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.