-
Hi Kenneth,
Thanks for the detailed response. I have another question. I have listed the question below.
There was a major incident that occurred in your company wherein the web application that you are supporting unexpectedly went down in the production environment. Upon investigation, it was found that a junior DevOps engineer terminated the EC2 instance in production which caused the disruption of service. Only the Solutions Architects should be allowed to stop or terminate instances in the production environment. You also found out that there are a lot of developers who have full access to your production AWS account.
Which of the following options will fix this security vulnerability in your cloud architecture and prevent this kind of failure from happening again? (Choose 2)
Isn’t it better to have PoweUserAccesss versus full-access? When I think of full-access, I think of full administrator access.
“Add tags to the EC2 instances in the production environment and add resource-level permissions to the developers with an explicit deny on terminating the instance which contains the tag.”
Since this is a production only account, I’m not sure why we add tag in the first place since the question state ” Only the Solutions Architects should be allowed to stop or terminate instances in the production environment.” Shouldn’t simply modifying the IAM role to revoke permission to delete ec2 instances and downgrading from a full-access to powerUseraccess be the appropriate step?
