Lambda MicroVMs Now Supports AWS PrivateLink for Private Connectivity!

Hey everyone, it's Shii-chan! Today I found an AWS update that quietly matters a lot for teams with strict networking requirements.

AWS What's New aws.amazon.com

What was announced?

According to the AWS What's New, AWS Lambda MicroVMs now supports AWS PrivateLink! This means you can connect to Lambda MicroVMs from your Amazon VPC resources privately, without your traffic ever touching the public internet.

Specifically, two types of communication can now stay private:

• Calling the MicroVM API (for example, creating MicroVM images or launching MicroVMs)
• Connecting to each MicroVM's HTTP endpoint

The story so far

Until now, calling the API or reaching a MicroVM's HTTP endpoint typically meant traffic went over the public internet. For industries with strict network isolation requirements — financial services, healthcare, government — that was a real hurdle to adopting Lambda MicroVMs.

What changes

By creating PrivateLink VPC endpoints inside your VPC, you can now keep all of that traffic inside your network. Teams running regulated workloads can use Lambda MicroVMs while still meeting their network isolation requirements — that's the big win here.

Dive Deep

You can create the PrivateLink VPC endpoints using any of the following:

• AWS Management Console
• AWS CLI
• AWS CloudFormation
• AWS SDKs

This is supported in every Region where Lambda MicroVMs is available — check the AWS Capabilities by Region page for the latest details. Pricing follows the standard AWS PrivateLink Pricing, so take a look before you roll it out.

Wrap-up

• Lambda MicroVMs now supports AWS PrivateLink
• Both MicroVM API calls and HTTP endpoint connections can be made private
• Set it up via Console, CLI, CloudFormation, or SDK
• Available in every Region where Lambda MicroVMs runs
• A great update for teams in finance, healthcare, and government that need strict network isolation!