Why is IAM considered foundational for AWS security?
Think about how AWS controls user permissions and access.
IAM (Identity and Access Management) is foundational because it defines who can do what in AWS, controlling access to resources securely.
Which IAM practice best supports the principle of least privilege?
Least privilege means giving minimal access necessary.
Granting only necessary permissions reduces risk and limits potential damage from compromised credentials.
Given an IAM policy that explicitly denies access to a resource, what happens if another policy explicitly allows access to the same resource?
Consider how AWS evaluates conflicting permissions.
In IAM, explicit deny always takes precedence over allow, blocking access regardless of other permissions.
What happens when an EC2 instance is assigned an IAM role with specific permissions?
Think about how IAM roles provide temporary credentials.
IAM roles assigned to EC2 provide temporary credentials automatically, enabling secure access without manual credential management.
Which practice is the most secure way to protect the AWS root account?
Consider how to minimize risk for the most powerful account.
The root account has full access; enabling MFA and limiting its use reduces risk of compromise.