Aws Rds Database

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Deploy and manage relational databases using RDS with Multi-AZ, read replicas, backups, and encryption. Use for PostgreSQL, MySQL, MariaDB, and Oracle.

Includes scriptsDevOps & Cloud
AI-generated overview

Deploys and manages Amazon RDS relational databases with Multi-AZ, read replicas, backups and encryption.

What it does
This skill guides the deployment and operation of Amazon RDS relational databases across PostgreSQL, MySQL, MariaDB, Oracle and SQL Server engines. It provides AWS CLI and Terraform configuration guidance, connection and configuration references, a schema validation script, and a SQL migration template. It covers high availability with Multi-AZ, read replicas, automated backups, encryption and credential handling.
When to use it
Use it when provisioning or operating relational databases on Amazon RDS, including transactional and OLTP workloads, read-heavy applications needing replicas, and development, staging or disaster recovery environments. It also suits teams that need guidance on backups, encryption and IAM database authentication.
Requirements
Requires AWS account access with permissions for RDS, EC2 security groups and related services, plus the AWS CLI or Terraform for the documented workflows. It ships an executable script (scripts/validate-schema.sh) and reference documents and a SQL migration template.

AWS RDS Database

Table of Contents

Overview

Amazon RDS simplifies relational database deployment and operations. Support multiple database engines with automated backups, replication, encryption, and high availability through Multi-AZ deployments.

When to Use

  • PostgreSQL and MySQL applications
  • Transactional databases and OLTP
  • Oracle and Microsoft SQL Server workloads
  • Read-heavy applications with replicas
  • Development and staging environments
  • Data requiring ACID compliance
  • Applications needing automatic backups
  • Disaster recovery scenarios

Quick Start

Minimal working example:

bash
# Create DB subnet groupaws rds create-db-subnet-group \  --db-subnet-group-name app-db-subnet \  --db-subnet-group-description "App database subnet" \  --subnet-ids subnet-12345 subnet-67890
# Create security group for RDSaws ec2 create-security-group \  --group-name rds-sg \  --description "RDS security group" \  --vpc-id vpc-12345
# Allow inbound PostgreSQLaws ec2 authorize-security-group-ingress \  --group-id sg-rds123 \  --protocol tcp \  --port 5432 \  --source-security-group-id sg-app123
# Create RDS instanceaws rds create-db-instance \  --db-instance-identifier myapp-db \  --db-instance-class db.t3.micro \  --engine postgres \  --engine-version 15.2 \// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
RDS Instance Creation with AWS CLI [blocked]RDS Instance Creation with AWS CLI
Terraform RDS Configuration [blocked]Terraform RDS Configuration
Database Connection and Configuration [blocked]Database Connection and Configuration

Best Practices

✅ DO

  • Use Multi-AZ for production
  • Enable automated backups
  • Use encryption at rest and in transit
  • Implement IAM database authentication
  • Create read replicas for scaling
  • Monitor performance metrics
  • Set up CloudWatch alarms
  • Store credentials in Secrets Manager
  • Use parameter groups for configuration

❌ DON'T

  • Store passwords in code
  • Disable encryption
  • Use public accessibility in production
  • Ignore backup retention
  • Skip automated backups
  • Create databases without Multi-AZ

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/aws-rds-databaseat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal