Bird
Raised Fist0
AWScloud~5 mins

Resources section in AWS - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Introduction
When you create cloud infrastructure with AWS CloudFormation, you need to tell it what resources to make. The Resources section is where you list all the things like servers, databases, or networks you want AWS to set up for you.
When you want to create a virtual server (EC2 instance) automatically.
When you need to set up a database (RDS) as part of your app environment.
When you want to create a storage bucket (S3) to hold files.
When you want to define a network setup like a Virtual Private Cloud (VPC).
When you want to manage all your cloud resources in one file for easy updates.
Config File - template.yaml
template.yaml
AWSTemplateFormatVersion: '2010-09-09'
Description: Simple EC2 instance setup
Resources:
  MyEC2Instance:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-0c55b159cbfafe1f0
      InstanceType: t2.micro
      Tags:
        - Key: Name
          Value: MyTestInstance

The AWSTemplateFormatVersion defines the template version.

The Description explains what this template does.

The Resources section lists all AWS resources to create. Here, MyEC2Instance is a virtual server.

Type tells AWS what kind of resource it is.

Properties set details like the server image and size.

Commands
This command tells AWS CloudFormation to create a new stack named 'my-test-stack' using the template file. It starts building the resources defined in the Resources section.
Terminal
aws cloudformation create-stack --stack-name my-test-stack --template-body file://template.yaml
Expected OutputExpected
An error occurred (ValidationError) when calling the CreateStack operation: Stack with id my-test-stack already exists
→
--stack-name - Names the stack for easy identification.
→
--template-body - Specifies the local template file to use.
This command checks the status and details of the stack named 'my-test-stack' to see if the resources were created successfully.
Terminal
aws cloudformation describe-stacks --stack-name my-test-stack
Expected OutputExpected
{ "Stacks": [ { "StackName": "my-test-stack", "StackStatus": "CREATE_COMPLETE", "CreationTime": "2024-06-01T12:00:00.000Z" } ] }
→
--stack-name - Specifies which stack to describe.
Key Concept

If you remember nothing else from this pattern, remember: the Resources section is where you list every AWS resource you want CloudFormation to create and manage.

Common Mistakes
Leaving out the Resources section or misspelling resource names.
CloudFormation won't know what to create and will give an error or create nothing.
Always include a properly named Resources section with valid resource definitions.
Using incorrect resource Types or invalid property names.
CloudFormation will fail to create the stack due to validation errors.
Check AWS documentation for correct resource Types and property names before writing the template.
Summary
The Resources section in a CloudFormation template lists all AWS resources to create.
Each resource needs a unique name, a Type, and Properties to define it.
Use AWS CLI commands to create the stack and check its status after deployment.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard