Before start tagging, make sure your CUR is set up as per Step 1 - Set up CUR and tags are active as per Step 2 - Activate Tags.
AWS CloudFormation enables you to create and provision AWS infrastructure deployments predictably and repeatedly. It helps you leverage AWS products such as Amazon EC2, Amazon Elastic Block Store, Amazon SNS, Elastic Load Balancing, and Auto Scaling to build highly reliable, highly scalable, cost-effective applications in the cloud without worrying about creating and configuring the underlying AWS infrastructure. AWS CloudFormation enables you to use a template file to create and delete a collection of resources together as a single unit (a stack).
You can use the Resource Tags property to apply tags to resources, which can help you identify and categorize those resources. You can tag only resources for which AWS CloudFormation supports tagging. For information about which resources you can tag with CloudFormation, see the individual resources in AWS resource and property types reference.
In this section we will show you a simple example of using Cloudformation for tagging the migrated resources. For further information on how to use CloudFormation, please check the service documentation page
{
"Key" : "map-migrated",
"Value" : "d-server-12345"
}
Replace d-server-12345 by ServerID
from Step 1
The AWS Cloud Development Kit (AWS CDK) is an open-source software development framework to define your cloud application resources using familiar programming languages.
In this section we will show you a simple example of using AWS CDK to tag the resources. For more information please visit CDK documentation. A tag applied to a given construct also applies to all of its taggable children. Tags are included in the AWS CloudFormation template synthesized from your app and are applied to the AWS resources it deploys.
Tags.of(myConstruct).add('map-migrated', 'd-server-12345');
Replace d-server-12345 by ServerID
from Step 1
AWS Application Migration Service (AWS MGN) is the primary migration service recommended to lift and shift your applications to AWS. Customers considering CloudEndure Migration are encouraged to use AWS Application Migration Service for future migrations. For more details on how to use MGN for tagging the migrated resources please check the MGN service documentation
In this section we will show you a simple example of using MGN to tag the migrated resources.
Add tags
box, use map-migrated
as the Tag Key
and use the ServerID
from Step 1 as the Value
then click Add
.All the resources migrated by MGN will receive the designated tags.
CloudEndure Migration Factory Solution coordinates and automates large scale migrations to the AWS Cloud, involving numerous servers. Enterprises can improve performance and prevent long cutover windows by automating manual processes and integrating multiple tools efficiently. This is possible through this solution’s orchestration platform options, which includes CloudEndure Migration and, as of version 2.0.0, AWS Application Migration Service (AWS MGN). We recommend AWS MGN to rehost servers to AWS at scale. Today, this solution is used by AWS Professional Services, AWS Partners, and other enterprises. For more details on CEMF, please check the CEMF solutions page
In this section we will show you a simple example of CEMF tagging the migrated resources.
To add tags to all imported servers in CEMF, a special script is required. Please use the script located here
Add tags
.Add tags
box, use map-migrated
as the Tag Key
and use the ServerID
from Step 1 as the Value
then click Add
.The AWS Serverless Application Model (SAM) is an open-source framework for building serverless applications. It provides shorthand syntax to express functions, APIs, databases, and event source mappings. With just a few lines per resource, you can define the application you want and model it using YAML. During deployment, SAM transforms and expands the SAM syntax into AWS CloudFormation syntax, enabling you to build serverless applications faster.
In this section we will show you a simple example of using AWS SAM to tag the resources. For more information please visit SAM documentation.
Globals:
Function:
Tags:
HttpApi:
Tags:
Replace d-server-12345 by ServerID
from Step 1