Amazon is adding many services and has many resources under services. It has Compute services, Database services, Analytics services, Monitoring services etc.People of an organization are experimenting on all those services on a daily basis to understand the concepts behind those services. As this experiment or bringing the process to production, they forget to clean up the resources or think about the price of particular service. Due to such situations, suddenly at the end of the month, we notice the price of our AWS account goes high and we will be confused to know which IAM users has charged more and utilized our AWS resources. This is a serious problem for any organizations to control the spawning of resources however, we can monitor the resources based on the tags and get to know how much each IAM users charged ;).
The aws-autotag project is focussed on tagging with owner tag for the resources which is launched or created on an AWS Account for all regions.Other benefits of the project are, IAM users forgot to add a tag to the resource which will create chaos and this project will tag the resources and overcome that situation.
This project utilizes following AWS Resources( AWS Lambda, AWS S3, AWS Cloudtrail, AWS SNS(Optional ). AWS Lambda is serverless compute engine which runs our code without launching any server and relieves us from setting up the environment.You can get more details of AWS Lambda here.
Let’s start setting up the environment for aws-autotag.
Login into AWS Console.
Choose region as Oregon.
Go to AWS CloudTrail and create a new trail to send all logs files to a single Bucket.
This will create an AWS Cloudtrail “Trail” and also creates an AWS S3 Bucket, which starts pushing logs files to specified S3 bucket.
Download the role which will used in further Lambda Lab.