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 Private Link, 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).

 

There are 2 ways to do this, depending on where your agents are installed:

Virtual Private Cloud Type

Use when...

VPC

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

Transit VPC

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

 

Considerations

Creating a Transit VPC is not technically difficult or complex, but it does require additional work. It’s recommended that you consider how these requirements fit into your technical and business needs as part of planning your strategy.

 

One example of these considerations is the cost of data transfer between regions. Another example is, if you have agents across multiple regions and want to connect them into the transit VPC, it is strongly recommended to discuss your plans with AWS Support.

 

Prerequisites

Before you begin, make sure you have the following:

  • An AWS Account
  • An AppDynamics SaaS Controller in AWS
  • AWS permissions, whether you’re going to create an interface VPC endpoint, AWS Transit VPC, and/or VPC peering

 

You will also need to take the following steps:

  1. Before you choose a method, be sure you Contact your AWS Account Representative if you need help setting up your VPC, Transit VPC or Inter-Region VPC Peering.

  2. Contact AppDynamics Support to get the AppDynamics SaaS PrivateLink endpoint information for the target AppDynamics SaaS Controller.

    You will need: 
    • AWS Account number you want to use for this connection 
    • AppDynamics controller endpoint name (e.g., customer.saas.appdynamics.com) you want to connect to

 

How do I connect my AWS VPC to an AppDynamics SaaS Controller?

The method for connecting an AWS VPC to a SaaS Controller depends on whether the two are in the same or different AWS regions.

 

 

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. 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.

 

VPC 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).

AWS PrivateLink Screenshot.png

 

Inter-region VPC Peering

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

 

  1. Create an AWS Transit VPC in the same AWS region as your AppDynamics Controller.

  2. Request a VPC Endpoint from AppDynamics. You will need to provide your AWS account number to the AppDynamics representative. Then, AppDynamics will provide the Endpoint ID for your controller.

  3. From the AWS Management Console,go to Service Category, and choose Find service by name.

  4. For Service Name, enter the name of the AppDynamics endpoint service you received from AppDynamics Support in step 2, above. 
    (For example: com.amazonaws.vpce.us-west-2.vpce-svc-00abc123)
  1. Click Verify. Upon success, you’ll see a Service name found message.

  2. For VPC, select the VPC where you want to create the endpoint.

  3. 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.

Version history
Revision #:
7 of 7
Last update:
‎03-24-2020 09:11 AM
Updated by:
 


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.