Creating S3 buckets in AWS - Try It Yourself

Creating S3 buckets

📖 Scenario: You are working as a cloud assistant helping a small business set up storage for their files. They want to create Amazon S3 buckets to keep their data safe and organized.

🎯 Goal: Build a simple AWS CloudFormation template that creates two S3 buckets with specific names and settings.

📋 What You'll Learn

Create an AWS CloudFormation template in YAML format.

Define two S3 buckets with exact names: mycompany-logs and mycompany-data.

Set the VersioningConfiguration to Enabled for the mycompany-data bucket only.

Add a BucketName property for each bucket with the exact names.

Use best practices for bucket creation in CloudFormation.

💡 Why This Matters

🌍 Real World

CloudFormation templates are used to automate and standardize cloud resource creation, saving time and reducing errors.

💼 Career

Knowing how to create and configure S3 buckets with CloudFormation is a key skill for cloud engineers and DevOps professionals.

1

Create the basic CloudFormation template structure

Start by creating a CloudFormation template with the root keys AWSTemplateFormatVersion set to '2010-09-09' and an empty Resources section.

AWS

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  # Your code here

Hint

This is the basic skeleton of a CloudFormation template. The Resources section will hold your bucket definitions.

2

Add the first S3 bucket resource

Inside the Resources section, add a resource named LogsBucket of type AWS::S3::Bucket with a BucketName property set to mycompany-logs.

AWS

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  LogsBucket:
    Type: AWS::S3::Bucket
    # Your code here

Hint

Remember to indent properly under LogsBucket and add the Properties section before BucketName.

3

Add the second S3 bucket with versioning enabled

Add another resource named DataBucket of type AWS::S3::Bucket with BucketName set to mycompany-data and enable versioning by adding VersioningConfiguration with Status set to Enabled.

AWS

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  LogsBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: mycompany-logs
  DataBucket:
    Type: AWS::S3::Bucket
    # Your code here

Hint

Versioning helps keep multiple versions of files. Make sure to nest Status: Enabled under VersioningConfiguration.

4

Complete the CloudFormation template

Ensure the template is valid YAML with correct indentation and no extra properties. The template should define exactly two S3 buckets named mycompany-logs and mycompany-data with versioning enabled only on mycompany-data.

AWS

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  LogsBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: mycompany-logs
  DataBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: mycompany-data
      VersioningConfiguration:
        Status: Enabled
# Your code here

Hint

Review your indentation and property names carefully. The template should be ready to deploy.

Practice

1. What is the main purpose of an Amazon S3 bucket?

easy

A. To store and organize files in the cloud

B. To run virtual servers

C. To manage user permissions

D. To monitor network traffic

Solution

1. Step 1: Understand what S3 buckets are

   S3 buckets are containers in the cloud used to store data like files and folders.

2. Step 2: Identify the correct purpose

   Among the options, only storing and organizing files matches the bucket's role.

3. Final Answer:

   To store and organize files in the cloud -> Option A

4. Quick Check:

   S3 bucket = cloud storage container [OK]

Hint: Buckets are cloud folders for files, not servers or monitoring [OK]

Common Mistakes:

• Confusing buckets with servers
• Thinking buckets manage permissions directly
• Assuming buckets monitor network

2. Which AWS CLI command correctly creates an S3 bucket named my-unique-bucket in the us-east-1 region?

easy

A. aws s3 create-bucket --bucket my-unique-bucket --region us-east-1

B. aws s3 mb my-unique-bucket --region us-east-1

C. aws s3api create-bucket --bucket my-unique-bucket --region us-east-1

D. aws s3api create-bucket --bucket my-unique-bucket --create-region us-east-1

Solution

1. Step 1: Identify the correct AWS CLI syntax for creating buckets

   The aws s3api create-bucket command is the standard for bucket creation with region specification.

2. Step 2: Check the region parameter correctness

   The correct parameter is --region, not --create-region. Also, aws s3 mb is shorthand but requires the bucket URL format.

3. Final Answer:

   aws s3api create-bucket --bucket my-unique-bucket --region us-east-1 -> Option C

4. Quick Check:

   Correct CLI syntax = aws s3api create-bucket --bucket my-unique-bucket --region us-east-1 [OK]

Hint: Use 'aws s3api create-bucket' with --region for bucket creation [OK]

Common Mistakes:

• Using 'aws s3 mb' without s3:// prefix
• Wrong parameter name like --create-region
• Omitting the --region parameter

3. What will happen if you run this command?

aws s3api create-bucket --bucket my.bucket.name --region us-west-2

medium

A. Command fails due to missing ACL parameter

B. Bucket is created successfully in us-west-2

C. Bucket is created but in default region us-east-1

D. Error because bucket name contains dots and region requires special config

Solution

1. Step 1: Understand bucket naming rules and region requirements

   Bucket names with dots require special handling in regions other than us-east-1 due to SSL certificate validation.

2. Step 2: Analyze the command behavior

   Without specifying the --create-bucket-configuration for us-west-2, the command will fail because of the dot in the bucket name and region mismatch.

3. Final Answer:

   Error because bucket name contains dots and region requires special config -> Option D

4. Quick Check:

   Dots in bucket + region ≠ simple create [OK]

Hint: Buckets with dots need extra config outside us-east-1 [OK]

Common Mistakes:

• Assuming bucket creates without error
• Ignoring region-specific config for dots
• Thinking ACL is mandatory for creation

4. You tried to create a bucket with this command:

aws s3api create-bucket --bucket 123_invalid_bucket --region us-east-1

But it failed. What is the most likely reason?

medium

A. Bucket name contains underscores which are invalid

B. Bucket name starts with numbers which is not allowed

C. Region us-east-1 does not support bucket creation

D. Missing --acl parameter causes failure

Solution

1. Step 1: Review bucket naming rules

   Bucket names cannot contain underscores (_) but can start with numbers.

2. Step 2: Check command and region validity

   Region us-east-1 supports bucket creation and --acl is optional, so failure is due to invalid underscore in name.

3. Final Answer:

   Bucket name contains underscores which are invalid -> Option A

4. Quick Check:

   Underscores not allowed in bucket names [OK]

Hint: Bucket names cannot have underscores, even if starting with numbers [OK]

Common Mistakes:

• Thinking numbers can't start bucket names
• Assuming region blocks creation
• Believing --acl is required

5. You want to create an S3 bucket named my.bucket.name in eu-west-1 region using AWS CLI. Which command will work correctly?

hard

A. aws s3api create-bucket --bucket my.bucket.name --region eu-west-1

B. aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 --create-bucket-configuration LocationConstraint=eu-west-1

C. aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 --acl public-read

D. aws s3 mb s3://my.bucket.name --region eu-west-1

Solution

1. Step 1: Understand bucket creation with dots in non-us-east-1 regions

   Bucket names with dots require specifying --create-bucket-configuration LocationConstraint for regions other than us-east-1.

2. Step 2: Analyze each command option

   aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 misses the configuration, so it fails. aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 --create-bucket-configuration LocationConstraint=eu-west-1 correctly includes the LocationConstraint. aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 --acl public-read adds ACL but misses LocationConstraint. aws s3 mb s3://my.bucket.name --region eu-west-1 uses shorthand but lacks configuration for dots.

3. Final Answer:

   aws s3api create-bucket --bucket my.bucket.name --region eu-west-1 --create-bucket-configuration LocationConstraint=eu-west-1 -> Option B

4. Quick Check:

   Dots + region ≠ no config; use LocationConstraint [OK]

Hint: Add LocationConstraint for buckets with dots outside us-east-1 [OK]

Common Mistakes:

• Omitting LocationConstraint for regions with dots
• Assuming ACL fixes creation errors
• Using shorthand without config for dots