Using AMP with interface VPC endpoints - Amazon Managed Service for Prometheus

Using AMP with interface VPC endpoints

Amazon Managed Service for Prometheus (AMP) is in open preview. The preview is open to all AWS accounts and you do not need to request access. Features may be added or changed before announcing General Availability.

The preview currently supports the following Regions:

  • US East (Ohio)

  • US East (N. Virginia)

  • US West (Oregon)

  • Europe (Frankfurt)

  • Europe (Ireland)

If you use Amazon Virtual Private Cloud (Amazon VPC) to host your AWS resources, you can establish a private connection between your VPC and Amazon Managed Service for Prometheus. You can use these connections to enable AMP to communicate with your resources on your VPC without going through the public internet.

Amazon VPC is an AWS service that you can use to launch AWS resources in a virtual network that you define. With a VPC, you have control over your network settings, such the IP address range, subnets, route tables, and network gateways. To connect your VPC to AMP, you define an interface VPC endpoint to connect your VPC to AWS services. The endpoint provides reliable, scalable connectivity to AMP without requiring an internet gateway, a network address translation (NAT) instance, or a VPN connection. For more information, see What Is Amazon VPC in the Amazon VPC User Guide.

Interface VPC endpoints are powered by AWS PrivateLink, an AWS technology that enables private communication between AWS services using an elastic network interface with private IP addresses. For more information, see the New – AWS PrivateLink for AWS Services blog post.

The following steps are for users of Amazon VPC. For more information, see Getting Started in the Amazon VPC User Guide.

Creating a VPC endpoint for AMP

To begin using AMP with your VPC, create an interface VPC endpoint for AMP. The service name to choose is com.amazonaws.region.aps-workspaces. For more information, see Creating an Interface Endpoint in the Amazon VPC User Guide.

You do not need to change the settings for AMP. AMP calls other AWS services using either public endpoints or private interface VPC endpoints, whichever are in use. For example, if you create an interface VPC endpoint for AMP, and you already have metrics flowing to AMP from resources located on your VPC, these metrics begin flowing through the interface VPC endpoint by default.