AWS allows customers to assign metadata to their AWS resources in the form of tags. Each tag consists of a customer-defined key and an optional value. Tags can make it easier to manage, search for, and filter resources by purpose, owner, environment, or other criteria. AWS tags can be used for many purposes like organizing your AWS resources or for your cost and usage report, automation, IT service management, access control, and security risk management.

Many customers require some or all AWS resources created by an AWS service to add a tag for consistency. This can be a default tag or custom tag for example ‘deployment ID’. For example, you might need to propagate custom tags from an Amazon Aurora Serverless to the VPC endpoints and network interfaces it creates or, when you create an Amazon SageMaker Studio Control Panel, to the Amazon EFS volume and security group it creates.

You can use AWS Tag Editor and AWS Resource Groups to find and add tags after the resources are created. Another option is to automatically propagate tags when the AWS resources are created. In this blog post, we share an example of how you can propagate custom tags automatically to the resources when you create Aurora serverless. In the next post, we will share another example of how you can re-use the same mechanism to automatically propagate custom tags when you create Sagemaker Studio Control Panel. You can use the same mechanism for other use-cases (for example, to propagate tags upon resource modification or after restoring an AWS resource from a backup).

Overview of solution

AWS CloudTrail helps you enable governance, compliance, and operational and risk auditing of your AWS account. Every action by an AWS service is an API call that is recorded in CloudTrail as an event. In the solution we describe in this post, we create a rule in Amazon EventBridge that triggers an AWS Lambda function. The AWS Lambda function gets a list of tags from the primary resource that we’re launching and applies tags to resources that are associated with it.

Solution architecture shows CloudTrail, EventBridge, and Lambda. CloudTrail finds the resources for tagging and the EventBridge rule triggers the Lambda function when the specified event occurs.

Figure 1: Services used in the solution

Solution steps:

  1. Find the AWS resources created by an AWS service that you need to tag.
  2. Create a rule in EventBridge that is triggered by an API call recorded in CloudTrail.
  3. Trigger a Lambda function to get the primary resource and tag, find associated resources, and apply the tag.

Solution walkthrough

We’ll share two examples of how you can tag AWS resources that are created by AWS services in your account.

Prerequisites

To complete the steps in this walkthrough, you need the following:

  • An AWS account.
  • Basic understanding of Python using Boto3 APIs and AWS CLI

Solution to automatically propagate tags when you create Amazon Aurora Serverless configuration

Complete these steps or use the CloudFormation template to tag VPC endpoints and network interfaces.

  1. Sign in to the AWS Cloud9 console.
  2. In Configure settings, create an environment with the default settings shown here:

Under Environment type, Create a new EC2 instance for environment (direct access) is selected. For Instance type, t2.micro (GIB RAM + 1vCPU) is selected. For Platform, Amazon Linux 2 (recommended) is selected.

Figure 2: Create a Cloud9 environment

  1. Run the following commands in your AWS Cloud9 environment to download the DNS resolver module in the target directory.
mkdir -p auroraTagPropagator/ pip3 install dnspython -t /home/ec2-user/environment/auroraTagPropagator/

  1. Create a Python file named lambda_function.py in this directory and paste the following code:
import boto3
import dns.resolver
import time #initialize rds and ec2 clients
rds = boto3.client("rds")
ec2 = boto3.client("ec2") def lambda_handler(event, context): #fetch cluster id from the cloudtrail event clusterId = event['detail']['requestParameters']['dBClusterIdentifier'] #call rds api using cluster id to fetch tags and endpoint response = rds.describe_db_clusters(DBClusterIdentifier=clusterId) tags = response['DBClusters'][0]['TagList'] endpoint = response['DBClusters'][0]['Endpoint'] #add sleep for dns to update time.sleep(45) #perform an nslookup on endpoint try: result = dns.resolver.resolve(endpoint, 'CNAME') except Exception as e: print("Failed to resolve DNS: " + str(e)) return #fetch vpcendpoint from the nslookup results for cnameval in result: vpce = str(cnameval.target) print (vpce) var=vpce.split("-")[1] print(var) vpcendpoint = "vpce-" + var print(vpcendpoint) #tag vpc endpoint tag_resp = ec2.create_tags(Resources=[vpcendpoint], Tags=tags) #get ENIs that are attached to vpc endpoints resp = ec2.describe_vpc_endpoints(VpcEndpointIds=[vpcendpoint]) for vpce in resp['VpcEndpoints']: enis = vpce['NetworkInterfaceIds'] #tag each eni for eni in enis: tag_resp = ec2.create_tags(Resources=[eni], Tags=tags)

  1. Zip these files and lambda_function.py in a single ZIP file.
zip -r auroraTagPropagator.zip *

  1. Push the file to your S3 bucket.
aws s3api put-object --bucket $bucket_name --key auroraTagPropagator.zip --body auroraTagPropagator.zip

  1. Go the IAM console, choose Policies, and then choose Create Policy.
  2. Choose the JSON tab and paste the following to grant permissions to create tags for resources in an Aurora Serverless configuration.
{
"Version": "2012-10-17", "Statement": [ { "Sid": "AllowCreateTagsForVPC", "Effect": "Allow", "Action": "ec2:CreateTags", "Resource": [ "arn:aws:ec2:*:ACCOUNTNUMBER:vpc/*", "arn:aws:ec2:*: ACCOUNTNUMBER:vpc-endpoint/*"
] }, { "Sid": "AllowToCreateLogs", "Effect": "Allow", "Action": [
"logs:CreateLogStream", "ec2:DescribeVpcEndpoints", "logs:CreateLogGroup", "logs:PutLogEvents", "rds:DescribeDBClusters" ], "Resource": "*" } ]
}

The permissions are pasted into the JSON editor in the IAM console.

Figure 3: JSON

  1. Choose Next: Tags and then choose Next: Review.
  2. On the Review policy page, enter auroraTaggingPolicy for the policy name and then choose Create policy.
  3. To create a role for the Lambda function, in the left navigation pane, choose Roles and then choose Create role.
  4. On Create role, under Choose a use case, choose Lambda, and then choose Next: Permissions.

On Create role, under Select type of trusted entity, AWS service is selected. Under Choose a use case, Lambda is selected. This allows Lambda functions to call AWS services on your behalf.

Figure 4: Choose a use case

  1. Search for the policy you just created, choose Next: Tags, and then choose Next: Review.
  2. For the put role name, enter auroraTagPropagatorRole.
  3. Go to the AWS Lambda console and create a function with the following details:
    • Function name: propagateAuroraTags
    • Runtime: Python 3.8
  4. For permissions, choose Use an existing role, and then choose auroraTagPropagatorRole from the dropdown.
  5. Choose Upload from and then upload the ZIP file.
  6. Since DNS update takes longer than the default lambda timeout of 30 seconds, we will update the timeout period to 1 min 30 seconds. To update the timeout, choose the Configuration tab, under General configuration, update the timeout period to 1 min 30 sec, as shown here:

In the Lambda console, there are tabs for Code, Test, Monitor, Configuration, Aliases, and Versions. The Configuration tab is selected and the Edit button is highlighted.

Figure 5: General configuration

  1. Go to the Amazon EventBridge console, choose Events, choose Rules, and then choose Create rule.
  2. For the rule name, enter propgateAuroraTagsRule.
  3. In Define pattern, choose Event pattern. For Event matching pattern, choose Pre-defined pattern by service. For Service provider, choose AWS. For Service name, choose Relational Database Service (RDS). For Event type, choose AWS API Call via CloudTrail. Choose Specific operation(s) and then enter CreateDBCluster.

The fields of the Define pattern page are completed as described in the post.

Figure 6: Define pattern

  1. On Select targets, under Target, choose Lambda function. Under Function, choose propagateAuroraTags from the dropdown, and then choose Create.

The fields in the Select targets page are completed as described in the post.

Figure 7: Select targets

You can verify the tags are attached to the VPC endpoint and network interfaces. The next time an Aurora Serverless configuration is created, custom tags will be applied automatically to the VPC endpoint and network interfaces.

Cleaning up

If you created the environment using CloudFormation template, here are the instructions to delete the CloudFormation stack.

Conclusion

In this post, we showed how you can create an automation to propagate tags whenever a resource is created. You can extend this logic to any of your use-case that requires you to tag all the subsequent resources when a new AWS service is created.

About the authors

Vaibhav Shah

Vaibhav Shah

Vaibhav Shah is an AWS Solutions Architect who is passionate about building automated solutions for complex problems. His technical interests include Serverless, DevOps, CI/CD, and everything related to automation.

Vikas Shah

Vikas Shah

Vikas Shah is an Enterprise Solutions Architect at AWS. He is a technology enthusiast who enjoys helping customers find innovative solutions to complex business challenges.