- Introduction
- Architecture
- Pre-requisites and Assumptions
- Amazon Web Services
- ThousandEyes
- Deployment
- Verification
- Additional Resources
Introduction
ThousandEyes’ flexibility allows you to place Enterprise Agents virtually anywhere your company has a network presence. However, deploying these Agents in cloud environments like Amazon Web Services (AWS) can introduce unwanted administrative and operations overhead.
One common example of this is trying to get an -based Enterprise Agent deployed in AWS, which is not natively supported by the cloud provider. This guide will show you how to import the ThousandEyes Open Virtual Appliance (OVA) into an AWS Machine Image (AMI) to reduce the time spent in the agent deployment process.
Architecture
The rule of thumb for an ideal agent placement is to deploy the Virtual Machine as close to the resources handling the workflows as possible. Here are a few examples:
- Connectivity with S2S VPN
- Connectivity with Direct Connect
Pre-requisites and Assumptions
This article assumes you have the following knowledge, resources & access:
Amazon Web Services
- An existing AWS Account
- An existing VPC and Subnet capable of hosting the ThousandEyes Agent
- An existing S3 bucket to store the ThousandEyes OVA file
- The user running this process requires the following permissions in IAM:
- AWSMigrationHubFullAccess
- AWSMigrationHubOrchestratorConsoleFullAccess
- AWSMigrationHubOrchestratorPlugin
- AWSMigrationHubOrchestratorInstanceRolePolicy
ThousandEyes
- An existing ThousandEyes Organization
- Your ThousandEyes Account Group Token
Deployment
1. Log in to your ThousandEyes Organization
2. Navigate to the Network & App Synthetics > Agent Settings section
3. Click on the Add New Enterprise Agent button
4. In the Appliance section, click on the Download – OVA button
5. With the OVA file downloaded, log in to your AWS account.
6. Navigate to your S3 bucket and click on Create folder
7. Name and create the folder by entering your desired folder name and then click Create folder.
Critical Note! To ensure proper function the folder name MUST begin with the prefix: migrationhub-orchestrator-vmie
Example: migrationhub-orchestrator-vmie-TEVA.
8. Inside the newly created folder, click Upload
9. Click Add files, select the OVA file downloaded from step 4, and then click Upload.
10. Within AWS, navigate to Migration Hub and select Workflows under Orchestrate
11. Click on Create workflow
12. Within the Workflow templates section, search with the keyword ‘virtual’, locate and select ‘Import virtual machine images to AWS’ and click Next.
13. Give the import process a name, select the folder that holds the OVA within the S3 Bucket and click Next.
Success Tip: Remember to select the folder containing the OVA. While the UI gives you the option to select the OVA file itself, doing so will result in an error.
14. Validate the workflow details and click Create.
Note: Allow time for the workflow creation to finalize before moving to the next step. Once the status shows as Not Started, you are ready to proceed.
15. Select the Workflow name from step 13, then click Run to start the import process.
16. Allow the import process to complete. This can take up to 30 minutes depending on size.
17. Navigate to EC2 and select AMIs under Images, you should see your newly created AMI in the list; click on Launch instance from AMI.
18. Fill out the following fields and click Launch instance, allowing time for the instance to be created once entered:
- Name
- Instance Type
- We recommend a 2vCPU, 2 GiB Memory instance
- Key Pair
- Used for SSH access after deployment
- VPC
- Subnet
- You may use a Public or private subnet.
- If using a private subnet it must be one with a NAT Gateway as the agent will require internet connectivity.
- Security Group
- Review our required firewall rules here.
19. Go to the newly created instance and verify it is running.
20. Access the Enterprise Agent by inputting the instance’s public or private IP in your browser (depending on your environment), which will trigger the Agent’s login screen.
21. Now you can configure the Agent just as you would a regular Virtual Appliance.
Note: More information on the configuration process here.
Verification
1. After you complete the Agent’s configuration, verify that you see the new agent registered on the ThousandEyes platform (usually takes about 3-5 minutes).
2. Congratulations, your new Agent is now ready to run tests!
Security Consideration Warning: While the new VM will inherit the Security Groups assigned to the VPC, we always recommend verifying that access control is properly configured.