Database and analytic tags
Use the tables below for migration plans whose Migration Tracking and Incentive Guide includes database and analytic MAP credits.
Source | Destination | Tag key | Tag value |
---|---|---|---|
On-premises Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm |
On-premises non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig |
On-premises Commercial DB&A | EC2 | map-migrated |
mig |
On-premises non-commercial DB&A | EC2 | map-migrated |
mig |
EC2 Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm_ec2_ |
EC2 non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig_ec2_ |
Source | Destination | Tag key | Tag value |
---|---|---|---|
On-premises Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm |
On-premises non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig |
On-premises Commercial DB&A | EC2 | map-migrated |
mig |
On-premises non-commercial DB&A | EC2 | map-migrated |
mig |
EC2 Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm_ec2_ |
EC2 non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig_ec2_ |
Note
Use lowercase letters for the comm
, mig
, comm_ec2_
,
and mig_ec2_
prefixes and uppercase letters for the alphanumeric MPE IDs (long MPE
IDs). For more information about what tag values you should use, see Tagging key combinations. For more information about your MPE ID, see MPE ID length.
A commercial database is defined as any third-party database engine, data warehouse, or analytics offering for which you have paid a fee for use rights, enhancements, maintenance, or support for that third party offering. A non-commercial database is defined as any third-party database engine, data warehouse, or analytics offering for which you have not paid a fee for use rights, enhancements, maintenance, or support for that third party offering. For a complete list of services that are included in MAP – Database & Analytics (DB&A), see the MAP 2.0 Included Services list: https://s3-us-west-2.amazonaws.com/map-2.0-customer-documentation/included-services/MAP_Included_Services_List.pdf.
Special scenario
If your destination database is changed from EC2 to any AWS DB&A service after your initial migration, then use the tables below to tag your DB&A service.
Source | Destination | Tag key | Tag value |
---|---|---|---|
EC2 Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm |
EC2 non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig |
Source | Destination | Tag key | Tag value |
---|---|---|---|
EC2 Commercial DB&A | Any AWS DB&A Service | map-migrated |
comm |
EC2 non-commercial DB&A | Any AWS DB&A Service | map-migrated |
mig |
Note
Use lowercase letters for the comm
and mig
prefixes and
uppercase letters for the alphanumeric MPE IDs (long MPE IDs). For more information about what
tag values you should use, see Tagging key combinations. For more information about your
MPE ID, see MPE ID length.