Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Enforcing Tag Policies on existing instances
A customer is using tagging policies and enforcing them SCP, so that an instance can't run unless it's tagged with relevant required tags.
If they were to attach that SCP, currently triggered on ec2:RunInstances, to an account with already running instances and potentially untagged or tagged in a non-compliant way, what would happen? Would it stop the instances or only prevent them from restarting once stopped?
- Argomenti
- Gestione e amministrazione
- Lingua
- English
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
RunInstances is the API for launching instances so an SCP that limits use of it with conditions will only apply to launching new ones.
StartInstances and StopInstances are for stop/start actions.
After attaching the above SCP policy to an account, I am unable (with Administrator access) to launch an instance with all the compliant tags. The policy is working fine when I deploy an instance with incorrect tags. Does it require an special permissions? Any advice please.