Launching CloudEOS and vEOS Router Instances Using AWS CloudFormation
Using AWS CloudFormation to launch CloudEOS and vEOS Router instances involves creating a CloudFormation stack to use to launch the instance. The created stack provides the base configuration for the instance. As part of this task, select a stack template, which defines the base configuration of the instance.Make sure to select the stack template that provides the resources required for the instances that are launching. Templates can be obtained from https://github.com/aristanetworks. For more information about AWS CloudFormation stacks and using stack templates, refer to the AWS documentation (see https://aws.amazon.com/documentation/cloudformation/).
Complete these steps to launch CloudEOS and vEOS Router instances using AWS CloudFormation.
- Log in to the Amazon Management Console.
The CloudFormation page appears showing the current stacks available to use.
Click on the
Create Stack button.
The page refreshes to show the templates that are available to use to create a new stack.
nic template for upload, and then click on the
Note: Templates can be found in the docs directory. Press Select to choose the desired AMI.The page refreshes showing the options for specifying the details for the stack.
Enter the Stack Name, Subnet IP Block for each interface, VPC ID,
KeyPair Name, UserData in base64 format, AMI ID. (To convert UserData from text
to base64 format, use a base64 command on MacOS or Linux machine.)
# base64 %EOS-STARTUP-CONFIG-START% hostname myhost %EOS-STARTUP-CONFIG-END% <Press CTRL+D> JUVPUy1TVEFSVFVQLUNPTkZJRy1TVEFSVCUKaG9zdG5hbWUgbXlob3N0CiVFT1MtU 1RBUlRVUC1DT05GSUctRU5EJQo=
- Review the details and make changes if needed.
Create button to create the stack.
Wait for the stack creation to complete. Resources created as part
of the stack creation process can be viewed in the Resource tab.
Click on the CloudEOS and vEOS Router instance ID to view the status of CloudEOS and vEOS
Router instance. The instance ID is shown in the Physical ID column of the
AWS cannot auto-assign a public IPv4 address if an EC2 instance is launched or started from the stopped state with multiple network interfaces attached to it. In such cases, the user cannot connect to the instance over IPv4 unless an Elastic IP address is assigned to the primary network interface (eth0). If the user does not want to associate an Elastic IP address with the CloudEOS and vEOS Router instance, then it is recommended to attach any additional interface only when the instance is in running state and never to stop and start your instance from thereon. The user may reboot the instance either from AWS console or from within CloudEOS and vEOS Router using the CLI or bash commands because the instance reboot does not cause the public IPv4 address to be released as opposed to instance stop. To associate Elastic IP address to your instance or primary network interface, refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html