New feature

AWS Lambda MicroVMs now supports AWS PrivateLink

AWS Lambda MicroVMs now supports AWS PrivateLink, enabling private connectivity directly from VPC resources without exposing traffic to the public internet. This helps regulated workloads meet strict network isolation requirements.

AWS Lambda MicroVMs now supports AWS PrivateLink, allowing private connectivity directly from Amazon Virtual Private Cloud (VPC) resources. This ensures that traffic does not travel over the public internet when interacting with Lambda MicroVMs, which is particularly useful for regulated industries such as financial services, healthcare, and government that require strict network isolation. Developers and IT teams can create PrivateLink VPC Endpoints within their VPC to access MicroVM APIs-for example, to create MicroVM images or launch MicroVMs-and to connect to each MicroVM's HTTP endpoint. This feature can be enabled using the AWS Management Console, AWS CLI, AWS CloudFormation, or AWS SDKs, and is available in all regions where Lambda MicroVMs is offered.

Why it matters

This update is significant for developers and IT teams using Lambda MicroVMs, especially in regulated industries that require strict network isolation for security and compliance.

Read the original AWS announcement