Accessing Macie with an interface endpoint (AWS PrivateLink)

You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and Amazon Macie. You can access Macie as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access Macie.

You establish this private connection by creating an interface endpoint, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for Macie.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for Macie interface endpoints

Amazon Macie supports interface endpoints in all the AWS Regions where it's currently available except the Asia Pacific (Osaka) and Israel (Tel Aviv) Regions. For a list of Regions where Macie is currently available, see Amazon Macie endpoints and quotas in the AWS General Reference. Macie supports making calls to all of its API actions through interface endpoints.

If you create an interface endpoint for Macie, consider doing the same for other AWS services that integrate with Macie and with AWS PrivateLink, such as Amazon EventBridge and AWS Security Hub. Macie and those services can then use the interface endpoints for the integration. For example, if you create an interface endpoint for Macie and an interface endpoint for Security Hub, Macie can use its interface endpoint when it publishes findings to Security Hub. Security Hub can use its interface endpoint when it receives the findings. For information about supported services, see AWS services that integrate with AWS PrivateLink in the AWS PrivateLink Guide.

Note that VPC endpoint policies are not supported for Macie. By default, full access to Macie is allowed through an interface endpoint. Alternatively, you can associate a security group with the endpoint network interfaces to control traffic to Macie through the interface endpoint.

Creating an interface endpoint for Macie

You can create an interface endpoint for Amazon Macie by using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create an interface endpoint in the AWS PrivateLink Guide.

When you create an interface endpoint for Macie, use the following service name:

com.amazonaws.region.macie2

Where region is the Region code for the applicable AWS Region.

If you enable private DNS for the interface endpoint, you can make API requests to Macie using its default Regional DNS name, for example, macie2.us-east-1.amazonaws.com for the US East (N. Virginia) Region.