Resources section in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource in AWS CloudFormation.

AWS

Resources:
  MyBucket:
    Type: [1]

Drag options to blanks, or click blank then click option'

AAWS::S3::Bucket

BAWS::EC2::Instance

CAWS::Lambda::Function

DAWS::DynamoDB::Table

Attempts:

3 left

💡 Hint

Common Mistakes

Using EC2 instance type instead of S3 bucket type.

Confusing Lambda function type with S3 bucket.

The Resources section defines AWS resources. To create an S3 bucket, use AWS::S3::Bucket as the resource type.

2fill in blank

medium

Complete the code to add a property to the S3 bucket resource.

AWS

Resources:
  MyBucket:
    Type: AWS::S3::Bucket
    Properties:
      [1]:
        Status: Enabled

Drag options to blanks, or click blank then click option'

AVersioningConfiguration.Status

BVersioningConfiguration

CVersioningConfiguration.Enabled

DPublicAccessBlockConfiguration

Attempts:

3 left

💡 Hint

Common Mistakes

Using dotted notation like VersioningConfiguration.Status instead of proper nesting.

Selecting unrelated properties like PublicAccessBlockConfiguration.

To enable versioning on an S3 bucket, use the VersioningConfiguration property with Status set to Enabled.

3fill in blank

hard

Fix the error in the resource definition by completing the missing property key.

AWS

Resources:
  MyInstance:
    Type: AWS::EC2::Instance
    Properties:
      [1]: t2.micro

Drag options to blanks, or click blank then click option'

AType

BInstanceSize

CInstanceType

DSize

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'InstanceSize' or 'Size' which are invalid property names.

Confusing 'Type' with 'InstanceType'.

The property to specify the EC2 instance size is InstanceType. Using other keys will cause errors.

4fill in blank

hard

Fill both blanks to define an IAM role with a trust policy.

AWS

Resources:
  MyRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument:
        Version: '2012-10-17'
        Statement:
          - Effect: Allow
            Principal:
              Service: [1]
            Action: [2]

Drag options to blanks, or click blank then click option'

Aec2.amazonaws.com

Bsts:AssumeRole

Clambda.amazonaws.com

Diam:PassRole

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong service principal like Lambda for EC2 role.

Using incorrect action such as 'iam:PassRole' in trust policy.

The trust policy for an EC2 role uses ec2.amazonaws.com as the service principal and sts:AssumeRole as the action.

5fill in blank

hard

Fill all three blanks to define an S3 bucket policy allowing public read access.

AWS

Resources:
  PublicBucketPolicy:
    Type: AWS::S3::BucketPolicy
    Properties:
      Bucket: [1]
      PolicyDocument:
        Version: '2012-10-17'
        Statement:
          - Effect: Allow
            Principal: [2]
            Action: [3]
            Resource: arn:aws:s3:::my-public-bucket/*

Drag options to blanks, or click blank then click option'

Amy-public-bucket

B*

Cs3:GetObject

Darn:aws:s3:::my-public-bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the bucket ARN instead of the bucket name in the Bucket property.

Using wrong action like 's3:PutObject' instead of 's3:GetObject'.

The bucket property must be the bucket name. The principal '*' means everyone. The action s3:GetObject allows public read access to objects.

Practice

1. What is the main purpose of the Resources section in an AWS CloudFormation template?

easy

A. To define the cloud parts AWS should create

B. To specify user permissions

C. To write code logic for the application

D. To store data in the cloud

Solution

1. Step 1: Understand the role of the Resources section

   The Resources section lists all the cloud components AWS will build, like servers or databases.

2. Step 2: Compare with other template sections

   Other sections handle permissions or outputs, but Resources is for creating cloud parts.

3. Final Answer:

   To define the cloud parts AWS should create -> Option A

4. Quick Check:

   Resources section = define cloud parts [OK]

Hint: Resources section always defines what AWS builds [OK]

Common Mistakes:

• Confusing Resources with Permissions or Outputs
• Thinking Resources stores data
• Assuming Resources runs application code

2. Which of the following is the correct way to start defining a resource named MyBucket of type AWS::S3::Bucket in the Resources section?

easy

A. "MyBucket": "AWS::S3::Bucket"

B. "Type": "AWS::S3::Bucket", "MyBucket": {}

C. "MyBucket": { "Type": "AWS::S3::Bucket" }

D. "AWS::S3::Bucket": { "MyBucket": {} }

Solution

1. Step 1: Check resource name and type syntax

   Each resource needs a unique name as key, then a block with a Type property.

2. Step 2: Match correct JSON structure

   "MyBucket": { "Type": "AWS::S3::Bucket" } correctly uses the resource name as key and sets Type inside an object.

3. Final Answer:

   "MyBucket": { "Type": "AWS::S3::Bucket" } -> Option C

4. Quick Check:

   Resource name as key + Type property = "MyBucket": { "Type": "AWS::S3::Bucket" } [OK]

Hint: Resource name is key, Type is inside its object [OK]

Common Mistakes:

• Putting Type outside resource object
• Using resource type as key instead of name
• Missing curly braces for resource details

3. Given this Resources snippet in a CloudFormation template:

{
  "MyInstance": {
    "Type": "AWS::EC2::Instance",
    "Properties": {
      "InstanceType": "t2.micro",
      "ImageId": "ami-12345678"
    }
  }
}

What will AWS create when this template is deployed?

medium

A. An EC2 instance of type t2.micro with the specified AMI

B. An S3 bucket named MyInstance

C. A Lambda function with t2.micro memory

D. A database instance with ImageId ami-12345678

Solution

1. Step 1: Identify resource type and properties

   The resource type is AWS::EC2::Instance, which creates a virtual server.

2. Step 2: Understand properties meaning

   InstanceType t2.micro means a small server; ImageId specifies the server image.

3. Final Answer:

   An EC2 instance of type t2.micro with the specified AMI -> Option A

4. Quick Check:

   EC2 instance with given type and image = An EC2 instance of type t2.micro with the specified AMI [OK]

Hint: Type AWS::EC2::Instance means a virtual server [OK]

Common Mistakes:

• Confusing EC2 with S3 or Lambda
• Ignoring Properties section
• Assuming ImageId is a database ID

4. You wrote this Resources section snippet:

{
  "MyBucket": {
    "Type": "AWS::S3::Bucket",
    "Properties": {
      "BucketName": 12345
    }
  }
}

What is the error in this configuration?

medium

A. Type AWS::S3::Bucket is invalid

B. BucketName must be a string, not a number

C. Properties section is missing

D. Resource name cannot be MyBucket

Solution

1. Step 1: Check BucketName property type

   BucketName must be text (string), but 12345 is a number here.

2. Step 2: Validate other parts

   Type and Properties exist and resource name is valid, so no error there.

3. Final Answer:

   BucketName must be a string, not a number -> Option B

4. Quick Check:

   BucketName requires string value = BucketName must be a string, not a number [OK]

Hint: BucketName must be quoted text, not a number [OK]

Common Mistakes:

• Using numbers instead of strings for names
• Misnaming resource types
• Omitting Properties section

5. You want to create two resources in your template: an S3 bucket named MyDataBucket and an EC2 instance named MyWebServer. Which Resources section snippet correctly defines both with minimal required properties?

hard

A. {
"MyDataBucket": {
"Type": "AWS::S3::Bucket",
"Properties": {
"InstanceType": "t3.micro"
}
},
"MyWebServer": {
"Type": "AWS::EC2::Instance"
}
}

B. {
"AWS::S3::Bucket": {
"MyDataBucket": {}
},
"AWS::EC2::Instance": {
"MyWebServer": {
"InstanceType": "t3.micro",
"ImageId": "ami-0abcdef1234567890"
}
}
}

C. {
"MyDataBucket": {
"Type": "AWS::EC2::Instance"
},
"MyWebServer": {
"Type": "AWS::S3::Bucket",
"Properties": {
"InstanceType": "t3.micro"
}
}
}

D. {
"MyDataBucket": {
"Type": "AWS::S3::Bucket"
},
"MyWebServer": {
"Type": "AWS::EC2::Instance",
"Properties": {
"InstanceType": "t3.micro",
"ImageId": "ami-0abcdef1234567890"
}
}
}

Solution

1. Step 1: Verify resource names and types

   MyDataBucket must be AWS::S3::Bucket, MyWebServer must be AWS::EC2::Instance.

2. Step 2: Check required properties for EC2

   EC2 instance requires InstanceType and ImageId properties; S3 bucket can be empty.

3. Step 3: Identify correct JSON structure

   { "MyDataBucket": { "Type": "AWS::S3::Bucket" }, "MyWebServer": { "Type": "AWS::EC2::Instance", "Properties": { "InstanceType": "t3.micro", "ImageId": "ami-0abcdef1234567890" } } } correctly defines both resources with proper types and properties.

4. Final Answer:

   { "MyDataBucket": { "Type": "AWS::S3::Bucket" }, "MyWebServer": { "Type": "AWS::EC2::Instance", "Properties": { "InstanceType": "t3.micro", "ImageId": "ami-0abcdef1234567890" } } } -> Option D

5. Quick Check:

   Correct types and properties for both resources = { "MyDataBucket": { "Type": "AWS::S3::Bucket" }, "MyWebServer": { "Type": "AWS::EC2::Instance", "Properties": { "InstanceType": "t3.micro", "ImageId": "ami-0abcdef1234567890" } } } [OK]

Hint: S3 needs Type only; EC2 needs Type plus InstanceType and ImageId [OK]

Common Mistakes:

• Swapping resource types
• Putting resource names inside types
• Missing required EC2 properties