A company is using AWS Control Tower to manage AWS accounts in an organization in AWS Organizations. The company has an OU that contains accounts. The company must prevent any new or existing Amazon EC2 instances in the OU's accounts from gaining a public IP address. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Create an SCP that prevents the launch of instances that have a public IP address. Additionally, configure the SCP to prevent the attachment of a public IP address to existing instances. Attach the SCP to the OU.
Most accepted answer: C. Create an SCP that prevents the launch of instances that have a public IP address. Additionally, configure the SCP to prevent the attachment of a public IP address to existing instances. Attach the SCP to the OU.
Community votes: B=5, C=11
Selected Answer: C Option C - From AWS doc page "Don't use AWS Organizations to update service control policies (SCPs) attached to an OU that is registered with AWS Control Tower. Doing so could result in the controls entering an unknown state, which will require you to repair your landing zone or re-register your OU in AWS Control Tower. Instead, you can create new SCPs and attach those to the OUs rather than editing the SCPs that AWS Control Tower has created." https://docs.aws.amazon.com/controltower/latest/userguide/orgs-guidance.html upvoted 12 times
Selected Answer: B Voting for B: SCP will cause a state drift, since company already use Control Tower upvoted 6 times 8693a49 2 years ago Adding a new SCP will not cause drift. Modifying an existing SCP that was created by CT would, which is not the case here. upvoted 3 times ...
Adding a new SCP will not cause drift. Modifying an existing SCP that was created by CT would, which is not the case here. upvoted 3 times
Selected Answer: B Why Option B Is the Best Fit Proactive controls in AWS Control Tower use CloudFormation hooks to validate resource configurations before deployment. By setting the AssociatePublicIpAddress property to False, you ensure that: - New EC2 instances cannot be launched with public IPs. - The control is enforced across all accounts in the OU, maintaining centralized governance. - Deployment fails if the configuration violates the control, preventing misconfigurations before they occur. This approach is preventive and scalable, aligning perfectly with the requirement to block public IPs for both new and existing EC2 instances. upvoted 1 times
Selected Answer: C "Behavior of proactive controls Proactive controls check resources whenever those resources are created or updated by means of AWS CloudFormation stack operations. Specifically, these proactive controls are implemented as preCreate and preUpdate hook handlers. As a consequence, these controls may not affect requests that are made directly to services through the AWS console, through AWS APIs, or through other means such as AWS SDKs, or other Infrastructure-as-Code (IaC) tools. For more information about when preCreate and preUpdate hooks operate, see AWS CloudFormation hooks." upvoted 1 times