Arista vEOS, Configuration Manual, Page: 57 / 128

3. Obtain the Subnet ID and the route table ID that corresponds to the subnet in which the vEOS Router instance
resides.
Example:
Subnet ID (subnet-1c68b744).
Route table ID (rtb-934cf9f7).
4. Edit the route table entry so that it points to the corresponding interface of the vEOS Router in that subnet.
Example
To reach any subnet other than 10.2.0.0/24, enter the Target to be the network interface ID of the locally
connected interface of the vEOS Router.
5. (Optional) Repeat steps 2 through 4 to modify route table entries for additional vEOS Router instances.
Configure the AWS CloudWatch Logs Agent (see Configuring the AWS CloudWatch Logs Agent on page 52).
Configuring the Agent ensures that the vEOS Router logs publish to AWS.
Using User-data for Configuration of Entities and vEOS Router Instances
vEOS supports configuration of startup-configuration, AWS CloudWatch, and Cloud HA through the use of
user-data. Because user-data can be used to pass in configurations; administrators can take advantage of this
feature to quickly configure vEOS Router instances, AWS CloudWatch, and Cloud HA.
Note: It is recommended to test vEOS Router configurations on a vEOS Router or EOS device before
using them to deploy a new vEOS Router.
Requirements for Uploading User-data
To ensure that the user-data is accepted on upload, make sure the user-data meets the following requirements:
• The configuration must be separated by start and end markers.
• Markers are required at the beginning of the line.
• You must upload either text or configuration files (these are the types of files supported by vEOS Router).
EOS configuration for all interfaces can be passed in during deployment. The configuration takes effect as new
interfaces attach to the vEOS Router.
List of Start and End Markers to Use
57
Using vEOS Router on the AWS Platform