Using User-data for Configuration of Entities and CloudEOS and vEOS Router Instances
CloudEOS and 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 CloudEOS and vEOS Router instances, AWS CloudWatch, and Cloud HA.
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 CloudEOS and vEOS Router).
EOS configuration for all interfaces can be passed in during deployment. The configuration takes effect as new interfaces attach to the CloudEOS and vEOS Router.
This table lists the start and end markers to use when configuring the EOS, AWS, Cloudwatch, and Cloud HA entities. For each specific entity, the configuration file and the location (file path) of the configuration file are given.
Entity / Configuration File / Use | Markers | File Path |
Entity: EOS File: EOS CLI configuration file Use: Configure CloudEOS and vEOS Router |
%EOS-STARTUP-CONFIG-START%
%EOS-STARTUP-CONFIG-END%
|
N/A |
Entity: AWS Logs File: aws.conf Use: Set up AWS region |
%AWS-CONFIG-START%
%AWS-CONFIG-END%
|
/mnt/flash/awslogs/aws.conf |
Entity: AWS Logs File: awslogs.conf Use: Configure logging parameters |
%AWSLOGS-CONFIG-START%
%AWSLOGS-CONFIG-END%
|
/mnt/flash/awslogs/awsconf.conf |
Entity: AWS Logs File: proxy.conf Use: Configure proxy settings |
%AWS-PROXY-START%
%AWS-PROXY-END%
|
/mnt/flash/awslogs/proxy.conf |
Entity: Cloud HA File: cloud_ha_config.json Use: Configure CloudEOS and vEOS Router for High Availability |
%CLOUDHA-CONFIG-START%
%CLOUDHA-CONFIG-END%
|
/mnt/flash/cloud_ha_config.json |