Connect to Dynatrace using AWS PrivateLink

AWS PrivateLink lets you connect your applications directly to the Amazon VPC service, so that traffic never leaves the AWS cloud. You can use PrivateLink to connect your monitored hosts to the Dynatrace VPC (Virtual Private Cloud) endpoint. Dynatrace monitoring traffic is always encrypted and secure, yet PrivateLink provides even greater security, stable connectivity, and a reduction in traffic costs.

The primary use case for PrivateLink with Dynatrace is connectivity for monitored applications running in AWS VPCs. Dynatrace will not use Interface VPC endpoints to access AWS CloudWatch and services such as EC2 or ELB.

PrivateLink connectivity overview

However, it’s also possible to use AWS VPCs for on-premises applications, provided that you use DirectConnect or VPN Gateway to connect your network to a VPC in a given region.

PrivateLink connectivity overview

The interface VPC Endpoint (PrivateLink) must be created in the VPC that's located in the same region as the Dynatrace environment. However, you can still monitor hosts running in a different VPC, including a VPC located in a different region.

VPC in a different region

For more information, see VPCs in different AWS regions

Dynatrace API provides you with the endpoint that enable you to set up your PrivateLink without assistance from Dynatrace. Set up the PrivateLink connection in these steps:

  1. Add your AWS account to your Environment allowlist
  2. Get the VPC Endpoint service name for your Environment
  3. Create the VPC Endpoint
  4. Override the VPC DNS configuration
  5. Enable PrivateLink communication in your Environment
  6. optional Override DNS configuration in other regions if you monitor hosts there

Prerequisites

Before you begin, make sure you have the following:

1. Add your AWS account to the allowlist

Add your AWS account ID to your Environment allowlist for AWS PrivateLink connection. Use the Dynatrace AWS PrivateLink API. For example, run the following call:

curl -X PUT "https://{EnvId}.live.dynatrace.com/api/config/v1/aws/privateLink/whitelistedAccounts/{AwsId}" \
-H "accept: application/json; charset=utf-8" \
-H "Authorization: Api-Token {ApiToken}" \
-H "Content-Type: application/json; charset=utf-8" -d "{\"id\":\"{AwsId}\"}"

Replace:

After a successful call, Dynatrace API returns the following response where 123456789012 is your AWS Account ID:

HTTP 201
{
"id": "{123456789012}"
}

2. Get VPC Endpoint service name

You'll need the VPC Endpoint service name for your Dynatrace Environment when you create the VPC Endpoint for your connection. Run the following Dynatrace API call to determine the VPC Endpoint service name:

  curl -X GET "https://{EnvId}.dynatrace.com/api/config/v1/aws/privateLink" \
  -H "accept: application/json; charset=utf-8" \
  -H "Authorization: Api-Token {ApiToken}"

After a successful call, Dynatrace API returns the following response containing the VPC Endpoint service name for your Environment. Note it down as you'll need it when creating the stack. The VPC Endpoint service name doesn't change, so you need to perform this action once.

HTTP 200
{
"enabled": false,
"vpcEndpointServiceName": "com.amazonaws.vpce.us-west-2.vpce-svc-12a34bc5defgh678i"
}

3. Create VPC Endpoint

Create an interface VPC Endpoint for one of the supported regions using either the AWS console or an API call. For more information, see Interface VPC Endpoints (AWS PrivateLink) in the AWS doc.

Dynatrace currently supports the following AWS regions and corresponding availability zones:

AWS Region code Availability zone names Availability zone IDs
us-east-1 us-east-1a, us-east-1b, us-east-1c use1-az2, use1-az4, use1-az6
us-west-2 us-west-2a, us-west-2b, us-west-2c usw2-az1, usw2-az2, usw2-az3
eu-central-1 eu-central-1a, eu-central-1b, eu-central-1c euc1-az1, euc1-az2, euc1-az3
eu-west-1 ue-west-1a, ue-west-1b, ue-west-1c euw1-az1, euw1-az2, euw1-az3
ap-southeast-2 ap-southeast-2a, ap-southeast-2b, ap-southeast-2c apse2-az1, apse2-az2, apse2-az3
  • In the AWS console, select one of the supported regions, go to VPC service, section Endpoint, and click Create Endpoint to create your PrivateLink endpoint.
  • Select Find Service by name as the service category, enter the service name you determined in the previous step (for example com.amazonaws.vpce.us-west-2.vpce-svc-12a34bc5defg678ij) and click Verify.
  • Configure the VPC, subnets, and security group settings. The security group needs to permit incoming traffic on port 443. If you use more than one VPC for your monitored applications, repeat this step for each VPC.

4. Override the DNS name of your Environment

Create a private DNS so that you can transparently connect to Dynatrace using the PrivateLink you’ve created using the CloudFormation template below. See Creating a Stack on the AWS CloudFormation Console in the AWS doc for more information.

  1. Determine the VPC Endpoint DNS name and its Hosted Zone ID to be used as a stack parameters. In the Management console, go to Networking & Content Delivery section > VPC > Endpoints where you should find the endpoint associated with a given service name. Select this endpoint and the details section will display DNS Names. The DNS Name is constructed as VPC-Endpoint-DNS-name(Hosted-zone-ID).

Use the first entry as the source for VPC Endpoint DNS name and its Hosted Zone ID.

  1. Start the Create Stack wizard.

  2. Select the stack template. Use the file hosted on Dynatrace GitHub as the stack template.

  3. Specify stack parameters. In the Specify stack details page, provide the following parameters you determined earlier:

  • Your Dynatrace Environment ID
  • VPC ID - the identifier of the VPC where you created the VPC endpoint
  • VPC Endpoint DNS name
  • Hosted Zone ID of VPC Endpoint DNS

Specify stack details screen based on the template provided by Dynatrace

  1. Click Next to go to Options, click Next step to review your stack, click Create stack to launch the stack running your private DNS.

Use AWS PrivateLink API to enable the PrivateLink communication. Enabling PrivateLink communication on your Environment makes OneAgents and Environment ActiveGates use only the domain you defined in Step 4 to connect to the service and won’t try to discover alternative endpoints for the connection. Run the following Dynatrace API call:

curl -X PUT "https://{EnvId}.dynatrace.com/api/config/v1/aws/privateLink" \
-H "accept: application/json; charset=utf-8" \
-H "Authorization: Api-Token {ApiToken}" \
-H "Content-Type: application/json; charset=utf-8"
-d "{\"enabled\":true}"

Replace:

After a successful call, Dynatrace API returns the HTTP 204 code.

VPCs in different AWS regions

If you monitor hosts from a VPC located in a different region, Such a VPC can be connected using VPC peering, Transit Gateway or VPN Gateway. Note that the DNS override must be present in every VPC that has hosts monitored by Dynatrace.

Create a Private Route 53 Hosted Zone in each VPC, or associate all the VPCs with a single private hosted zone.

For example, you have a Dynatrace environment in Sydney, that is the ap-southeast-2 region, but the monitored hosts are running in a VPC in Tokyo, ap-northeast-1 region. In order to connect Dynatrace OneAgents via PrivateLink you need to perform the following steps:

  1. Make sure he you have a VPC configured in Sydney.
  2. Create an interface VPC Endpoint in the Sydney VPC.
  3. Establish an inter-region VPC peering between the Tokyo and Sydney VPCs.
  4. Create the CloudFormation stack based on a template obtained above with the DNS override for the Tokyo VPC.

You can use a single endpoint for multiple VPCs, but each VPC needs to be connected using the VPC-peering and needs a DNS override.

While you can connect OneAgent via PrivateLink, we recommend that you use an ActiveGate. If you download the OneAgent installer via ActiveGate, it already contains a pre-configured ActiveGate endpoint and doesn’t need connectivity to the PrivateLink endpoint. For example, if you have an environment called xyz12345.live.dynatrace.com and ActiveGate running in a local network at https://172.31.1.5:9999, modify the OneAgent installer download URL by replacing the environment domain with the ActiveGate domain and adding environment context in the path, for example:

wget --no-check-certificate -O Dynatrace-OneAgent-Linux.sh https://172.31.1.5:9999/e/xyz12345/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=<api token>&arch=x86&flavor=default

The Dynatrace server must be aware of the ActiveGate at the time of OneAgent installer download.

Multi-environment ActiveGates

PrivateLink connectivity isn't supported by ActiveGates that are configured for multi-environment support. To use PrivateLink for multiple environments, each environment needs a dedicated Environment ActiveGate.

What happens next?

Once you’ve completed these steps, all instances of ActiveGate or OneAgent installed in your VPC will begin using PrivateLink. Thanks to the DNS override, using PrivateLink is transparent. No process restart is required.

To verify that your PrivateLink endpoint is really used:

  • Try resolving your Dynatrace environment domain from an instance running in your VPC. The domain should resolve to a private IP addresses in your VPC, for example:
nslookup xyz12345.dynatrace.com
cluster-us-west-2-prod-us-west-2-oregon.live.ruxit.com  canonical name = vpce-0c79a2e58780e4b62-x8vhytdj.oregon-1.vpce.dynatrace.com.
Name:   vpce-0c79a2e58780e4b62-x8vhytdj.oregon-1.vpce.dynatrace.com
Address: 172.31.41.143
Name:   vpce-0c79a2e58780e4b62-x8vhytdj.oregon-1.vpce.dynatrace.com
Address: 172.31.28.144
Name:   vpce-0c79a2e58780e4b62-x8vhytdj.oregon-1.vpce.dynatrace.com
Address: 172.31.13.64
  • If the domain resolves to a public IP address, double-check your DNS and VPC configurations. The private DNS region (EndpointRegion) and VPC ID (Vpcid) must match the corresponding instance settings. The VPC must also support privately hosted zones, so enableDnsHostnames and enableDnsSupport must be set to true.
  • If the domain name resolves as expected, but OneAgent can’t connect to the endpoint on port 443, check if incoming traffic on port 443 is permitted in the security group settings associated with your PrivateLink endpoint.
  • You can also enable VPC flow logs for the network interfaces of your instances or the network interfaces associated with PrivateLink. By checking the IP addresses in the logs, you can verify if an instance is communicating with a private endpoint. If you see REJECT entries instead of ACCEPT, then most likely the traffic is blocked by your security group settings.