All Services
Database
Amazon Relational Database Service
Amazon RDS operates supported relational database engines with managed provisioning, backups, patching, monitoring, storage, and high-availability deployment options.
Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Relational Database Service.
Amazon Relational Database Service pricing and cost programs
Pricing model: Managed relational database usage
- On-Demand
- Available
- Reserved Instances or reserved capacity
- Available
- Savings Plans
- Available
- Spot
- Not applicable
Billing dimensions: DB instance time · Storage and I/O · Backups · Data transfer
Programs and modes: On-Demand DB Instances · Reserved DB Instances · Database Savings Plans · Extended Support
Engine, Region, deployment, and license model affect Reserved DB Instance and Savings Plans eligibility.
Free Tier: Available — verify current offers
Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.
Official AWS pricing
Official AWS sources reviewed 2026-07-21.
Why implement Amazon Relational Database Service?
- Removes operating-system and database-host provisioning, routine patching, automated backups, storage replacement, and Multi-AZ replication management.
- Supports familiar relational engines and SQL tooling with controlled instance, storage, parameter, maintenance, backup, and read-scaling options.
- Integrates private VPC networking, KMS, Secrets Manager, IAM features for supported engines, CloudWatch, Performance Insights, and AWS Backup.
How to implement Amazon Relational Database Service
- Choose the engine, supported version, license model, instance class, storage, Multi-AZ topology, backup retention, maintenance window, and parameter settings from compatibility and measured workload needs.
- Create subnet and parameter groups, deploy encrypted instances in private subnets, restrict security groups, keep credentials in Secrets Manager, and require encrypted client connections.
- Migrate and validate schema and data, establish pooling and retry behavior, enable logs and monitoring, and rehearse backup restore, failover, scaling, patching, and deletion recovery.
Amazon Relational Database Service best practices
- Use Multi-AZ for production availability and read replicas for read scaling or regional recovery; do not confuse a read replica with an automatic Multi-AZ standby.
- Monitor CPU, memory, connections, storage, IOPS, latency, locks, replica lag, and slow queries; tune SQL and indexes before simply increasing instance size.
- Keep supported minor versions current, use least privilege and TLS, protect backups and deletion, test restoration and failover, and use connection pooling or RDS Proxy for bursty clients.
Amazon Relational Database Service use cases and server impact
- Transactional web and business applications
- Managed commercial or open-source relational databases
- Read-scaled reporting from operational SQL data
Replaces relational database hosts and much routine DBA infrastructure, while schema design, query tuning, capacity decisions, compatibility, and recovery testing remain shared responsibilities.
Official implementation resources
How Amazon Relational Database Service works with other AWS services
Arrows show the documented technical direction. Reciprocal navigation does not imply a reverse technical dependency.
Official AWS sources reviewed 2026-07-25.
Amazon Virtual Private Cloud → Amazon Relational Database Service
An RDS DB instance or cluster is placed in a DB subnet group and accepts connections according to VPC routing and security groups.
- Why teams use it
- A private data tier limits database exposure while allowing approved application tiers to connect.
- Permissions and networking
- Use subnets across Availability Zones, allow only the application security group and database port, and keep public accessibility disabled unless required.
- Pricing and security caveats
- Multi-AZ, cross-AZ transfer, NAT, and endpoints have separate cost implications. Network isolation does not replace database authentication or encryption.
Amazon Relational Database Service → Amazon CloudWatch
RDS publishes service metrics to CloudWatch and can export selected database logs for centralized retention and analysis.
- Why teams use it
- Teams can alarm on capacity and availability symptoms while correlating database behavior with application telemetry.
- Permissions and networking
- Enable only needed log exports, restrict log access, and combine metrics with database-native diagnostics for engine-level analysis.
- Pricing and security caveats
- Enhanced monitoring, Performance Insights features, log ingestion, storage, and alarms can add cost; metrics alone do not prove query root cause.
AWS Backup → Amazon Relational Database Service
AWS Backup applies centrally managed plans and vault controls to supported RDS instances and clusters by using service backup capabilities.
- Why teams use it
- Central policies, retention, reporting, and cross-account controls can standardize database protection.
- Permissions and networking
- Coordinate RDS native and AWS Backup windows, test restores, separate backup administration, and verify feature support for the engine, deployment, and Region.
- Pricing and security caveats
- Backup storage, restores, copies, and data transfer can add cost; overlapping retention can create unexpected storage and an untested backup is not a recovery plan.
Architecture patterns using this service
Planning guides that use Amazon Relational Database Service