Arista vEOS, Configuration Manual, Page: 53 / 128

#configuration here
%AWS-CONFIG-END%
%AWSLOGS-CONFIG-START%
#configuration here
%AWSLOGS-CONFIG-END%
%AWS-PROXY-START%
#configuration here
%AWS-PROXY-END%
Note: Restart awslogs using sudo systemctl restart awslogs under bash. The reconfiguration does not
take effect until awslogs restarts.
vEOS Router log filenames
By default, the hostname of the vEOS Router instance is the filename of all vEOS Router logs for that instance.
Network Configuration Tasks for vEOS Router Instances
Complete additional configuration tasks to ensure that the vEOS Router instances launched have the required
networking configuration. The configuration tasks include creating the additional network interfaces required
by the topology, attaching the new interfaces to vEOS Router instances, and configuring the route table of the
AWS Specific Cloud Router.
Creating the Additional Network Interfaces
Creating the additional network interfaces required for the topology ensures that there are interfaces available
to attach to vEOS Router instances. When creating the new network interfaces, there is the option of using the
subnet and security groups that were automatically assigned to the instance, or specify a different subnet and
security groups for the instance.
Pre-requisites:
To use the existing subnet and security group for the vEOS Router instance, make sure to have the following
information:
• Subnet ID
• Names of the security groups
Obtain this information by viewing the instance details.
Procedure
Complete these steps to create network interfaces.
1. Go to the EC2 Dashboard.
2. In the NETWORK & SECURITY menu on the left part of the page, select Network Interfaces.
The page refreshes to show all of the current network interfaces.
53
Using vEOS Router on the AWS Platform