Creating S3 buckets in AWS - Practice Exercises

Challenge - 5 Problems

❓ Configuration

intermediate

What is the output of this AWS CLI command?

You run the following AWS CLI command to create an S3 bucket in the us-east-1 region:

aws s3api create-bucket --bucket my-unique-bucket-12345 --region us-east-1

What will be the result?

AWS

aws s3api create-bucket --bucket my-unique-bucket-12345 --region us-east-1

A Bucket is created but in the default region us-west-2.

B Command fails because LocationConstraint must be set for us-east-1.

C Bucket is created successfully without specifying LocationConstraint.

D Command fails because bucket name is invalid.

💡 Hint

The us-east-1 region is special in AWS S3 bucket creation.

When creating an S3 bucket in us-east-1, you do not need to specify the LocationConstraint parameter. The bucket will be created successfully without it.

❓ Architecture

intermediate

How many buckets can you create in AWS by default?

By default, how many Amazon S3 buckets can you create in a single AWS account?

A 1000 buckets

B 100 buckets

C Unlimited buckets

D 10 buckets

💡 Hint

Think about AWS default service limits.

AWS limits the number of S3 buckets per account to 100 by default to manage resources.

❓ security

advanced

Which bucket policy option correctly denies public access?

You want to deny all public access to your S3 bucket named 'my-secure-bucket'. Which bucket policy snippet correctly denies any request that is not from your AWS account?

AWS

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Principal": "*",
      "Action": "s3:*",
      "Resource": ["arn:aws:s3:::my-secure-bucket", "arn:aws:s3:::my-secure-bucket/*"],
      "Condition": {
        "StringNotEquals": {
          "aws:PrincipalAccount": "123456789012"
        }
      }
    }
  ]
}

A Effect: Allow, Principal: *, Condition: StringEquals aws:PrincipalAccount your-account-id

B Effect: Deny, Principal: *, Condition: StringNotEquals aws:PrincipalAccount your-account-id

C Effect: Deny, Principal: your-account-id, Condition: StringEquals aws:PrincipalAccount your-account-id

D Effect: Allow, Principal: *, no Condition

💡 Hint

Deny overrides allow and Principal * means everyone.

Option B denies any action from principals not in your account, effectively blocking public access.

❓ service_behavior

advanced

What happens if you try to create an S3 bucket with a name already taken globally?

You attempt to create an S3 bucket named 'example-bucket' but this name is already used by another AWS user in a different region. What will happen?

A Bucket creation fails with an error that the bucket name is already taken.

B Bucket is created successfully in your region with the same name.

C Bucket creation succeeds but is shared globally with the other user.

D AWS automatically appends a unique suffix to your bucket name and creates it.

💡 Hint

S3 bucket names must be unique across all AWS users worldwide.

S3 bucket names are globally unique. If the name is taken, creation fails with an error.

✅ Best Practice

expert

Which bucket configuration best ensures data durability and availability across multiple regions?

You want to create an S3 bucket that stores data redundantly across multiple AWS regions to protect against regional failures. Which configuration achieves this?

A Enable S3 Transfer Acceleration on a single regional bucket.

B Create a standard S3 bucket in one region with versioning enabled.

C Create multiple buckets in different regions and manually copy data between them.

D Use S3 Cross-Region Replication (CRR) to replicate objects to a bucket in another region.

💡 Hint

Look for automated replication across regions.

S3 Cross-Region Replication automatically copies objects to another bucket in a different region, ensuring durability and availability.