Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically add AWS tags to servers #11627

Closed
russjones opened this issue Mar 31, 2022 · 1 comment · Fixed by #12593
Closed

Automatically add AWS tags to servers #11627

russjones opened this issue Mar 31, 2022 · 1 comment · Fixed by #12593
Assignees
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements needs-rfd This issue should have RFD before implementation starts

Comments

@russjones
Copy link
Contributor

Convert AWS tags attached to a instance into labels. This will allow users to reuse existing discovery/inventory information in AWS with Teleport as well.

On possible implementation is upon startup of a ssh_service, query the metadata endpoint for all tags associated with that instances and automatically add all tags as labels. Also attach instance name as a label.

https://aws.amazon.com/about-aws/whats-new/2022/01/instance-tags-amazon-ec2-instance-metadata-service/

Potentially look into doing the same for all resources, not just for SSH servers.

@russjones russjones added the feature-request Used for new features in Teleport, improvements to current should be #enhancements label Mar 31, 2022
@russjones russjones changed the title Automatically add AWS tags as labels to SSH servers Automatically add AWS tags to servers Mar 31, 2022
@webvictim
Copy link
Contributor

There is one further requirement as part of this request:

  • allow the Teleport nodename displayed in the web UI/tsh ls to be set from an EC2 tag, overriding the default (i.e. hostname)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements needs-rfd This issue should have RFD before implementation starts
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants