Amazon Aurora

Amazon Aurora is a managed relational database service built around PostgreSQL, MySQL, and DSQL engines. It is a strong match for teams already operating in AWS that want familiar SQL compatibility with infrastructure tasks handled through RDS. The trade-off is pricing complexity: outside the tightly limited free option, your bill follows capacity, storage, I/O, engine, Region, and configuration.

Overview

Aurora centralizes provisioning, patching, backup, and recovery in the Amazon RDS console, command-line interface, and API. Aurora PostgreSQL and Aurora MySQL retain open-source compatibility, so existing applications and tools can often run without modification. Standard migration tools support moving MySQL and PostgreSQL databases to and from Aurora, while Babelfish can support legacy SQL Server applications on Aurora PostgreSQL with minimal code changes.

AWS claims up to six times the throughput of PostgreSQL and MySQL, and designs Aurora for up to 99.99% availability in one Region or 99.999% across multiple Regions. Those are useful design targets for enterprise and globally distributed workloads, but they do not promise a particular application's performance or uptime.

Key features

Managed operations and elastic capacity

Aurora Serverless can start, stop, and adjust capacity as demand changes, charging for the capacity consumed. This suits intermittent or unpredictable workloads that should not run at a fixed provisioned capacity. Provisioned configurations remain available for steadier workloads, but storage, I/O, and optional features can add to either model's cost.

Security and compliance

Encryption at rest uses AWS KMS keys, while SSL with AES-256 protects data in transit. Amazon GuardDuty RDS Protection profiles and monitors Aurora login activity for suspicious behavior. AWS includes Aurora in compliance programs such as SOC, PCI, FedRAMP, and HIPAA, which can help regulated teams assess it against their requirements.

AWS integrations

Aurora MySQL can invoke AWS Lambda and exchange data with Amazon S3. These integrations are most relevant when the rest of an application already uses AWS services; they offer less advantage to teams seeking a cloud-neutral database stack.

Pricing

Free plan

The Free plan costs free and provides Aurora PostgreSQL Serverless instances with up to 4 ACUs and 1 GiB of storage per cluster. That cap makes it suitable for evaluation, small experiments, or a narrowly sized development workload, not a general production database.

Aurora PostgreSQL Serverless Free plan

This plan is free, with no cost for new AWS customers; AWS credits are available for up to 12 months. It includes up to 4 ACUs and 1 GiB of storage per cluster. The short credit window and small storage allowance mean growing workloads will move to paid usage quickly.

Paid plan

The Paid plan has custom pricing. It supports provisioned and serverless configurations, charging for database instances and storage, with optional features billed separately. Choose it when you need capacity beyond the free ceiling or production-scale operation, but budget only after modeling your expected usage.

On-demand configurations

Aurora PostgreSQL and Aurora MySQL On-Demand pricing is custom and usage-based. Provisioned instances are billed per instance-hour; storage and optional features are separate. The price changes with engine, AWS Region, instance or capacity, storage, I/O, and selected configuration, so it is not a predictable flat subscription.

Platforms

Aurora is offered through an API. Operational work is performed with Amazon RDS console and CLI tooling alongside API operations, rather than through a separately listed desktop or mobile application.

Who it's for

Aurora is aimed at enterprise applications, multi-tenant SaaS, and globally distributed applications that need managed relational infrastructure. AWS-centered teams can benefit most from RDS operations, Lambda and S3 integration, GuardDuty monitoring, and familiar PostgreSQL or MySQL behavior. It is a weaker fit for a small project demanding a fixed monthly price, minimal configuration choices, or a self-hosted database.

Pros and cons

• Pro: PostgreSQL and MySQL compatibility can avoid application and tooling rewrites.
• Pro: RDS console, CLI, and API cover provisioning, patching, backup, and recovery in one operating model.
• Pro: Serverless capacity can follow demand instead of requiring a permanently fixed size.
• Pro: AWS cites high single-Region and multi-Region availability targets and supports compliance programs including HIPAA and FedRAMP.
• Con: Paid pricing varies across engine, Region, capacity, storage, I/O, and optional features, making spend harder to forecast.
• Con: The free PostgreSQL Serverless option is limited to 4 ACUs and 1 GiB per cluster.
• Con: AWS Premium Support is required for Aurora-specific troubleshooting and guidance.

Alternatives

MySQL is a better choice when you want a freemium, self-managed engine with a Community Edition and broad API, desktop, and operating-system support.

Azure SQL Database fits teams standardizing on Microsoft Azure and wanting a free offer with stated vCore, storage, backup, and database quotas.

SQLite is preferable for an embedded, free database that requires no separate server and no license fee.

Microsoft SQL Server suits organizations that specifically need Microsoft SQL Server editions and licensing options.

PostgreSQL is the straightforward option when you want the free, open-source engine without managed AWS infrastructure.

Amazon DynamoDB is an alternative for teams wanting a freemium AWS database with a defined free tier and a non-relational model.

Amazon RDS is worth considering when you want AWS-managed databases through RDS but prefer the broader RDS service rather than Aurora specifically.

MariaDB Server is a free, self-hosted choice for non-production applications using its Community Server.

Browse more options in Database Software.

Verdict

Choose Amazon Aurora for AWS-based enterprise, SaaS, or globally distributed systems that need managed PostgreSQL or MySQL compatibility, elastic capacity, and integrated operational controls. Look elsewhere if a small free allowance, self-hosting, or a stable subscription price matters more than AWS's managed scale and ecosystem.