Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I use AWS PrivateLink to connect to an AppDynamics SaaS Controller?

Table of Contents

Use Case

Prerequisites

Connect your AWS Virtual Private Cloud to an AppDynamics SaaS Controller

Your Controller is in the same region as the VPC

Your Controller is in a different region than the VPC

 

Use Case

Certain organizations have policies in place that restrict traffic from traversing the public Internet. AppDynamics provides support for AWS PrivateLink, which offers private connectivity between AppDynamics Agents running in an AWS Virtual Private Cloud (VPC) and an AppDynamics SaaS Controller.

 

Customers who have both a workload running in AWS and an AppDynamics SaaS Controller hosted in AWS have the option to access AppDynamics SaaS Controllers privately via AWS PrivateLink. The customer VPC and AppDynamics SaaS Controller can reside in the same AWS region or different AWS Regions (subject to regions where AWS supports Inter-Region VPC Peering).

 

Prerequisites

Before you begin, make sure you have the following:

  • An AWS Account
  • An AppDynamics SaaS Controller in AWS
  • AWS permissions to create an interface VPC endpoint
  • AWS permissions to create AWS Transit VPC and/or VPC peering

 

You will also need to take the following steps:

  1. Contact AppDynamics Support to get the AppDynamics SaaS PrivateLink endpoint information for the target AppDynamics SaaS Controller.
  2. Contact your AWS Account Representative if you need help setting up your VPC, Transit VPC or Inter-Region VPC Peering. Note: The Transit VPC and Inter-Region VPC Peering are used if your Controller and Agents are in different AWS Regions.

 

Connect your AWS Virtual Private Cloud to an AppDynamics SaaS Controller

To integrate your AWS Virtual Private Cloud (VPC) with an AppDynamics SaaS controller, follow the instructions below for your type of AppDynamics deployment:

  • Your VPC is in the same AWS region as the target AppDynamics SaaS controller.
  • Your VPC is in a different AWS region than the target AppDynamics SaaS controller.

Note: The VPC is where your AppDynamics Agents are hosted.

 

Your VPC is in the same AWS region as the target AppDynamics SaaS Controller

If your VPC is in the same AWS region as the target AppDynamics SaaS Controller, you’ll create an interface endpoint to an endpoint service. See an overview of this configuration here.  Follow the steps below or refer to the detailed steps here.

  1. Log in to the AWS Management Console.
  2. In the Find Service search bar, enter VPC.
  3. In the VPC Dashboard left navigation pane, choose Endpoints.
  4. Click Create Endpoint.

 

Your VPC is in a different AWS region than the target AppDynamics SaaS Controller

If your VPC is in a different AWS region than the target AppDynamics SaaS Controller, you’ll need to create an AWS Transit VPC. For example, the VPC where your AppDynamics Agents are hosted (i.e. the Customer VPC in the Customer AWS region) may be in one region, but your Controller may be hosted in another region (i.e. the AppDynamics SaaS region).

  1. For Service category, choose Find service by name.
  2. For Service Name, enter the name of the AppDynamics endpoint service you should have received from AppDynamics Support. (For example: com.amazonaws.vpce.us-west-2.vpce-svc-00abc123)
  3. Click Verify. Upon success, you’ll see a Service name found message.
  4. For VPC, select the VPC where you want to create the endpoint.
  5. Click Create Endpoint.

 

This generates a request to the AppDynamics SaaS PrivateLink endpoint service over the AWS PrivateLink network. Once the request is accepted and processed by AppDynamics, the connection between your organization's endpoint and the AppDynamics endpoint will be live and you should see traffic flowing to the Controller.

 

AWS PrivateLink Screenshot.png

 

To set up and manage the Transit VPC configuration, follow the outline below or refer to AWS Transit VPC in the AWS documentation for detailed instructions.

  1. Create an AWS Transit VPC in the same AWS region as your AppDynamics Controller.
  2. Set up the VPC peering with the origin VPC where the Agents are running.
  3. Create an endpoint in the AWS Transit VPC. Follow steps mentioned in the AppDynamics Controller is in the same region as the VPC section above.
Version history
Revision #:
3 of 3
Last update:
‎04-01-2019 02:23 PM
Updated by:
 
Tags (2)
0 Kudos