Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/GorillaStack/retro-tag
Retrospectively tag AWS resources so you can work out who created them
https://github.com/GorillaStack/retro-tag
aws aws-tags cloudtrail tagging
Last synced: about 2 months ago
JSON representation
Retrospectively tag AWS resources so you can work out who created them
- Host: GitHub
- URL: https://github.com/GorillaStack/retro-tag
- Owner: GorillaStack
- License: gpl-3.0
- Created: 2019-07-19T01:55:43.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2023-12-05T17:20:26.000Z (about 1 year ago)
- Last Synced: 2024-08-02T22:22:40.460Z (5 months ago)
- Topics: aws, aws-tags, cloudtrail, tagging
- Language: Ruby
- Size: 81.1 KB
- Stars: 104
- Watchers: 9
- Forks: 10
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Audit: audit_tag.rb
Awesome Lists containing this project
README
# Retro Tag
[](/LICENSE)
[](https://www.gorillastack.com)
Retro Tag helps you retrospectively tag resources with the ARN of the user that created them and the creation date/time using the [Auto Tag](https://github.com/GorillaStack/auto-tag) engine, and supports tagging across multiple regions and across AWS accounts.
This is designed to solve the problem of [Auto Tagging](https://github.com/GorillaStack/auto-tag) existing resources in your environments.
## About
Retro Tag uses the log data in your AWS CloudTrail S3 bucket logs to gather information about the "who" and "when" for each of your AWS existing resources. Using this information, engineers can determine which resources are required, which are not, and can cleanup the resources, or improve their tagging.
## Installation
The installation consists of a `CSV` created from AWS Athena scanning
the CloudTrail S3 bucket, a single `Main` CloudFormation Stack with the
AutoTag Lambda function in the same account as the CloudTrail S3 Bucket,
and a `Role` CloudFormation Stack deployed to each additional account where tagging
will be applied.
### Query CloudTrail logs using AWS Athena
Use AWS Athena to scan your history of CloudTrail logs in S3 and produce
a CSV file of events that we can process.
WARNING: You are charged for AWS Athena based on the amount the data that is scanned.
#### Table Query
Login to the AWS account and region where your CloudTrail logs S3 bucket is located and bring up the Athena service. You'll probably need to create a unique table for each AWS account in the S3 bucket.
Update the table name, S3 bucket, S3 path including the AWS account ID to query.
```sql
CREATE EXTERNAL TABLE IF NOT EXISTS my_table_name (
eventversion STRING,
userIdentity STRUCT<
type:STRING,
principalid:STRING,
arn:STRING,
accountid:STRING,
invokedby:STRING,
accesskeyid:STRING,
userName:STRING,
sessioncontext:STRUCT<
attributes:STRUCT<
mfaauthenticated:STRING,
creationdate:STRING>,
sessionIssuer:STRUCT<
type:STRING,
principalId:STRING,
arn:STRING,
accountId:STRING,
userName:STRING>>>,
eventTime STRING,
eventSource STRING,
eventName STRING,
awsRegion STRING,
sourceIpAddress STRING,
userAgent STRING,
errorCode STRING,
errorMessage STRING,
requestParameters STRING,
responseElements STRING,
additionalEventData STRING,
requestId STRING,
eventId STRING,
resources ARRAY>,
eventType STRING,
apiVersion STRING,
readOnly STRING,
recipientAccountId STRING,
serviceEventDetails STRING,
sharedEventID STRING,
vpcEndpointId STRING
)
ROW FORMAT SERDE 'com.amazon.emr.hive.serde.CloudTrailSerde'
STORED AS INPUTFORMAT 'com.amazon.emr.cloudtrail.CloudTrailInputFormat'
OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'
LOCATION 's3://my-cloudtrail-bucket/dev/AWSLogs/11111111111/'
```
#### Data Query
Update the table name, run the Athena query, and save the output to a CSV file.
NOTE: You can request a longer Athena query timeout limit from AWS if the default 30 minutes is not enough.
```sql
SELECT eventTime, eventSource, eventName, awsRegion, userIdentity.accountId as "userIdentity.accountId", recipientAccountId, "$path" as key, requestParameters, responseElements
FROM my_table_name
WHERE
eventName in (
'AllocateAddress',
'CloneStack',
'CopyImage',
'CopySnapshot',
'CreateAutoScalingGroup',
'CreateBucket',
'CreateCustomerGateway',
'CreateDBInstance',
'CreateDhcpOptions',
'CreateFunction20150331',
'CreateFunction20141111',
'CreateImage',
'CreateInternetGateway',
'CreateLoadBalancer',
'CreateLogGroup',
'CreateNatGateway',
'CreateNetworkAcl',
'CreateNetworkInterface',
'CreatePipeline',
'CreateRole',
'CreateRouteTable',
'CreateSecurityGroup',
'CreateSnapshot',
'CreateStack',
'CreateSubnet',
'CreateTable',
'CreateUser',
'CreateVolume',
'CreateVpc',
'CreateVpnConnection',
'CreateVpnGateway',
'CreateVpcPeeringConnection',
'ImportSnapshot',
'PutMetricAlarm',
'PutRule',
'RegisterImage',
'RunInstances',
'RunJobFlow'
)
and eventSource in (
'autoscaling.amazonaws.com',
'datapipeline.amazonaws.com',
'dynamodb.amazonaws.com',
'ec2.amazonaws.com',
'events.amazonaws.com',
'elasticloadbalancing.amazonaws.com',
'elasticmapreduce.amazonaws.com',
'iam.amazonaws.com',
'lambda.amazonaws.com',
'logs.amazonaws.com',
'monitoring.amazonaws.com',
'opsworks.amazonaws.com',
'rds.amazonaws.com',
's3.amazonaws.com'
)
and errorcode is null
```
### Deploy the Main CloudFormation template
In the same account as your CloudTrail S3 bucket deploy this Main CloudFormation template in a single region. This one CloudFormation stack, in combination with the IAM Role CloudFormation stack, will have the ability to tag all regions and more than one AWS account.
**Note:** An explanation of each of the parameters:
```
CloudTrailBucketName - Name of bucket where your CloudTrail logs are stored.
CodeS3Bucket - Name of bucket where AutoTag code is stored. You will need to have either downloaded a zip of a AutoTag release and upload it to your own bucket, or refer to the bucket where your AutoTag code is stored if you also have AutoTag running inside the same AWS account.
CodeS3Path - Path to the zip file containing the AutoTag code inside the CodeS3Bucket.
```
```bash
export REGION=ap-southeast-2 # set this to the region you plan to deploy to
wget https://raw.githubusercontent.com/GorillaStack/retro-tag/master/cloud_formation/autotag_retro_main-template.json
aws cloudformation create-stack \
--template-body file://autotag_retro_main-template.json \
--stack-name AutoTagRetro \
--parameters \
ParameterKey=CloudTrailBucketName,ParameterValue=my-cloudtrail-bucket \
ParameterKey=CodeS3Bucket,ParameterValue=gorillastack-autotag-releases-$REGION \
ParameterKey=CodeS3Path,ParameterValue=autotag-0.5.1.zip \
ParameterKey=AutoTagDebugLogging,ParameterValue=Disabled \
ParameterKey=AutoTagTagsCreateTime,ParameterValue=Enabled \
ParameterKey=AutoTagTagsInvokedBy,ParameterValue=Enabled \
--capabilities CAPABILITY_NAMED_IAM \
--region $REGION
```
### Deploy the IAM Role CloudFormation template
In each *additional* AWS account where tagging will be applied, deploy this IAM Role CloudFormation template in a single region.
```bash
export REGION=ap-southeast-2 # set this to the region you plan to deploy to
export MAIN_AWS_ACCOUNT_NUMBER=11111111111 # set this to the AWS account number where we deployed the Main CloudFormation template
wget https://raw.githubusercontent.com/GorillaStack/retro-tag/master/cloud_formation/autotag_retro_role-template.json
aws cloudformation create-stack \
--template-body file://autotag_retro_role-template.json \
--stack-name AutoTagRetro \
--parameters \
ParameterKey=MainAwsAccountNumber,ParameterValue=$MAIN_AWS_ACCOUNT_NUMBER \
ParameterKey=MainStackName,ParameterValue=AutoTagRetro \
--capabilities CAPABILITY_NAMED_IAM \
--region $REGION
```
### Tag Existing Resources
Use the `retro_tagging/retro_tag.rb` script to scan your environment for resources and then apply tagging to any resources that still exist.
The script will start by scanning each region for the AWS resources that exist then it will run the AutoTag lambda function against each CloudTrail log in S3 that includes at least one of the existing AWS resources.
```bash
$ bundle install # run this once to grab the ruby gem dependencies
Bundle complete! 17 Gemfile dependencies, 28 gems now installed.
export CSV_PATH="~/Downloads/MyAwsAccount_10292019.csv" # set this to the CSV exported from Athena
export BUCKET=my-cloudtrail-bucket # set this to the name of the CloudTrail S3 bucket
export BUCKET_REGION=ap-southeast-2 # set this to the region of the CloudTrail S3 bucket
export SCAN_PROFILE=development # set this to a profile of the account where tagging will be applied, this should match the data in the CSV
export LAMBDA_PROFILE=development # set this to a profile of the account where the Main CloudFormation template was deployed
export LAMBDA_REGION=ap-southeast-2 # set this to the region where the Main CloudFormation template was deployed
./retro_tag.rb \
--csv "$CSV_PATH" \
--bucket $BUCKET \
--bucket-region $BUCKET_REGION \
--scan-profile "$SCAN_PROFILE" \
--lambda-profile "$LAMBDA_PROFILE" \
--lambda-region $LAMBDA_REGION
```
## Audit AutoTags
Use the `retro_tagging/audit_tag.rb` script to scan all supported resources for Auto Tags to view the overall coverage of the Retro Tag process.
The script will start by scanning each region for the AWS resources that exist and show a report.
`./audit_all_tags.rb --profile development-readonly`
`./audit_all_tags.rb --access_key_id XXX --secret-access-key XXXXXX`
Each resource's tags are inspected for the existence of the `AutoTag_Creator` and `AutoTag_CreateTime` required tags. For each AWS resource a point is added to either the `Passed` or `Failed` column based on each of those required tags existence.
Example Output:
```json
+---------------------------+--------+--------+----------+
| Auto-Tag Audit Summary |
+---------------------------+--------+--------+----------+
| Service | Passed | Failed | Coverage |
+---------------------------+--------+--------+----------+
| AutoScaling Groups | 62 | 6 | 91.18% |
+---------------------------+--------+--------+----------+
| CloudWatch Alarms | 2,034 | 1,904 | 51.65% |
+---------------------------+--------+--------+----------+
| CloudWatch Events Rules | 64 | 0 | 100.0% |
+---------------------------+--------+--------+----------+
| CloudWatch Log Groups | 680 | 110 | 86.08% |
+---------------------------+--------+--------+----------+
| Data Pipelines | 82 | 14 | 85.42% |
+---------------------------+--------+--------+----------+
| DynamoDB Tables | 564 | 148 | 79.21% |
+---------------------------+--------+--------+----------+
| EC2 AMIs | 178 | 30 | 85.58% |
+---------------------------+--------+--------+----------+
| EC2 Customer Gateways | 2 | 6 | 25.0% |
+---------------------------+--------+--------+----------+
| EC2 DHCP Options Sets | 10 | 46 | 17.86% |
+---------------------------+--------+--------+----------+
| EC2 EIPs | 52 | 124 | 29.55% |
+---------------------------+--------+--------+----------+
| EC2 Instances | 282 | 48 | 85.45% |
+---------------------------+--------+--------+----------+
| EC2 Snapshots | 260 | 90 | 74.29% |
+---------------------------+--------+--------+----------+
| EC2 Volumes | 452 | 58 | 88.63% |
+---------------------------+--------+--------+----------+
| EMR Clusters | 2 | 0 | 100.0% |
+---------------------------+--------+--------+----------+
| Elastic Load Balancing | 98 | 38 | 72.06% |
+---------------------------+--------+--------+----------+
| Elastic Load Balancing V2 | 2 | 0 | 100.0% |
+---------------------------+--------+--------+----------+
| IAM Roles | 338 | 90 | 78.97% |
+---------------------------+--------+--------+----------+
| IAM Users | 276 | 46 | 85.71% |
+---------------------------+--------+--------+----------+
| Lambda Functions | 152 | 0 | 100.0% |
+---------------------------+--------+--------+----------+
| OpsWorks Stacks | 16 | 4 | 80.0% |
+---------------------------+--------+--------+----------+
| RDS Instances | 25 | 12 | 67.57% |
+---------------------------+--------+--------+----------+
| S3 Buckets | 158 | 170 | 48.17% |
+---------------------------+--------+--------+----------+
| Security Groups | 994 | 514 | 65.92% |
+---------------------------+--------+--------+----------+
| VPC ENIs | 602 | 112 | 84.31% |
+---------------------------+--------+--------+----------+
| VPC Internet Gateways | 60 | 20 | 75.0% |
+---------------------------+--------+--------+----------+
| VPC NAT Gateways | 24 | 4 | 85.71% |
+---------------------------+--------+--------+----------+
| VPC Network ACLs | 12 | 84 | 12.5% |
+---------------------------+--------+--------+----------+
| VPC Peering Connections | 52 | 8 | 86.67% |
+---------------------------+--------+--------+----------+
| VPC Route Tables | 166 | 116 | 58.87% |
+---------------------------+--------+--------+----------+
| VPC Subnets | 380 | 84 | 81.9% |
+---------------------------+--------+--------+----------+
| VPCs | 62 | 18 | 77.5% |
+---------------------------+--------+--------+----------+
| VPN Connections | 8 | 2 | 80.0% |
+---------------------------+--------+--------+----------+
| VPN Gateways | 24 | 14 | 63.16% |
+---------------------------+--------+--------+----------+
```
## FAQ
### Supported Ruby versions
The retro tagging and audit logging functions were confirmed to be working on Ruby version 2.6.6.
## Contributing
If you have questions, feature requests or bugs to report, please do so on [the issues section of our github repository](https://github.com/GorillaStack/retro-tag/issues).
If you are interested in contributing, please get started by forking our GitHub repository and submit a pull-request.