This is an open-source tagging solution for AWS. Deploy auto tag to lambda and set up CloudTrail and have each of your resources tagged with the resource who created it. It was written by GorillaStack.
Automatically tagging resources can greatly improve the ease of cost allocation and governance.
Within 5-7 minutes of creating a supported resource type, CloudTrail will write to s3 logs, which triggers our AutoTag code to tag the resource with the ARN of it's creator.
We have created a CloudFormation template that creates all the resources required for AutoTag.
We also host each release of AutoTag in public s3 buckets in each region, such that all you have to do is install the CloudFormation template.
Through the console
- Go to the CloudFormation console
- Click the blue "Create Stack" button
- Select "Upload a template to Amazon S3", choosing the downloaded CloudFormation template, then click the blue "Next" button
- Name the stack "autotag" - this part is important, as the autotag code need to find the created resources through the API
- In the parameter section:
- CloudTrailBucketName: Name the S3 bucket that the template will create. This needs to be unique for the region, so select something specific
- CodeS3Bucket: As mentioned, we have a version of AutoTag in each region, to make deployment easy regardless of what region you are deploying your CloudFormation template. Edit this parameter to match your region. It should have the following pattern:
- CodeS3Path: This is the version of AutoTag that you wish to deploy. The default value
autotag-0.3.0.zipis the latest version
Supported Resource Types
Right now Auto Tag, supports the following resource types in AWS:
- EC2 instances
- RDS instances
- S3 buckets
- EBS volumes
- Elastic Map Reduce clusters
- Internet Gateways
- AutoScaling Groups
- VPC Subnets
- Data Pipelines
If you have questions, feature requests or bugs to report, please do so on the issues section of our github repository.
If you are interested in contributing, please get started by forking our github repository and submit pull-requests.
When the repository was first authored, this was not supported by the lambda node version (v0.10). Even now with version 4.3 support, we still need to transpile code to es5 for compatibility, as not all language features are available (e.g. import etc).
Support for es5
If you still wish to transpile to es5 for older node versions run the following:
$ grunt run:babel # runs interactively, issue ^C to existing
Export the generated es5
lib/ directory to AWS rather than the es6