Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Given a company with multiple teams using EC2, what are some common or practical strategies for setting some TAG guidelines when instances or ami's are created so that resources can be more easily searched and filtered?

share|improve this question
CloudFormation automatically tags all the resources created so it's a nice way to keep track of things. – Drew Khoury Nov 24 '13 at 10:42

Initially we tried making tags mandatory for everyone creating the VM to use tags in the following format.

name [name of the person creating the vm] 
project [project for the vm created for] 
team [team the VM belongs to]
purpose [what is the VM used for] 
application [what application will be served on the vm]

This worked quite well. We improvised by creating a simple PHP form what would call EC2 API. The PHP form was validated so that all entries are valid, consistent and mandatory. Team and projects had list boxes.

Using simple EC2 api's, we would generate reports based on tags

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.