Why managed databases matter in AWS - See It in Action

Why Managed Databases Matter

📖 Scenario: You are working for a small online store that wants to keep its customer data safe and accessible without spending too much time managing servers. You will create a simple AWS setup to understand why using a managed database service is helpful.

🎯 Goal: Build a basic AWS infrastructure using a managed database service to store customer information securely and reliably.

📋 What You'll Learn

Create an AWS RDS instance using a managed database service

Configure the database instance with basic settings

Set up a security group to allow access only from the application server

Understand how managed databases reduce manual work and improve reliability

💡 Why This Matters

🌍 Real World

Managed databases are used by companies to avoid the hassle of installing, patching, and backing up database software manually. This lets teams focus on building applications instead of managing servers.

💼 Career

Cloud architects and DevOps engineers often design infrastructure using managed services like AWS RDS to ensure reliability, security, and scalability with less operational overhead.

1

Create an AWS RDS instance resource

Write the AWS CloudFormation YAML code to create an RDS database instance resource named CustomerDB with engine mysql and instance class db.t3.micro.

AWS

# Your code here to create the RDS instance resource

Hint

Use AWS::RDS::DBInstance resource type with the specified properties.

2

Add a security group for the database

Add a security group resource named DBSecurityGroup that allows inbound MySQL traffic (port 3306) only from the application server's security group AppServerSG.

AWS

Resources:
  CustomerDB:
    Type: AWS::RDS::DBInstance
    Properties:
      DBInstanceIdentifier: CustomerDB
      Engine: mysql
      DBInstanceClass: db.t3.micro
      AllocatedStorage: 20
      MasterUsername: admin
      MasterUserPassword: password123

# Your code here to add DBSecurityGroup resource

Hint

Use AWS::EC2::SecurityGroup with ingress rule for port 3306 from AppServerSG.

3

Configure database backup and multi-AZ

Update the CustomerDB resource to enable automated backups with a retention period of 7 days and enable Multi-AZ deployment for high availability.

AWS

Resources:
  CustomerDB:
    Type: AWS::RDS::DBInstance
    Properties:
      DBInstanceIdentifier: CustomerDB
      Engine: mysql
      DBInstanceClass: db.t3.micro
      AllocatedStorage: 20
      MasterUsername: admin
      MasterUserPassword: password123
      VPCSecurityGroups:
        - !Ref DBSecurityGroup

# Your code here to add BackupRetentionPeriod and MultiAZ properties

  DBSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupDescription: Allow MySQL access from AppServerSG
      SecurityGroupIngress:
        - IpProtocol: tcp
          FromPort: 3306
          ToPort: 3306
          SourceSecurityGroupId: !Ref AppServerSG

Hint

Add BackupRetentionPeriod and MultiAZ properties inside CustomerDB properties.

4

Add a tag to identify the environment

Add a tag to the CustomerDB resource with key Environment and value Production.

AWS

Resources:
  CustomerDB:
    Type: AWS::RDS::DBInstance
    Properties:
      DBInstanceIdentifier: CustomerDB
      Engine: mysql
      DBInstanceClass: db.t3.micro
      AllocatedStorage: 20
      MasterUsername: admin
      MasterUserPassword: password123
      VPCSecurityGroups:
        - !Ref DBSecurityGroup
      BackupRetentionPeriod: 7
      MultiAZ: true

# Your code here to add Tags property

  DBSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupDescription: Allow MySQL access from AppServerSG
      SecurityGroupIngress:
        - IpProtocol: tcp
          FromPort: 3306
          ToPort: 3306
          SourceSecurityGroupId: !Ref AppServerSG

Hint

Add a Tags list with the specified key and value inside CustomerDB properties.

Practice

1. What is the main benefit of using a managed database service in AWS?

easy

A. It requires manual setup of hardware

B. It only works with specific programming languages

C. It needs you to manage software updates

D. It handles backups and maintenance automatically

Solution

1. Step 1: Understand managed database features

   Managed databases automate tasks like backups, patching, and scaling.

2. Step 2: Compare options

   The other options refer to manual tasks like hardware setup, software updates, or language restrictions, which are handled automatically by managed services.

3. Final Answer:

   It handles backups and maintenance automatically -> Option D

4. Quick Check:

   Managed databases automate maintenance [OK]

Hint: Managed means AWS does the hard work for you [OK]

Common Mistakes:

• Thinking you must manually update software
• Assuming hardware setup is required
• Believing managed DBs limit programming languages

2. Which AWS service is a managed relational database?

easy

A. Amazon RDS

B. Amazon EC2

C. Amazon S3

D. AWS Lambda

Solution

1. Step 1: Identify AWS services

   Amazon RDS is designed for managed relational databases.

2. Step 2: Eliminate other options

   EC2 is virtual servers, S3 is storage, Lambda is serverless compute.

3. Final Answer:

   Amazon RDS -> Option A

4. Quick Check:

   Managed relational DB = RDS [OK]

Hint: RDS = managed relational database service [OK]

Common Mistakes:

• Confusing EC2 with database service
• Thinking S3 stores databases
• Assuming Lambda manages databases

3. Consider this AWS RDS feature: automatic backups. What happens if you delete your database instance?

medium

A. Backups are converted to snapshots automatically

B. Backups are deleted immediately

C. Backups are kept for the retention period

D. Backups are sent to Amazon S3 Glacier

Solution

1. Step 1: Understand RDS backup retention

   RDS keeps automated backups for the retention period even after the DB instance is deleted, unless you delete the backups manually or disable retention.

2. Step 2: Review other options

   Backups are not converted to snapshots automatically, nor deleted immediately by default, and are not sent to Glacier automatically.

3. Final Answer:

   Backups are kept for the retention period -> Option C

4. Quick Check:

   RDS retains automated backups for retention period after deletion [OK]

Hint: RDS retains automated backups for retention period after DB instance deletion [OK]

Common Mistakes:

• Thinking backups are deleted immediately
• Thinking backups auto-convert to snapshots
• Believing backups move to Glacier by default

4. You set up an AWS managed database but notice it is not scaling automatically. What is the most likely cause?

medium

A. The database engine does not support backups

B. Auto scaling is not enabled or configured

C. You did not create a security group

D. The database is running on EC2 instances

Solution

1. Step 1: Check auto scaling settings

   Managed databases require auto scaling to be enabled to scale automatically.

2. Step 2: Eliminate unrelated causes

   Backups support is unrelated to scaling; security groups control access; EC2 is not managed DB.

3. Final Answer:

   Auto scaling is not enabled or configured -> Option B

4. Quick Check:

   Auto scaling off means no scaling [OK]

Hint: Auto scaling must be enabled for automatic scaling [OK]

Common Mistakes:

• Confusing backups with scaling
• Ignoring security group role
• Thinking EC2 is managed DB

5. You want to build a web app that requires a database with automatic backups, scaling, and security without manual maintenance. Which AWS approach best fits this need?

hard

A. Use Amazon RDS with Multi-AZ deployment and automated backups enabled

B. Deploy a database on EC2 and schedule manual backups

C. Store data in Amazon S3 and manage backups yourself

D. Use AWS Lambda functions to handle database scaling

Solution

1. Step 1: Identify managed database features needed

   Automatic backups, scaling, and security are built into Amazon RDS with Multi-AZ and backups enabled.

2. Step 2: Compare other options

   EC2 requires manual maintenance; S3 is object storage, not a database; Lambda is compute, not DB scaling.

3. Final Answer:

   Use Amazon RDS with Multi-AZ deployment and automated backups enabled -> Option A

4. Quick Check:

   Managed DB with backups and scaling = RDS Multi-AZ [OK]

Hint: Managed RDS with Multi-AZ covers backups and scaling [OK]

Common Mistakes:

• Choosing EC2 for managed features
• Confusing S3 with database storage
• Using Lambda for database scaling