Deploy Aviatrix Controller LAB
Aviatrix Sandbox Starter is a comprehensive tool to build Cloud Networks in minutes. It could also be used to just deploy the Aviatrix Controller in AWS with metered option.
- Docker installed and left running
- AWS Access Key ID and Secret Access Key
- Key Pair name from AWS Ohio region
- Subscribe to Aviatrix metered software from AWS Marketplace
- This procedure works the best for a brand new Aviatrix Controller deployment
Before launching the UI, run the following commands in the CLI console.
[shahzad-ali ~ % docker volume create TF [shahzad-ali ~ % docker run -v TF:/root -p 5000:5000 -d aviatrix/sandbox-starter
Now in your web browser type http://0.0.0.0:5000/ and then follow the workflow.
The standard workflow will deploy the controller in your AWS account.
It is recommended to provide a corporate email address to request for Aviatrix CoPilot test license In the future, we might add the option to launch Controller in other Clouds
The Controller launch process takes about 10 min to complete. After the Controller is launched, you can see its public IP address in the "Debug" option. Now you can log in to the Aviatrix Controller using the admin user-name and the password you specified.
Cost Calculator, Troubleshooting, detailed deployment steps in Azure, and other resources are available at the following link.
Terraform to Deploy Aviatrix Controller
One can also deploy an Aviatrix Controller using the terraform. Here are the instructions and git-hub repository
First of all I created an EC2 in the AWS' VPC. But when i create the EC2, AWS tell me to create a key that will allow me to connect to the EC2... i don't understand everything, so i just named a key "my name" and then the EC2 was created.
Next, i try to deploy Aviatrix Controller. When i get to the parameters where i have to choose VPC and subnet, i can't choose the keypair "Controller" as seen in the video, it shows me the key "my name" that i created before. Is this normal ?
Another thing that i noticed, my EC2 is configured "t2.large" not "t3.large", do i have to change it in the parameters when i deploy the controller ? or do i have to create an EC2 t3.large ?
Secondly, i just want to know if i pay the Aviatrix Controller that will be running in my AWS' VPC after deploying it ? I'm trying to practise in Cloud architecture (as shown in Aviatrix Controller Deployment video) that's why i want to know, im not really using the VPC.
Thanks for listening.