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

Tag Terraform AWS resources using a label module #15

Open
matthew-a-carr opened this issue Feb 2, 2021 · 4 comments
Open

Tag Terraform AWS resources using a label module #15

matthew-a-carr opened this issue Feb 2, 2021 · 4 comments

Comments

@matthew-a-carr
Copy link
Contributor

matthew-a-carr commented Feb 2, 2021

Why

We need a way of tagging our AWS modules in a consistent way to help manage, organise, search for, and filter resources. The Cloud Posse Label Module is the most popular label module from the Terraform Registry and has great supporting documentation.

This will also help us start to think about defining other required environments: UAT, Production.

How

  • Create a tags.tf file and create label modules for our AWS resources
  • Read through the Cloud Posse Label Module documentation for guidance on tagging strategies. I.e: When should you define/re-use a label definition.
  • Tag required resources using created labels

Links

@matthew-a-carr
Copy link
Contributor Author

@paulgutman FYI, please could you add a comment on here as to what tags you would like to see on all beacon resources created within AWS

@paulgutman
Copy link

I think we should have the following tags
Service
Environment
owner

Where
Service is Beacons
Environment is Dev, UAT or Production
Owner - email address of the Beacons team

Happy to discuss

@matthew-a-carr
Copy link
Contributor Author

@paulgutman thank you, all that makes sense.

Currently, we have been using the environments: dev, staging and production. Do you have a preference of using UAT over staging - there's no additional effort at this point to change to using UAT if you would rather us?

@paulgutman
Copy link

paulgutman commented Mar 17, 2021 via email

@zackads zackads mentioned this issue Apr 20, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants