# Amazon RDS Cloud service · AWS. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-services-hub/amazon-rds > Amazon RDS (Relational Database Service) is a managed service provided by Amazon Web Services (AWS) that makes it easier to set up, operate, and scale a relational database in the cloud by handling routine database tasks such as provisioning, patching, backup, recovery, and scaling. Practice exams covering Amazon RDS: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C02 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional). ## 8 key features of Amazon RDS Amazon RDS is a fully-managed database service offering scalability, high availability, security, and support for multiple database engines, with automated backups and monitoring, aimed at easing database management for developers. 1. **Managed Database Service**: Amazon RDS is a managed database service that automates time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups, enabling users to focus on their applications rather than database management. 2. **Support for Multiple Database Engines**: Amazon RDS supports a variety of database engines, including Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle Database, and SQL Server, providing flexibility and options to suit different application requirements. 3. **Scalability**: With Amazon RDS, you can easily scale your database's compute resources or storage capacity with just a few mouse-clicks or an API call, often with no downtime required for many types of adjustments. 4. **High Availability and Disaster Recovery**: Amazon RDS provides high availability and failover support for DB instances using Multi-Availability Zone deployment and offers various disaster recovery solutions to ensure data durability and reliability. 5. **Security**: Amazon RDS features built-in security capabilities, including network isolation using Amazon VPC, encryption at rest using keys you create and control through AWS Key Management Service (KMS), and encryption in transit using SSL. 6. **Automated Backups**: RDS automatically performs a daily system snapshot of your data and stores transaction logs, enabling point-in-time recovery for your database instances. 7. **Monitoring and Metrics**: Using Amazon CloudWatch, RDS provides detailed metrics and logs for monitoring the performance and health of your databases, which helps in identifying and resolving issues rapidly. 8. **Seamless Integration**: RDS is designed to integrate seamlessly with other AWS services like Amazon EC2, Amazon S3, and AWS Lambda, allowing you to build feature-rich applications that are highly scalable and secure. ## Where Amazon RDS is used Amazon RDS supports a variety of use cases including managed web application databases, complex multi-tiered application database support, simplified migration from on-premises to cloud, business continuity and disaster recovery, agile development processes, and microservices backend provisioning. 1. **Managed Database for Web Applications**: Amazon RDS provides a scalable, reliable, and managed database service that is ideal for running relational databases for web applications. It automates time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups. This allows web developers to focus on application logic rather than database management. 2. **Multi-Tiered Application Database**: For applications with complex architectures, such as multi-tiered applications, Amazon RDS serves as a highly available and isolated database tier. It offers various database instance types and supports read replicas to handle the load and ensure consistent performance. 3. **Migration of On-premises Databases to the Cloud**: Organizations looking to migrate their existing on-premises databases to the cloud can use Amazon RDS for a simplified migration process. The AWS Database Migration Service (DMS) can be used along with RDS to securely and efficiently move databases to AWS, helping to reduce overhead and hardware costs. 4. **Business Continuity and Disaster Recovery**: Amazon RDS enhances business continuity and disaster recovery efforts with its built-in replication, automated backups, and database snapshots features. It ensures data durability and allows businesses to quickly recover from unforeseen events affecting database availability. 5. **DevOps and Agile Development**: Developers practicing DevOps and Agile methodologies can benefit from Amazon RDS through its ability to quickly provision database instances for development and testing. It also enables easy scaling of database resources to meet fluctuating demands during different stages of application development. 6. **Microservices Backend**: For microservices architectures, Amazon RDS can serve as a backend that supports a range of database engines well-suited for microservices components. This use case allows each microservice to have its isolated database instance for better performance and scalability. ## How Amazon RDS is priced Amazon RDS pricing models include On-Demand Instances, Reserved Instances, Database Storage and I/Os, Provisioned IOPS, Backup Storage, and Data Transfer costs. - **On-Demand Instances**: DB instance usage is billed in one-second increments with a 10-minute minimum following a billable status change, such as creating, starting, or modifying the DB instance class. - **Reserved Instances**: Provides a discounted hourly rate and an optional upfront payment, giving you the option to reserve a database instance for a one or three-year term. The pricing varies based on the instance type, region, database engine, and payment option. - **Database Storage and I/Os**: Database storage charges are based on provisioned capacity per GB-month, prorated when provisioned capacity changes. Per-request I/O charges apply only to Amazon RDS magnetic storage and Amazon Aurora. - **Provisioned IOPS**: If your application requires a consistent and high I/O rate, you can provision additional input/output operations per second (IOPS). The pricing of provisioned IOPS is separate from the storage cost and is based on the amount of IOPS provisioned. - **Backup Storage**: Amazon RDS provides a backup storage amount equal to the size of your database instance for free, which is based on your provisioned database storage. Additional backup storage beyond the provided amount is chargeable. - **Data Transfer**: Data transfer IN to Amazon RDS is usually free, but data transfer OUT from Amazon RDS to the internet may incur charges depending on the amount of data and the region. - **Database Savings Plans**: Eligible RDS usage can receive discounted pricing in exchange for a commitment to a specific amount of usage, measured in dollars per hour, over a one-year term. - **RDS Extended Support**: RDS Extended Support allows continued use of MySQL and PostgreSQL major versions after community end-of-life, with critical security and bug fixes for up to three additional years. It is charged per vCPU-hour for provisioned Aurora, RDS for MySQL, and RDS for PostgreSQL instances, or per consumed ACU-hour for Aurora Serverless v2; pricing also depends on the calendar date. - **Public IPv4 Addresses**: Standard public IPv4 address charges apply to public IPv4 addresses associated with resources launched in an Amazon VPC. - **Free Tier**: For AWS Free Tier signups after July 15, 2025, either the Free Plan or Paid Plan provides $100 in credits, with up to an additional $100 for activating foundational AWS services. Free Tier credits are valid for up to 12 months. ## Services Amazon RDS works with - **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon RDS integrates with Amazon EC2 to enable applications hosted on EC2 instances to easily access and interact with managed relational databases. - **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon RDS seamlessly integrates with Amazon Virtual Private Cloud (VPC) to provide secure and isolated networking environments for databases. ## What is Amazon RDS Amazon Relational Database Service (Amazon RDS) is a managed database service offered by Amazon Web Services (AWS) designed to simplify the setup, operation, and scaling of a relational database in the cloud. It provides resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups. This service seeks to free users from the routine database administration tasks, allowing them to focus on application development and business insights. Amazon RDS supports a variety of database engines, catering to the diverse needs and preferences of developers and businesses. Users can choose from several widely-used database engines including Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle Database, and SQL Server. Each of these options comes with their set of features, performance characteristics, and pricing, giving users the flexibility to select the one that best fits their application's requirements. Amazon RDS Custom provides a managed deployment option for applications that require customization of the underlying operating system and database environment. Amazon RDS on AWS Outposts lets you deploy fully managed database instances in on-premises environments. One of the key benefits of Amazon RDS is its scalability. Users can start with a modestly sized database instance and scale up to larger and more powerful instances as their needs grow, with just a few clicks or an API call. It's also possible to scale the database storage and compute resources with minimal downtime, which is crucial for maintaining a seamless user experience. Amazon Aurora Serverless v2 offers an alternative to provisioned Aurora instances, automatically adjusting database capacity to match application demand. Additionally, RDS supports read replicas which enhance the read scalability and performance for read-heavy database workloads. Another hallmark of RDS is its durability and reliability. Amazon RDS is designed to be highly available and has features such as automated backups, database snapshots, and multi-AZ (Availability Zone) deployments which enhance data protection and allow the database to be resilient against failures. In the case of multi-AZ deployments, the service automatically replicates the data to a standby instance in a different AZ, which provides failover support in the event of an infrastructure failure. Amazon RDS security is also a key focus, with AWS providing numerous controls to help safeguard your databases. These include network isolation using Amazon VPC, encryption at rest using keys you create and control through AWS Key Management Service (KMS), and encryption in transit using SSL. For RDS for MySQL and RDS for PostgreSQL, Multi-AZ DB clusters provide another deployment option: one writer and two readable standby instances across three Availability Zones, combining failover support with read capacity. Additionally, Amazon RDS is fully compliant with many industry standards, thus making it an appropriate choice for applications that require strict data regulations. The service offers automated software patching, allowing you to ensure your database is running with the latest patches for improved security and performance. Amazon RDS also provides detailed monitoring and metrics for your database instances through Amazon CloudWatch, giving you deep insight into performance and health. In summary, Amazon RDS offers a potent combination of simplicity, scalability, and robustness for managing relational databases in the cloud, significantly reducing the administrative burden and freeing developers to focus on innovation and application optimization. Its broad database engine compatibility ensures that enterprises and developers can operate their preferred databases without needing to invest in hardware and perform routine maintenance, all while benefiting from the elasticity and power of cloud computing. ## Free Amazon RDS tools - [RDS Max Connections Calculator](https://blowstack.com/tools/aws-rds-max-connections-calculator): Find the default max_connections per engine and DB instance class, and budget connections for Lambda, pods and RDS Proxy. ## Concepts related to Amazon RDS - [7 Rs of Migration](https://blowstack.com/tools/cloud-concepts-hub/7-rs-of-migration): The 7 Rs of Migration are seven strategies for deciding whether and how to move applications and workloads to the cloud. - [ACID Transactions](https://blowstack.com/tools/cloud-concepts-hub/acid-transactions): ACID transactions group data operations into a reliable unit of work with atomicity, consistency, isolation, and durability guarantees. - [Approximate Nearest Neighbor Search](https://blowstack.com/tools/cloud-concepts-hub/approximate-nearest-neighbor-search): Approximate Nearest Neighbor Search uses indexes to find vectors close to a query vector while trading guaranteed exact results for lower search cost and latency. - [AWS global infrastructure](https://blowstack.com/tools/cloud-concepts-hub/aws-global-infrastructure): AWS global infrastructure is the worldwide arrangement of Regions, Availability Zones, and edge locations that provides the physical foundation for deploying and delivering cloud workloads. - [Backpressure](https://blowstack.com/tools/cloud-concepts-hub/backpressure): Backpressure is feedback from a constrained downstream component that causes upstream components to slow or pause production. - [Backup and Restore](https://blowstack.com/tools/cloud-concepts-hub/backup-and-restore): Backup and Restore is the practice of preserving recoverable copies of data and using them to return systems or information to a usable state after loss, corruption, or disruption. - [Backward Compatibility](https://blowstack.com/tools/cloud-concepts-hub/backward-compatibility): Backward compatibility is the ability of an updated system, interface, or data reader to continue supporting the contracts or data of earlier versions. - [Benefits of migrating to the AWS Cloud](https://blowstack.com/tools/cloud-concepts-hub/benefits-of-migrating-to-the-aws-cloud): Benefits of migrating to the AWS Cloud are the operational, financial, and business advantages of using on-demand cloud resources instead of owning and managing all underlying infrastructure. - [Bring Your Own License](https://blowstack.com/tools/cloud-concepts-hub/bring-your-own-license): Bring Your Own License (BYOL) is a licensing model in which customers use eligible software licenses they already own or obtain separately to run software on cloud infrastructure. - [Cache-Aside](https://blowstack.com/tools/cloud-concepts-hub/cache-aside): Cache-aside is a caching pattern in which application code checks a cache first and, on a miss, reads from the authoritative data store and populates the cache. - [Cloud Service Models](https://blowstack.com/tools/cloud-concepts-hub/cloud-service-models): Cloud service models define which technology layers a provider operates and which responsibilities remain with the customer. - [Composite Availability](https://blowstack.com/tools/cloud-concepts-hub/composite-availability): Composite availability is the end-to-end availability of a system determined by its required dependencies, redundant components, and failure relationships. - [Concurrency Control](https://blowstack.com/tools/cloud-concepts-hub/concurrency-control): Concurrency control coordinates simultaneous access to shared data so that overlapping operations preserve the required consistency and isolation guarantees. - [Connection Pooling](https://blowstack.com/tools/cloud-concepts-hub/connection-pooling): Connection pooling maintains a reusable set of network connections so applications can borrow them instead of establishing a new connection for every operation. - [Data Durability](https://blowstack.com/tools/cloud-concepts-hub/data-durability): Data durability is the ability of a storage system to preserve data over time without permanent loss. - [Data Integrity](https://blowstack.com/tools/cloud-concepts-hub/data-integrity): Data integrity is the assurance that data remains accurate, complete, consistent, and protected against unauthorized or unintended changes throughout its lifecycle. - [Data Locality](https://blowstack.com/tools/cloud-concepts-hub/data-locality): Data locality is the placement of data and the workloads that use it close together to reduce network movement, latency, and transfer costs. - [Data Replication](https://blowstack.com/tools/cloud-concepts-hub/data-replication): Data replication is the process of maintaining copies of the same data on multiple storage systems or locations and propagating changes between them. - [Data Sovereignty](https://blowstack.com/tools/cloud-concepts-hub/data-sovereignty): Data sovereignty is the principle that data is subject to the laws and governing authority of the jurisdictions that apply to it. - [Database](https://blowstack.com/tools/cloud-concepts-hub/database): A database is an organized collection of data that applications can efficiently store, retrieve, update, and manage. - [Database Indexing](https://blowstack.com/tools/cloud-concepts-hub/database-indexing): Database indexing uses auxiliary data structures to locate records efficiently without scanning all stored data. - [Database Normalization](https://blowstack.com/tools/cloud-concepts-hub/database-normalization): Database normalization organizes relational data into tables according to dependencies to reduce redundancy and prevent inconsistent updates. - [Database Replication](https://blowstack.com/tools/cloud-concepts-hub/database-replication): Database replication copies database data and propagates changes to other database instances or locations to support migration, availability, and read scaling. - [Deadlocks](https://blowstack.com/tools/cloud-concepts-hub/deadlocks): Deadlocks occur when transactions or processes form a cycle of resource dependencies, leaving each waiting for another to release a resource. - [Encryption](https://blowstack.com/tools/cloud-concepts-hub/encryption): Encryption is the process of transforming readable data into ciphertext using a cryptographic algorithm and a key to protect its confidentiality. - [Encryption at Rest](https://blowstack.com/tools/cloud-concepts-hub/encryption-at-rest): Encryption at rest protects stored data by converting it into ciphertext that requires the appropriate cryptographic keys to read. - [Eventual Consistency](https://blowstack.com/tools/cloud-concepts-hub/eventual-consistency): Eventual consistency is a distributed-data model in which replicas may temporarily return different values but converge if updates stop and replication completes successfully. - [Failover](https://blowstack.com/tools/cloud-concepts-hub/failover): Failover is the transfer of traffic or processing from a failed or unhealthy resource to a healthy alternative so a service can continue operating. - [Fault Isolation](https://blowstack.com/tools/cloud-concepts-hub/fault-isolation): Fault isolation is the design principle of containing failures within defined boundaries so they do not disrupt otherwise healthy parts of a system. - [Fault Tolerance](https://blowstack.com/tools/cloud-concepts-hub/fault-tolerance): Fault tolerance is the ability of a system to continue performing its intended function when one or more components fail. - [Heterogeneous Migration](https://blowstack.com/tools/cloud-concepts-hub/heterogeneous-migration): Heterogeneous migration moves a database from one database engine to a different engine, requiring compatible data structures and application behavior on the destination. - [High availability](https://blowstack.com/tools/cloud-concepts-hub/high-availability): High availability is the design and operation of a system to remain accessible and usable despite component failures or maintenance. - [Homogeneous Migration](https://blowstack.com/tools/cloud-concepts-hub/homogeneous-migration): Homogeneous migration moves a database between environments while retaining the same database engine, such as PostgreSQL to PostgreSQL. - [IOPS](https://blowstack.com/tools/cloud-concepts-hub/iops): IOPS, or input/output operations per second, measures the rate at which a storage system completes read and write operations. - [JDBC](https://blowstack.com/tools/cloud-concepts-hub/jdbc): JDBC (Java Database Connectivity) is a standard Java API for connecting to databases, executing SQL, and processing results through database-specific drivers. - [License Portability](https://blowstack.com/tools/cloud-concepts-hub/license-portability): License portability is the ability to reuse software license entitlements across eligible infrastructure environments under the software vendor’s licensing terms. - [License-Included Pricing](https://blowstack.com/tools/cloud-concepts-hub/license-included-pricing): License-Included Pricing is a cloud pricing model in which the charge for a resource or service includes the right to use specified commercial software. - [Migration and data transfer](https://blowstack.com/tools/cloud-concepts-hub/migration-and-data-transfer): Migration and data transfer is the planned movement of applications and data between environments, including the methods, costs, and operational controls needed to complete that movement safely. - [Monolithic Architecture](https://blowstack.com/tools/cloud-concepts-hub/monolithic-architecture): Monolithic architecture organizes an application's core functionality into a single deployable unit whose components are released together. - [Multi-Tier Architecture](https://blowstack.com/tools/cloud-concepts-hub/multi-tier-architecture): Multi-tier architecture separates an application into independently deployed tiers with distinct responsibilities and controlled network communication. - [OLTP Versus OLAP](https://blowstack.com/tools/cloud-concepts-hub/oltp-versus-olap): OLTP versus OLAP distinguishes databases optimized for frequent operational transactions from systems optimized for large-scale analytical queries. - [Open Database Connectivity (ODBC)](https://blowstack.com/tools/cloud-concepts-hub/open-database-connectivity-(odbc)): Open Database Connectivity (ODBC) is a standard programming interface that lets applications access data sources through compatible drivers. - [Pilot Light](https://blowstack.com/tools/cloud-concepts-hub/pilot-light): Pilot light is a disaster recovery strategy that keeps essential components and replicated data ready in a recovery environment while leaving most application capacity inactive until needed. - [Point-in-Time Recovery](https://blowstack.com/tools/cloud-concepts-hub/point-in-time-recovery): Point-in-Time Recovery restores a database or other supported data store to its recoverable state at a selected time within a retained recovery window. - [Public Cloud](https://blowstack.com/tools/cloud-concepts-hub/public-cloud): Public cloud is a deployment model in which a third-party provider offers computing resources for use by many customers on provider-operated infrastructure. - [Random I/O](https://blowstack.com/tools/cloud-concepts-hub/random-io): Random I/O is a storage access pattern in which reads or writes target nonconsecutive locations rather than progressing sequentially through data. - [Random Sampling](https://blowstack.com/tools/cloud-concepts-hub/random-sampling): Random sampling selects observations from a defined population using chance rather than their position, convenience, or an engineer’s judgment. - [Read/Write Splitting](https://blowstack.com/tools/cloud-concepts-hub/readwrite-splitting): Read/Write Splitting routes database writes to a primary database and eligible reads to replicas so that read workloads can scale independently. - [Recovery Point Objective](https://blowstack.com/tools/cloud-concepts-hub/recovery-point-objective): Recovery Point Objective (RPO) is the maximum acceptable amount of data loss from a disruption, expressed as a duration of time. - [Recovery Time Objective](https://blowstack.com/tools/cloud-concepts-hub/recovery-time-objective): Recovery Time Objective (RTO) is the target maximum elapsed time for restoring a disrupted workload to an agreed level of service. - [Referential Integrity](https://blowstack.com/tools/cloud-concepts-hub/referential-integrity): Referential integrity ensures that references between related records point to existing, valid target records. - [Relational Data Model](https://blowstack.com/tools/cloud-concepts-hub/relational-data-model): The relational data model organizes data into tables of rows and columns, using keys to identify records and represent relationships between tables. - [Resiliency](https://blowstack.com/tools/cloud-concepts-hub/resiliency): Resiliency is a system’s ability to withstand disruptions and recover while continuing to meet defined business requirements. - [Right-Sizing](https://blowstack.com/tools/cloud-concepts-hub/right-sizing): Right-sizing is matching cloud resource types, configurations, and capacity to workload requirements without unnecessary cost or unacceptable performance risk. - [Rightsizing](https://blowstack.com/tools/cloud-concepts-hub/rightsizing): Rightsizing is matching the type, size, and quantity of cloud resources to workload requirements while meeting performance and availability targets at an appropriate cost. - [Separation of Concerns](https://blowstack.com/tools/cloud-concepts-hub/separation-of-concerns): Separation of concerns is the design principle of dividing a system into distinct responsibilities that interact through clearly defined interfaces. - [Server-Side Encryption](https://blowstack.com/tools/cloud-concepts-hub/server-side-encryption): Server-side encryption is the encryption of data by the service receiving or storing it, rather than by the client before transmission. - [Service Level Objectives](https://blowstack.com/tools/cloud-concepts-hub/service-level-objectives): Service level objectives are measurable targets for the reliability and performance of a service over a defined evaluation period. - [SQL Injection](https://blowstack.com/tools/cloud-concepts-hub/sql-injection): SQL injection is an application vulnerability in which untrusted input changes the structure or meaning of a database query. - [SQL Joins](https://blowstack.com/tools/cloud-concepts-hub/sql-joins): SQL joins combine rows from tables or other relational inputs according to a matching condition and rules for retaining unmatched rows. - [Structured Data](https://blowstack.com/tools/cloud-concepts-hub/structured-data): Structured data is information organized according to a defined schema, with consistent fields, data types, and relationships that support systematic processing. - [Synchronous Replication](https://blowstack.com/tools/cloud-concepts-hub/synchronous-replication): Synchronous replication is a data-protection method that requires a write to satisfy replication acknowledgments from designated replicas before success is returned to the client. - [Time-Series Data](https://blowstack.com/tools/cloud-concepts-hub/time-series-data): Time-series data consists of observations associated with timestamps and analyzed to understand changes over time. - [Transaction Isolation](https://blowstack.com/tools/cloud-concepts-hub/transaction-isolation): Transaction isolation controls how concurrent database transactions observe and affect one another’s data. - [Tree Data Structures](https://blowstack.com/tools/cloud-concepts-hub/tree-data-structures): Tree data structures organize nodes into an acyclic hierarchy of parent–child relationships for efficient navigation, searching, and transformation. - [Uniqueness Constraints](https://blowstack.com/tools/cloud-concepts-hub/uniqueness-constraints): Uniqueness constraints are rules that require a column value or combination of column values to occur no more than once within a defined scope. - [Vertical Scaling](https://blowstack.com/tools/cloud-concepts-hub/vertical-scaling): Vertical scaling changes the capacity of an existing compute resource or database instance by increasing or decreasing its allocated resources rather than changing the number of instances. - [Warm Standby](https://blowstack.com/tools/cloud-concepts-hub/warm-standby): Warm standby is a disaster recovery strategy that keeps a scaled-down, functional copy of a production environment running in a separate recovery location. - [Write-Through Caching](https://blowstack.com/tools/cloud-concepts-hub/write-through-caching): Write-through caching updates the cache and the backing data store synchronously as part of the write operation.