To deploy the new changes, AppConfig’s StartDeploymentĪPI must be run using the AWS AppConfig Console or the CLI. To deploy changes made to the CustomerManagedTags document:Īfter you make changes to the customization configuration profile, you must deploy theĬhanges for them. Using the sameĬonfigurationID as a default configuration tag rule overrides theĭefault rule, and applies the custom rule in its place. You can see which version of configuration is deployed to your account by viewing the past deploymentsĪny of the existing tag rules can be overridden by updating the customization profileĮither with AWS CloudFormation by Deploying a configuration profile or, or directly using using AppConfig’s CreateHostedConfigurationVersion API. The alarm definitions can then be viewed in the specified output file, in this case,

The tag definitions can then be viewed in the specified output file, in this case, Is AMSManagedTags, while to view customer tag definitions, the value is CustomerManagedTags.Ĭlient ID: The unique application instance identifier, this For example, the following configuration profileĬonfiguration: To view AMS Accelerate default tag definitions, the value You can enable the read-only mode by modifying the customer configuration profile to include the

Resource Tagger stops at this point, and does not make any changes to your resources (does not add or remove tags). The AWS Config rules that you can look for have the AMSResourceTagger- prefix.įor example the AMSResourceTagger-EC2Instance Config rule evaluates if appropriate tags are created forĪWS::EC2::Instance resources based on the configuration profile. When in read-only mode, Resource Tagger still examines the tagging rules that are being specified in the managedĪnd customer configuration profiles, and scans for resources that do not meet these tagging rules. This is useful if you want to provide your own tagging mechanism. Resource Tagger can be set to a read-only mode that prevents it from adding or removing any tags on your resources. Preventing Resource Tagger from modifying resources The ams:rt:ams-managed tag opts you in to having your The following is an example Resource Tagger configuration snippet that adds the tagĪms:rt:ams-managed with the value true to allĪmazon EC2 instances. If you want to use the Resource Tagger to tag your resources, see Rules, automatically adding and removing tags on resources to ensure they comply with your rules. Resource Tagger has a configurable set of rules that define how your resources should be tagged, then it enforces those The AMS Accelerate Resource Tagger is a component that is deployed in your account during AMS Accelerate onboarding.

Resources managed by Resource Tagger, do not use the ams:rt: prefixįor tag keys. Resource Tagger, but the configuration profiles do not indicate that the tag should beĪpplied, then Resource Tagger removes your manually added tag. This means that if the resource is managed by If you manually create your own tag with the ams:rt: prefix, it'sĬonsidered managed by Resource Tagger.

Final draft tagger number id