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

Need a 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

Need a 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

Need a 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

Need a hint?

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