Template structure (JSON/YAML) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the AWS CloudFormation template version.

AWS

{
  "AWSTemplateFormatVersion": "[1]",
  "Resources": {}
}

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

A2010-09-09

B2020-01-01

C2005-12-15

D2015-07-30

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect date format.

Leaving the version field empty.

The correct AWS CloudFormation template version is 2010-09-09.

2fill in blank

medium

Complete the code to specify the description field in the AWS CloudFormation template.

AWS

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Description": "[1]",
  "Resources": {}
}

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

ATemplate Metadata

BMy AWS CloudFormation Template

CResource Definitions

DAWS Template Version

Attempts:

3 left

💡 Hint

Common Mistakes

Using technical terms instead of a description.

Leaving the description empty.

The Description field should be a short text describing the template, such as My AWS CloudFormation Template.

3fill in blank

hard

Fix the error in the Resources section by completing the resource type.

AWS

{
  "Resources": {
    "MyBucket": {
      "Type": "[1]",
      "Properties": {
        "BucketName": "my-sample-bucket"
      }
    }
  }
}

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

AAWS::S3::Bucket

BAWS::Lambda::Function

CAWS::EC2::Instance

DAWS::DynamoDB::Table

Attempts:

3 left

💡 Hint

Common Mistakes

Using EC2 instance type for a bucket.

Using Lambda function type for a bucket.

The resource type for an S3 bucket is AWS::S3::Bucket.

4fill in blank

hard

Fill both blanks to define an EC2 instance with a specific instance type and AMI ID.

AWS

{
  "Resources": {
    "MyInstance": {
      "Type": "AWS::EC2::Instance",
      "Properties": {
        "InstanceType": "[1]",
        "ImageId": "[2]"
      }
    }
  }
}

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

At2.micro

Bami-0abcdef1234567890

Cm5.large

Dami-1234567890abcdef0

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing instance types and AMI IDs.

Using invalid AMI IDs.

The InstanceType is commonly t2.micro for small instances, and the ImageId is a valid AMI ID like ami-0abcdef1234567890.

5fill in blank

hard

Fill all three blanks to define an IAM role with assume role policy and managed policy ARN.

AWS

{
  "Resources": {
    "MyRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "AssumeRolePolicyDocument": [1],
        "Path": "[2]",
        "ManagedPolicyArns": ["[3]"]
      }
    }
  }
}

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

A{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": {"Service": "ec2.amazonaws.com"}, "Action": "sts:AssumeRole" }] }

B/

Carn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess

D{}

Attempts:

3 left

💡 Hint

Common Mistakes

Using empty or incorrect policy documents.

Wrong path format.

Incorrect or missing policy ARN.

The AssumeRolePolicyDocument must allow EC2 service to assume the role, the Path is usually "/", and the ManagedPolicyArns can include the AmazonS3ReadOnlyAccess policy ARN.