S3 Bucket Policies

You have updated an S3 bucket policy to allow IAM users to read/write files in the S3 bucket, but one of the users complain that he can't perform a PutObject API call. What is a possible cause for this?

• The S3 bucket policy must be wrong

• The user is lacking permissions

• The IAM user must have an explicit DENY in the attached IAM Policy

• You need to contact AWS Support to lift this limit

You have a website that loads files from an S3 bucket. When you try the URL of the files directly in your Chrome browser it works, but when the website you're visiting tries to load these files it doesn't. What's the problem?

• The Bucket policy is wrong

• The IAM policy is wrong

• CORS is wrong

• Encryption is wrong

Use S3 bucket for policy to?

• Grant private access to the bucket

• Force objects to be encrypted at upload

• Grant access to another account (Cross Account)

• All of the above

CORS stand for what?

• Cross-Operation Resource Sharing

• Cross-Option Resource Sharing

• Cross-Object Resource Sharing

• Cross-Origin Resource Sharing

JSON based policies consists of:

• Resources: buckets and objects

• Actions: Set of API to Allow or Deny

• Effect: Allow / Deny

• Principal: The account or user to apply the policy to

You will need MFA to

• permanently delete an object version

• suspend versioning on the bucket

• enabling versioning

• listing deleted versions

You won’t need MFA for

• permanently delete an object version

• suspend versioning on the bucket

• enabling versioning

• listing deleted versions