RancherOS AWS Metadata

A system service to add AWS metadata on RancherOS environment

           ,/         \,
          ((__,-"""-,__))
           `--)~   ~(--`
          .-'(       )`-,
          `~~`d\   /b`~~`
              |     |
              (6___6)
               `---`

      RancherOS AWS Metadata

Supported tags and respective Dockerfile links

• 1.0.0

How to use

Add this cloud-init config on your EC2 user-data or in your rancher configuration file.

#cloud-config
rancher:
  services:
    aws-metadata:
      image: chrisenytc/rancheros-aws-metadata:1.0.0
      privileged: true
      labels:
        io.rancher.os.after: network
        io.rancher.os.scope: system
        io.rancher.os.reloadconfig: 'true'
        io.rancher.os.createonly: 'false'
        cron.schedule: "*/5 * * * *"
      volumes:
        - /usr/bin/ros:/bin/ros:ro
        - /var/lib/rancher/conf:/var/lib/rancher/conf:rw

Environment list

• AWS_AVAILABILITY_ZONE
• AWS_DEFAULT_REGION
• AWS_IAM_ROLE
• AWS_ACCESS_KEY_ID
• AWS_SECRET_ACCESS_KEY
• AWS_SECURITY_TOKEN
• AWS_AMI_ID
• AWS_AMI_LAUNCH_INDEX
• AWS_AMI_MANIFEST_PATH
• AWS_INSTANCE_ID
• AWS_INSTANCE_TYPE
• AWS_INSTANCE_ACTION
• AWS_HOSTNAME
• AWS_LOCAL_HOSTNAME
• AWS_LOCAL_IPV4
• AWS_PUBLIC_IPV4
• AWS_MAC_ADDRESS
• AWS_SECURITY_GROUPS
• AWS_RESERVATION_ID

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/chrisenytc/rancheros-aws-metadata. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

1. Fork it chrisenytc/rancheros-aws-metadata
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am "Add some feature")
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Support

If you have any problem or suggestion please open an issue here.

License

Check here.