AWS Startup Guide

Welcome to getting started on AWS! This guide takes you through the 3 steps to launch your Aviatrix Controller instance:

  1. Subscribing to the AMI (Amazon Machine Image).
  2. Launching the Controller with CloudFormation.
  3. Onboarding your AWS account in your Aviatrix Controller.

When complete, you’ll be ready to deploy use cases.

3-step

Note

You can also watch a video for this startup guide.

Important

The Aviatrix Controller must be launched by a Cloudformation script provided by Aviatrix. Follow the instructions in this document to launch the Controller. Do not launch the Controller instance from the AWS Console.

Subscribing to an Aviatrix AMI

If you have already subscribed the Metered AMI on AWS Marketplace, skip this step and proceed to the Launch the Controller with CloudFormation section.

  1. To subscribe to the AMI, click the AMI link below to take you to the AWS Marketplace.

Aviatrix Secure Networking Platform Metered with Copilot

  1. Click Continue to Subscribe. Subscribing means that you can begin deploying the software in later steps via the CloudFormation template.

    AMI_24x7_copilot

  2. Click Accept Terms. Then, return to this guide and continue. Do not proceed to Continue to Configuration.

Launching the Controller with CloudFormation

1. Click the link below to take you to the CloudFormation page on the AWS Console with the pre-loaded template. Follow the instructions in the next steps to run the Cloudformation script.

CloudFormation for Aviatrix Secure Networking Platform Metered with Copilot

Other Aviatrix Products

CloudFormation for Aviatrix Secure Networking Platform Metered with Copilot

  1. If you have not logged in, you will be prompted to log in to the AWS console.
  2. Change to the region where you would like to install the Aviatrix Controller on the CloudFormation page. Note the CloudFormation is already loaded.
  3. Click Next.
cft-next
  1. Fill in the following fields:
  • The Stack name,
  • Select a VPC in the dropdown menu,
  • Select a public subnet in that VPC (Go to AWS VPC console to make sure the public subnet is indeed in your selected VPC. A public subnet must have a default route point to IGW in its associated VPC route table. Read this link if you do not know what public subnet is.)
  • And a keypair (Read how to create a keypair to create a keypair in AWS EC2 console if this field is blank.)
imageCFSpecifyDetails

Note

The Aviatrix Controller must be launched on a public subnet. If this is the first time you launch an Aviatrix Controller, select the default setting New for IAM Role Creation. If an Aviatrix IAM role has been created before, select aviatrix-role-ec2 for IAM Role Creation. The Aviatrix Controller instance is termination protected.

  1. Select instance size. Set the Controller Size to t3.large and keep the IAM role creation at New unless you have already created the Aviatrix IAM roles.

  2. Click Next.

  3. Click Acknowledge.

  4. Mark the checkbox next to “I acknowledge that AWS CloudFormation ...” and then click Create.

    imageCFCreateFinal

  5. When the stack creation completes (the status changes to CREATE_COMPLETE), click on the Outputs tab. You will need to use the values displayed when you onboard a primary access account for AWS in your Aviatrix Controller. (You might have to refresh your browser window and/or AWS console to see your Stack show up and the Status to be updated).

imageCFComplete

Onboarding your AWS account in your Aviatrix Controller

Now that Aviatrix Controller instance has been launched, log in to your Controller and go through the onboarding process.

  1. To access the Controller, open a browser window to https://AviatrixControllerEIP, where AviatrixControllerEIP can be found in the Stack Outputs. You can also find the Controller instance EIP by going to AWS EC2 console, click the Controller instance, and locate its public IP address.

Tip

You may receive a warning that the connection may not be secure. This is because the certificate is self-signed by the Controller. It is safe to continue to the page.

imageControllerBrowserWarning
  1. Log in to the Controller:
  • Username - admin
  • Password - the AviatrixControllerPrivateIP from your AWS account. You can find this IP address in the Outputs section of the CloudFormation stack or by going to AWS EC2 console, clicking the Controller instance, and locating its private IP address.
  1. Enter your email address. This email will be used for alerts as well as password recovery if needed.
  2. When prompted, change your password. Make sure this password is secure.
  3. Click Run. The Controller will upgrade itself to the latest software version. Wait for a few minutes for the process to finish.

Tip

The Controller upgrade takes about 3-5 minutes. Once complete, the login prompt will appear. Use the username “admin” and your new password to login.

If you wish to run a custom version, consult the Aviatrix Support team before attempting it.

  1. When you log into the Controller, the Onboarding page should open. On the Onboarding page, select AWS.

    imageOnboardAws

  2. Set up a primary access account for AWS using the following information:

  • The Controller instance’s AWS 12-digit account ID.

Check out this link if you have questions regarding Aviatrix access account.

Fill out the fields as follows: (The AWS Account Number can be found at the Stack Outputs section or get from this link.)

Field Expected Value
Account Name Enter a name that is unique on the Controller. Example name: AWSOpsTeam.
AWS Account Number The Controller instance’s 12-digit AWS account number. It can be found in the Stack Outputs section AccoundId.
IAM role-based Check this box.
  1. Once complete, click Create at the bottom of the form.

Occasionally, you may need to update your IAM policy. See this document to audit your policy to check for updates and update it if necessary.

Next: Start a Use Case

Congratulations!

You are now ready to deploy use cases. Here are some of the things you can do:

Important

Any resources created by the Controller, such as Aviatrix gateways, route entries, ELB, SQS queues, etc, must be deleted from the Controller console. If you delete them directly on an AWS console, the Controller’s view of resources will be incorrect which will lead to features not working properly.

For technical support, please open a support ticket at Aviatrix Support Portal.

Enjoy!

Additional Information for Controller