AWS Lambda MicroVMs now supports AWS PrivateLink

AWS Lambda MicroVMs now supports AWS PrivateLink, enabling private connectivity to Lambda MicroVMs directly from Amazon Virtual Private Cloud (VPC) resources without exposing traffic to the public internet. This launch helps regulated workloads in financial services, healthcare, and government meet strict network isolation requirements when building with Lambda MicroVMs. PrivateLink VPC Endpoints deliver private connectivity to AWS services from your VPC, ensuring that your traffic does not travel over the public internet when communicating with AWS services. Today's launch extends this capability to Lambda MicroVMs. Developers and IT teams needing private connectivity to Lambda MicroVMs can now create PrivateLink VPC Endpoints in their VPC to call MicroVM APIs (for example, to create MicroVM images or launch MicroVMs) and to connect to each MicroVM’s HTTP endpoint. PrivateLink VPC Endpoints for Lambda MicroVMs can be created using the AWS Management Console, AWS CLI, AWS CloudFormation, or the AWS SDKs. This feature is supported in all Regions where Lambda MicroVMs is available. Visit the [AWS Capabilities by Region page](https://builder.aws.com/build/capabilities) for the latest region availability. To learn more about using PrivateLink with Lambda MicroVMs, see the [developer guide](https://docs.aws.amazon.com/lambda/latest/dg/microvms-networking.html). For pricing details, see [AWS PrivateLink Pricing](https://aws.amazon.com/privatelink/pricing/). To learn more about configuring private connectivity for AWS services, visit the [AWS PrivateLink developer guide](https://docs.aws.amazon.com/vpc/latest/privatelink/interface-endpoints.html).