How to store, rotate, and scope database credentials: secrets managers, dynamic credentials, the application path vs the human path, and the mistakes that leak passwords.

Managing Database Passwords and Secrets: Best Practices

A guide to audit logging in MySQL — from the general query log to audit plugins, binlog-based CDC, and Bytebase.

MySQL Audit Logging Guide

Every critical asset has its system of record, except the database. Bytebase is the one. The standard for database development.

The Standard for Database Development

Dynamic data masking is chosen by access path, not product. Five approaches (engine-native, in-database, application, BI layer, and Bytebase) and which caller each one masks.

How to Implement Dynamic Data Masking: Five Approaches by Access Path

Static vs dynamic data masking, when each applies, how they differ on backups, performance, and reversibility, and when to run both.

Static vs Dynamic Data Masking: When to Use Which

The static data masking tools that produce safe non-production data, Delphix, Tonic.ai, and greenmask compared, plus how to roll your own when no tool fits.

Static Data Masking Tools (and How to Roll Your Own)

Compare BigQuery data masking options: native column-level dynamic data masking (built-in masking rules via policy tags and data policies, Dataplex catalog) and Bytebase fleet-wide masking.

BigQuery Dynamic Data Masking

Compare SQL Server data masking options, native Dynamic Data Masking (five mask types, SQL Server 2022 granular UNMASK) and Bytebase fleet-wide masking.

SQL Server Dynamic Data Masking

Compare Oracle data masking options. Native Data Redaction (five function types via DBMS_REDACT, EXEMPT REDACTION POLICY) and Bytebase fleet-wide masking.

Oracle Dynamic Data Masking

You write a one-line UPDATE against production. Here's the lane that keeps it safe: the four phases, the controls, and what each one prevents.

How to Handle Ad-hoc Database Data Changes?

Notes on the MySQL 9.7 LTS release: Hypergraph Optimizer in Community, JSON Duality View DML, Group Replication observability, and Dynamic Data Masking for Enterprise.

Notes on the MySQL 9.7 LTS release

Most DAC implementations stop at the connection. Real DAC operates at the statement and covers three vectors: machine, human, and AI agent.

What is Database Access Control (DAC)?

Practical guide to dynamic data masking: five best practices, a vendor comparison, an end-to-end walkthrough, and the compliance specifics auditors ask about.

Dynamic Data Masking Best Practices

How Bytebase audits the workflow layer: every SQL, schema change, approval, and export tied to a real user identity, with structured exports for any SIEM.

How Bytebase Handles Audit Logging

PostgreSQL 19 features I'm excited about: planner advisor framework, DDL extraction, online REPACK, pg_stat_recovery, parallel autovacuum, sequence sync, and 64-bit MultiXact.

PostgreSQL 19 features I'm excited about

Bytebase is HIPAA-compliant — independent verification that our administrative, physical, and technical safeguards meet the HIPAA Security Rule for handling Protected Health Information.

HIPAA Compliance

PAM tools gate connections; databases also need SQL review, schema change workflow, and statement-level approval. Why most teams use PAM with Bytebase.

Bytebase vs. PAM: Why Database Teams Need More Than Privileged Access Management

What SOC 2 compliance audits actually want from your database audit log: not 'logging enabled' but evidence your auditor will accept. Lessons from going through our own audit.

SOC 2 Audit Log Requirements: Lessons From Our Own Audit

Bytebase vs. Atlas compared across migration approach, CI/CD, access control, and pricing. Updated for Atlas v1.1 and Bytebase 3.16.

Bytebase vs. Atlas: a side-by-side comparison for database schema migration

Audit-surviving database access control: statement-level enforcement across machine, human, and AI agent workloads, with the mistakes that fail SOC 2.

Database Access Control (DAC) Best Practices

SOX Section 404 requires IT general controls over database changes. Learn the ITGC domains, six audit questions teams fail, and how to build SOX-ready controls

Database Change Management for SOX Compliance

TRUNCATE and DELETE both remove rows, but they differ in speed, rollback behavior, and locking. Compare how they work in PostgreSQL, MySQL, and SQL Server.

TRUNCATE vs DELETE in SQL: Differences Across PostgreSQL, MySQL, and SQL Server

Six database design patterns for production systems: normalization, star schema, EAV, polymorphic associations, multi-tenancy, and anti-patterns.

Database Design Patterns Every Developer Should Know

pgvector adds vector storage and similarity search to PostgreSQL. Learn how to install it, query embeddings, build indexes, and decide when it is enough.

pgvector: How to Add Vector Search to PostgreSQL

Upsert inserts or updates a row based on key conflicts. Learn MySQL INSERT ON DUPLICATE KEY UPDATE, PostgreSQL ON CONFLICT, and SQL Server MERGE.

Upsert in SQL: INSERT ON DUPLICATE KEY vs ON CONFLICT Explained

AI agents need more than DDL. The full database lifecycle codified (schema, dependencies, ownership, history) gives LLMs the context to query correctly.

From Schema as Code to Schema as Context

Learn how to find and fix slow MySQL queries using the slow query log, EXPLAIN, index tuning, and query rewrites, with practical examples for each.

How to Fix Slow MySQL Queries: A Practical Guide

A detailed comparison of Convex and Supabase covering architecture, real-time capabilities, data model, pricing, and schema management to help you choose.

Convex vs Supabase: Which Backend Platform Should You Choose?

Blue-green deployments work cleanly for stateless apps. Databases are stateful. Learn what makes database blue-green deployments hard and how to do them safely.

Database Blue-Green Deployment: A Practical Guide

The 10 best data management tools in 2026 — database GUI clients, schema migration tools, data pipelines, and analytics platforms compared with pricing.

Top 10 Data Management Tools in 2026

How to give AI agents governed access to your databases. Identity, authorization, query control, audit, and masking, applied to a new principal type.

How to Govern AI Agent Database Access

Postgres-only SQL editors are designed specifically for Postgres databases, providing a more focused and efficient experience for Postgres users. In this post, we are taking a look at the top Postgres-only SQL editors in 2026.

Enterprise Text-to-SQL: Context, Evaluation, and Governance

Database deployment tools for devops teams in 2026.

Database Deployment Tools for DevOps Teams in 2026

Schema change detection and notification are essential for data pipelines. This article explains why a simple column rename can break your data pipeline and how to prevent it.

Schema Change Detection and Notification: Why a Simple Column Rename Can Break Your Data Pipeline

A comprehensive guide to understanding and analyzing Postgres query plans.

Postgres Query Plan: How to Read and Fix Performance Issues

This article explores the anatomy of Postgres permissions ERROR 42501.

The Anatomy of Postgres Permission ERROR 42501

Postgres Logs Explained: A Practical Guide for Production

Postgres 19 widens MultiXactOffset to 64 bits, eliminating the hidden 4 billion member limit that caused catastrophic outages for high-concurrency workloads.

Postgres 19 Feature Preview: 64-bit MultiXactOffset

A guide to MySQL schema migration best practice.

MySQL Schema Migration Best Practice

Postgres 19 introduces automatic sequence synchronization for logical replication, eliminating manual tracking and making major version upgrades and failover significantly easier.

Postgres 19 Feature Preview: Sequence Synchronization for Logical Replication

A guide to multi-environment deployments in databases.

Database Multi-Environment Deployments - The Challenges and Patterns

A guide to open source sensitive data discovery tools, from NLP libraries like spaCy and Microsoft Presidio to multi-source scanners like Hawk-Eye and full metadata platforms like OpenMetadata.

Top Open Source Sensitive Data Discovery Tools in 2026

Database audit logging has two layers: infrastructure (provider-managed) and workflow (database activity). What each captures, and why compliance requires both.

Database Audit Logging: Two Layers, One Trail

A practical guide to HITRUST database compliance covering access control, audit logging, change management, and data protection.

Database Compliance for HITRUST: Controls, Risks, and Best Practices

Learn why requiring a primary key is important and how the "Require Primary Key" review rule protects your production database.

Require Primary Key: A SQL Review Rule Explained

Learn why enforcing NOT VALID in CHECK constraints is important and how the "Enforce NOT VALID in CHECK" review rule protects your production database.

Enforce NOT VALID in CHECK: A SQL Review Rule Explained

Postgres Audit Logging Guide

Learn why CASCADE operations in SQL can lead to catastrophic data loss and how the "Prohibit CASCADE" review rule protects your production database.

Prohibit CASCADE: A SQL Review Rule Explained

A comprehensive guide on migrating from Supabase to AWS, covering database, auth, storage, functions, realtime, and networking.

How to Migrate from Supabase to AWS

Top open-source Postgres backup solutions for 2026.

What is Enterprise Database Management (EDM)?

What is Postgres Transaction ID (XID) Wraparound and how to monitor and prevent it.

Postgres Transaction ID (XID) Wraparound

How a CI/CD pipeline for database schema migration works end-to-end. What it gates, what it leaves outside, and the tools that fit.

How to Build a CI/CD Pipeline for Database Schema Migration

A practical guide to shipping features with PostgreSQL, covering my day-to-day development workflow, the tools I actually use, and real-world examples

How I Ship Features with Postgres

A practical look at what LGPD (Brazil's General Personal Data Protection Act) means for database operations, how it differs from GDPR, and the controls teams need to actually comply.

Database Compliance for LGPD: Implications and Best Practices

Explain what is Postgres LATERAL JOIN and how to use it.

What is Postgres LATERAL JOIN?

Introduction to MySQL Online DDL and its three algorithms: INSTANT, INPLACE, and COPY

MySQL Online DDL: A Practical Guide

List of open source postgres connection poolers

Open Source Postgres Connection Pooler

A comprehensive guide to understanding the dilemma of singular vs. plural table naming in SQL databases.

SQL Table Naming Dilemma: Singular vs. Plural

PostgreSQL 18 features that change how application developers write and ship code.

What's New in PostgreSQL 18: A Developer's Perspective

Compare Snowflake Dynamic Data Masking with database views and Bytebase fleet-wide masking on edition gate, policy management, and audit trail.

Snowflake Dynamic Data Masking (DDM) and Alternatives

Top open-source Postgres authentication solutions for 2025.

Postgres Case Sensitivity Explained

A comprehensive guide to understanding pg_database_owner in Postgres

What is pg_database_owner in Postgres

Which operation causes a Postgres table rewrite

Which Postgres Operation causes a table rewrite

An engineering perspective to evaluate Postgres row-level-security footguns

Postgres Row-Level Security Footguns

An engineering perspective to evaluate Postgres rollback strategies

Postgres Rollback Explained

Learn how Postgres locks affect schema migrations and which DDL operations conflict with DML to achieve zero-downtime deployments.

Postgres Schema Migration without Downtime

A checklist of gh-ost limitations and potential gotchas

gh-ost Limitations You Need to Know Before Production

5 quick wins for application developers to improve Postgres reliability and make both their own and DBA/infrastructure teams' lives easier.

5 Postgres Production Tips for Application Developers

Learn how to use CREATE INDEX CONCURRENTLY in Postgres to build indexes without blocking writes. Pitfalls, safety checks, and performance tips.

How to Use Postgres CREATE INDEX CONCURRENTLY

An extensive comparison between Supabase and MongoDB on performance, usability, operability, ecosystem and more.

Supabase vs. MongoDB: a Complete Comparison in 2025

When evaluating database management tools, DataGrip and Bytebase represent two different philosophies: individual developer productivity versus team collaboration and governance.

Bytebase vs. DataGrip: a side-by-side comparison for database management

Supabase pricing starts free. We break down real costs for Pro ($25/mo) and Team ($599/mo) plans, explain overages, and compare each service head-to-head with AWS.

Supabase vs AWS: Feature and Pricing Comparison (2026)

Is Supabase free? Compare Supabase pricing vs AWS RDS and Aurora across free tier, Pro, and production plans. Includes Supabase free tier limits, storage costs, and compute pricing for 2026.

Supabase Pricing vs AWS RDS: Is Supabase Free? Full Cost Comparison (2026)

Learn how Bytebase enables organizations to implement comprehensive Database Security Lifecycle Management, unifying security and operations from development to production.

Database Security Lifecycle Management

Areas where MySQL shines and Postgres falls short.

Features I Wish Postgres Had but MySQL Already Has

Areas where PostgreSQL shines and MySQL falls short.

Features I Wish MySQL Had but Postgres Already Has

This guide focuses on HIPAA compliance at the database layer, providing healthcare organizations and database teams with practical guidance for implementing HIPAA Security Rule requirements.

HIPAA Data Security and Retention Requirements

Compare the online index creation difference between Postgres and MySQL

Postgres vs. MySQL: Online Index Creation

SOC 2 Data Security and Retention Requirements for Database Systems and How Bytebase Helps

SOC 2 Data Security and Retention Requirements

Compare the different indexing options between Postgres and MySQL

Postgres vs. MySQL: Indexing Options

Compare the JSON support difference between Postgres and MySQL

Postgres vs. MySQL: JSON Support

While PostgreSQL RLS is a powerful feature, it has inherent design limitations that hinder broader adoption. In this post, we’ll examine these limitations and explore alternatives.

Postgres Row-Level Security (RLS) Limitations and Alternatives

Evaluate several database schema diagram tools, and help you to choose the right one for 2025

Top 4 Free, Open Source Database Schema Diagram Tools to Visualize Database Easier in 2025

An overview of the most popular text-to-SQL AI tools in 2026, including DataGrip, TablePlus, SQL Chat, Vanna.ai, SQLAI.ai, Postgres.new, and DBHub MCP server. Compare features and capabilities to find the best SQL AI assistant for your workflow.

Top 5 Text-to-SQL Query Tools in 2026

Compare the DDL transaction difference between Postgres and MySQL

Postgres vs. MySQL: DDL Transaction Difference

Evaluate several TypeScript ORMs, and help you to choose the right one for 2025

Top TypeScript ORM 2025

Evaluate Prisma and TypeORM, and help you to choose the right TypeScript ORM for 2025

Prisma vs TypeORM: The Better TypeScript ORM in 2025

PostgreSQL 18 features and what they change for running production databases.

What's New in PostgreSQL 18: A DBA's Perspective

Explore alternatives to Amazon RDS, including 

RDS Alternatives in 2025

An extensive comparison between DynamoDB and Cassandra on performance, usability, operability, ecosystem and more.

DynamoDB vs. Cassandra: a Complete Comparison in 2025

An extensive comparison between DynamoDB and MongoDB on performance, usability, operability, ecosystem and more.

RDS vs. DynamoDB: a Complete Comparison in 2025

How gh-ost and pt-online-schema-change compare on architecture, cut-over, foreign keys, and runtime control — for teams choosing a MySQL online schema migration tool.

gh-ost vs pt-online-schema-change

GitHub and Bitbucket are both tools for code collaboration. This article compares the features and pricing of GitHub and Bitbucket.

GitHub vs Bitbucket:a Complete Comparison in 2025

Drizzle ORM vs Prisma comparison: type safety, performance, bundle size, serverless support, migrations, and ecosystem. Find out which TypeScript ORM is right for your project in 2026.

Drizzle ORM vs Prisma: Which TypeScript ORM Should You Use in 2026?

An engineering perspective to evaluate Google AlloyDB and Cloud SQL, and help you to choose the right Google Cloud database for 2025

AlloyDB vs. Cloud SQL: engineering guide to choose the right Google Cloud database for 2025

Understanding DynamoDB Pricing (2025)

A simple comparison of AWS Aurora versus RDS pricing in 2025, helping you understand key differences and choose the right database service for your needs and budget.

AWS Aurora vs. RDS Pricing: A Detailed Comparison 2025


| Update History | Comment          |
| -------------- | ---------------- |
| 2025/04/28     | Initial version. |

Amazon Relational Database Service (RDS) offers a fully managed database solution that simplifies setup, operation, and scaling of relational databases in the cloud. While it's easy and relative cheap to get started, the bill can accumulate pretty fast as this heated Reddit [Postgres RDS is too expensive](https://www.reddit.com/r/devops/comments/1gyjwoj/postgres_rds_is_too_expensive/) post suggests.
Thus Understanding its pricing structure is essential for optimizing costs and making informed decisions for your database deployments. This article breaks down AWS RDS pricing components with specific examples from the US East (N. Virginia) region to help you better understand and manage your database costs.

## Introduction to AWS RDS Pricing

AWS RDS follows a **pay-as-you-go** pricing model with no upfront costs or long-term commitments required. The pricing structure is designed to be flexible, allowing you to pay only for the resources you consume. However, this flexibility can make it **challenging to predict costs** without understanding the various pricing components.

The primary factors that influence your AWS RDS costs include:

1. Database instance type and size
2. Storage type and capacity
3. I/O operations
4. Data transfer
5. Backup storage
6. Deployment options (Single-AZ vs Multi-AZ)
7. Reserved Instances vs On-Demand pricing

Let's explore each of these components in detail with specific pricing examples from the US East (N. Virginia) region.

## AWS RDS Pricing Components

### 1. Database Instance Costs

Database costs depend on the instance type and size you select. AWS offers different families optimized for various workloads:

- **T-class instances**: Burstable performance, ideal for moderate workloads with occasional CPU spikes
- **M-class instances**: General-purpose, balanced for compute, memory, and network needs
- **R-class instances**: Memory-optimized, designed for memory-heavy applications
- **X-class instances**: Extreme memory-optimized, offering the highest memory-to-CPU ratio

**Example pricing (US East - N. Virginia):**

| Instance Type | vCPU | RAM (GiB) | On-Demand Price (Hourly) |
| :------------ | :--: | :-------: | :----------------------: |
| db.t3.micro   |  1   |     1     |         ~$0.017          |
| db.m5.large   |  2   |     8     |         ~$0.171          |
| db.r5.large   |  2   |    16     |         ~$0.226          |

T-class instances (T3, T4g) use a CPU credit model.  
If you exceed the baseline, additional CPU credits are billed at **$0.075 per vCPU-Hour**.

### 2. Storage Costs

AWS RDS offers three types of storage:

- **General Purpose SSD (gp2, gp3)**:  
  Cost-effective for most workloads.

- **Provisioned IOPS SSD (io1, io2)**:  
  Designed for I/O-intensive applications needing low-latency and consistent performance.

- **Magnetic Storage** (legacy):  
  Older option, mainly for backward compatibility — **not recommended** for new deployments.

**Example Pricing (US East - N. Virginia):**

| Storage Type                   | Price per GB-Month |                                      IOPS/Throughput Details                                       |
| :----------------------------- | :----------------: | :------------------------------------------------------------------------------------------------: |
| General Purpose SSD (gp3)      |      ~$0.115       | 3,000 baseline IOPS, 125 MB/s; extra IOPS: ~$0.08/IOPS-month; extra throughput: ~$0.065/MB/s-month |
| Provisioned IOPS SSD (io1/io2) |      ~$0.125       |                    Provision 1,000–256,000 IOPS; extra IOPS: ~$0.10/IOPS-month                     |
| Magnetic Storage (legacy)      |       ~$0.10       |                             Legacy option; not recommended for new use                             |

- **gp3** storage includes a generous baseline; extra IOPS and throughput cost extra.
- **Provisioned IOPS** allows fine-tuning performance, but at a higher price.
- **Magnetic Storage** should only be used for legacy systems.

### 3. Backup Storage Costs

AWS RDS provides automated backups and manual snapshots:

- Backup storage up to **100%** of your total database storage (per region) is **free**.
- Additional backup storage beyond the free limit costs **~$0.095 per GB-month** (US East - N. Virginia).
- Exporting snapshots to Amazon S3 costs **~$0.10 per GB**.

### 4. Data Transfer Costs

Data transfer costs depend on the source and destination:

- **RDS ↔ EC2 (same Availability Zone)**: Free
- **RDS Multi-AZ replication (between Availability Zones)**: Free
- **RDS ↔ EC2 (different Availability Zones, same region)**: ~$0.01 per GB
- **Internet data transfer in**: Free
- **Internet data transfer out**: Tiered pricing, starting at **~$0.09 per GB** for the first 10 TB per month

**Notes:**

- Transfers **within the same AZ** are free, minimizing costs.
- **Cross-AZ** transfers outside of Multi-AZ setups can add up if not carefully designed.
- Internet outbound traffic is the most expensive part — watch your usage if serving external clients.

### 5. Zero-ETL Integration Costs

For RDS for MySQL zero-ETL integration with Amazon Redshift:

- **CDC (Change Data Capture) data transfer**: ~$2.00 per GB (US East - N. Virginia)
- **Snapshot export**: ~$0.10 per GB

**Notes:**

- CDC charges are significantly higher than typical data transfer, reflecting the real-time replication cost.
- Snapshot export pricing aligns with regular RDS snapshot export costs.

## Deployment Options and Their Impact on Pricing

### Single-AZ vs Multi-AZ Deployments

- **Single-AZ**: Provides a database instance in a single Availability Zone
- **Multi-AZ**: Automatically provisions and maintains a synchronous standby replica in a different Availability Zone

Multi-AZ deployments cost twice as much as Single-AZ deployments for the instance hours, as you're essentially running two instances. However, there's no additional charge for data transfer between the primary and standby instances.

### Read Replicas

Read replicas allow you to scale read operations and can be deployed within the same region or cross-region:

- In-region read replicas are charged at the standard instance and storage rates
- Cross-region read replicas incur additional data transfer charges for replicating data across regions

## Cost Optimization Strategies

### 1. Right-sizing Your Instances

- Start with smaller instances and scale up based on workload needs.
- Monitor CPU, memory, and I/O utilization using AWS monitoring tools.
- Use **T-class burstable instances** for development, testing, or low-traffic production environments.

### 2. Leveraging Reserved Instances

Reserved Instances (RIs) offer up to **72% savings** over On-Demand pricing in exchange for a 1- or 3-year commitment:

- **All Upfront**: Full payment upfront for the highest discount.
- **Partial Upfront**: Partial upfront payment, balance paid monthly.
- **No Upfront**: Monthly payments with a smaller discount.

**Example (US East - N. Virginia, db.m5.large):**

| Purchase Option         | Effective Price |  Annual/Total Cost  | Savings |
| :---------------------- | :-------------: | :-----------------: | :-----: |
| On-Demand               |  ~$0.171/hour   |    ~$1,498/year     |    —    |
| 1-year RI (No Upfront)  |  ~$0.109/hour   |     ~$955/year      |  ~36%   |
| 3-year RI (All Upfront) |  ~$0.048/hour   | ~$1,259 for 3 years |  ~72%   |

### 3. Storage Optimization

- Choose **General Purpose SSD (gp3)** for the best price-performance balance.
- Reserve **Provisioned IOPS SSD** for workloads with consistently high I/O needs.
- Archive old or infrequently accessed data to cheaper storage tiers.

### 4. Backup Management

- Set a **backup retention period** that balances recovery needs and storage costs.
- Regularly delete unnecessary manual snapshots.
- Use **AWS Backup** for centralized backup management across services.

### 5. Multi-AZ Deployment Considerations

- Reserve **Multi-AZ deployments** for production workloads requiring high availability.
- Use **Single-AZ deployments** for development and testing to save costs.

### 6. Monitoring and Analyzing Costs

- Use **AWS Cost Explorer** to analyze RDS spending patterns.
- Set up **AWS Budgets** to receive alerts when spending exceeds thresholds.
- Leverage **AWS Trusted Advisor** for cost optimization recommendations.

## Real-World Pricing Examples

### Small Workload (Development/Testing)

**Setup:**

- **Instance:** db.t3.small (Single-AZ)
- **Storage:** 20 GB General Purpose SSD (gp3)
- **Backup Retention:** 7 days

**Monthly Cost Estimate:**

| Item           | Calculation             |       Cost        |
| :------------- | :---------------------- | :---------------: |
| Instance       | $0.034/hour × 730 hours |      ~$24.82      |
| Storage        | 20 GB × $0.115/GB       |      ~$2.30       |
| Backup Storage | Within free tier        |       Free        |
| **Total**      |                         | **~$27.12/month** |

### Medium Workload (Small Production)

**Setup:**

- **Instance:** db.m5.large (Multi-AZ)
- **Storage:** 100 GB General Purpose SSD (gp3)
- **Backup Retention:** 14 days

**Monthly Cost Estimate:**

| Item           | Calculation                 |        Cost        |
| :------------- | :-------------------------- | :----------------: |
| Instance       | $0.171/hour × 2 × 730 hours |      ~$249.66      |
| Storage        | 100 GB × $0.115/GB × 2      |      ~$23.00       |
| Backup Storage | Within free tier            |        Free        |
| **Total**      |                             | **~$272.66/month** |

### Large Workload (Enterprise Production)

**Setup:**

- **Instance:** db.r5.2xlarge (Multi-AZ)
- **Storage:** 1,000 GB Provisioned IOPS SSD (io1) with 5,000 IOPS
- **Backup Retention:** 30 days

**Monthly Cost Estimate:**

| Item             | Calculation                              |         Cost         |
| :--------------- | :--------------------------------------- | :------------------: |
| Instance         | $0.904/hour × 2 × 730 hours              |      ~$1,319.84      |
| Storage          | 1,000 GB × $0.125/GB × 2                 |       ~$250.00       |
| Provisioned IOPS | 5,000 IOPS × $0.10/IOPS-month × 2        |      ~$1,000.00      |
| Backup Storage   | 500 GB × $0.095/GB (first 1,000 GB free) |       ~$47.50        |
| **Total**        |                                          | **~$2,617.34/month** |

## Conclusion

Understanding AWS RDS pricing is crucial for optimizing your cloud database costs. By carefully selecting instance types, storage options, and deployment configurations — and by leveraging cost-saving options like Reserved Instances — you can significantly reduce expenses while maintaining the performance and availability your applications require.

AWS regularly updates its pricing — always verify with the [official AWS pricing pages](https://aws.amazon.com/rds/pricing/).

By applying the cost optimization strategies outlined in this guide and regularly reviewing your database usage patterns, you can maximize the value of your AWS RDS investment while keeping costs under control.


Understanding AWS RDS Pricing (2025)


<HintBlock type="info">

This post is maintained by Bytebase, an open-source database DevSecOps tool that can manage MySQL hosted in any providers. We update the post every year.

</HintBlock>

| Update History | Comment          |
| -------------- | ---------------- |
| 2026/04/01     | Update PlanetScale. |
| 2025/04/28     | Initial version. |

This concise guide compares pricing across seven major MySQL hosting providers: AWS RDS, AWS Aurora, Google Cloud SQL, Azure Database for MySQL, DigitalOcean, PlanetScale, and Aiven. Assuming you're familiar with these services, we'll focus on pricing structures, cost comparisons, and recommendations for different use cases.

## Pricing Comparison Tables

### Basic Monthly Pricing Comparison

| Provider         | Entry-Level                             | Mid-Range                                   | Enterprise-Level                             | Free Tier       |
| ---------------- | --------------------------------------- | ------------------------------------------- | -------------------------------------------- | --------------- |
| AWS RDS MySQL    | $12.41 (db.t4g.micro: 2 vCPU, 1 GiB)    | $99.28 (db.m6g.large: 2 vCPU, 8 GiB)        | $794.24 (db.m6g.4xlarge: 16 vCPU, 64 GiB)    | Yes (12 months) |
| AWS Aurora MySQL | $59.86 (db.t4g.medium: 2 vCPU, 4 GiB)   | $211.70 (db.r6g.large: 2 vCPU, 16 GiB)      | $1,693.60 (db.r6g.4xlarge: 16 vCPU, 128 GiB) | Yes (12 months) |
| Google Cloud SQL | $11.32 (db-f1-micro: 0.2 vCPU, 0.6 GiB) | $122.49 (db-n1-standard-2: 2 vCPU, 7.5 GiB) | $980.03 (db-n1-standard-16: 16 vCPU, 60 GiB) | Yes (90 days)   |
| Azure MySQL      | $14.60 (B1ms: 1 vCPU, 2 GiB)            | $99.28 (GP_Gen5_4: 4 vCPU, 16 GiB)          | $794.24 (GP_Gen5_32: 32 vCPU, 128 GiB)       | Yes (12 months) |
| DigitalOcean     | $15.15 (1 vCPU, 1 GiB)                  | $60.90 (2 vCPU, 4 GiB)                      | $244.35 (6 vCPU, 16 GiB)                     | No              |
| Aiven            | Free (2 vCPU, 1 GiB)                    | $110 (Startup tier: 2-4 vCPU, 4-8 GiB)      | $435 (Premium tier: 4-8 vCPU, 16-32 GiB)     | Yes             |
| PlanetScale      | $39 (1/8 vCPU, 1 GiB) - includes 1 primary and 2 replicas | $179 (1 vCPU, 8 GiB) - includes 1 primary and 2 replicas | $999 (8 vCPU, 32 GiB) - includes 1 primary and 2 replicas | No              |

_Entry-level options provide the most economical starting point, with Google Cloud SQL and AWS RDS offering the lowest prices. DigitalOcean, PlanetScale, and Aiven provide more predictable performance at this tier compared to the burstable instances from hyperscalers. Notably, Aiven offers a completely free tier suitable for development._

_PlanetScale has a locally-attached NVMe offering which has a much better price to performance ratio, but we have chosen not to include it here as the specs aren't directly comparable to their network-attached storage product._

![entry_level_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/entry_level_pricing_chart.webp)

_The chart above illustrates the significant price difference between AWS Aurora and other providers at the entry-level tier. Aiven's free tier stands out as the most cost-effective option for development and testing environments._

### Mid-Range Pricing Comparison

![mid_range_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/mid_range_pricing_chart.webp)

_At the mid-range tier, AWS Aurora is significantly more expensive than other options, while DigitalOcean offers the most economical solution. AWS RDS and Azure provide identical pricing at this tier, making them interchangeable from a pure cost perspective. PlanetScale is among the more expensive tiers at first glance, but their clusters include an HA setup by default with 1 primary and 2 replicas distributed across 3 AZs._

### Enterprise-Level Pricing Comparison

![enterprise_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/enterprise_pricing_chart.webp)

_The enterprise tier shows the most dramatic pricing differences, with AWS Aurora costing more than twice as much as DigitalOcean. The significant price premium for Aurora reflects its advanced features and performance capabilities for mission-critical workloads._

### Storage Pricing

| Provider         | Storage Type               | Price per GB-month  | Performance                 |
| ---------------- | -------------------------- | ------------------- | --------------------------- |
| AWS RDS MySQL    | General Purpose SSD (gp3)  | $0.115              | 3,000 IOPS baseline         |
| AWS RDS MySQL    | Provisioned IOPS SSD (io1) | $0.125 + $0.10/IOPS | Up to 256,000 IOPS          |
| AWS Aurora MySQL | Aurora Storage             | $0.10               | Auto-scaling, distributed   |
| Google Cloud SQL | SSD                        | $0.17               | Scales with instance        |
| Google Cloud SQL | HDD                        | $0.09               | Lower performance           |
| Azure MySQL      | General Purpose            | $0.115              | Included IOPS based on size |
| Azure MySQL      | Business Critical          | $0.25               | Higher performance          |
| DigitalOcean     | SSD                        | Included in plan    | Varies by plan              |
| Aiven            | SSD                        | Included in plan    | Varies by plan              |
| PlanetScale      | General Purpose             | $0.50               | Scales with instance        |
| PlanetScale      | NVMe                        | Included            | Extreme performance; No IOPS limits |

_Storage pricing varies significantly between unbundled (AWS, Google, Azure) and bundled (DigitalOcean, Aiven) approaches. For high-performance workloads, AWS's provisioned IOPS offers the most control but at premium pricing. Google Cloud SQL has the highest SSD pricing, while Aurora offers good value with its distributed storage system._

![storage_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/storage_pricing_chart.webp)

_The chart above shows that Azure Business Critical storage is significantly more expensive than other options at $0.25/GB-month, while Google Cloud SQL HDD offers the lowest unbundled price at $0.09/GB-month. AWS Aurora provides a good balance of performance and cost at $0.10/GB-month. Note that DigitalOcean and Aiven include storage in their base pricing, making them potentially more economical for storage-intensive workloads._

### Network Transfer Pricing

| Provider         | Inbound | Outbound (Same Region) | Outbound (Different Region) | Outbound to Internet |
| ---------------- | ------- | ---------------------- | --------------------------- | -------------------- |
| AWS RDS/Aurora   | Free    | Free                   | $0.01-$0.02/GB              | $0.09-$0.15/GB       |
| Google Cloud SQL | Free    | Free                   | $0.01-$0.08/GB              | $0.08-$0.15/GB       |
| Azure MySQL      | Free    | Free                   | $0.01-$0.05/GB              | $0.05-$0.12/GB       |
| DigitalOcean     | Free    | Free                   | N/A                         | $0.01/GB (after 1TB) |
| Aiven            | Free    | Free                   | Included                    | Included             |
| PlanetScale      | Free    | Free                   | Included                    | Included             |

_Network transfer costs become significant for applications with heavy data movement, especially across regions or to the internet. DigitalOcean offers the most economical outbound internet transfer, while Aiven includes all network transfer in their base pricing, eliminating this variable cost component._

![network_transfer_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/network_transfer_pricing_chart.webp)

_The chart above highlights the dramatic difference in outbound internet transfer costs between providers. AWS RDS/Aurora and Google Cloud SQL charge up to $0.15/GB, while DigitalOcean charges only $0.01/GB after the first 1TB. Aiven stands out by including all network transfer in their base pricing, making it the most predictable option for applications with heavy data transfer requirements._

### High Availability and Backup Pricing

| Provider         | High Availability Setup            | Backup Storage                       | Point-in-Time Recovery |
| ---------------- | ---------------------------------- | ------------------------------------ | ---------------------- |
| AWS RDS MySQL    | 2x instance cost                   | Free up to 100% of DB storage        | Included               |
| AWS Aurora MySQL | Built-in (minimal additional cost) | Free up to 100% of DB storage        | Included               |
| Google Cloud SQL | 2x instance cost                   | 7 backups free, then $0.08/GB-month  | Included               |
| Azure MySQL      | 1.5-2x instance cost               | Included for 7-35 days based on tier | Included               |
| DigitalOcean     | Additional cost for standby nodes  | Included in plan                     | Included               |
| Aiven            | Included in Business/Premium tiers | Included in plan                     | Included               |
| PlanetScale      | Included (1 primary + 2 replicas)  | 2x daily backups included            | Not available           |

_High availability configurations significantly impact total cost, effectively doubling the price for most providers except Aurora (which has built-in HA) and Aiven (which includes it in higher tiers). PlanetScale MySQL/Vitess clusters come with HA and 3 nodes by default. Backup costs are generally included with limitations, with Google Cloud SQL being the only provider to charge after a certain threshold._

![ha_backup_pricing_chart](/content/blog/mysql-hosting-options-pricing-comparison/ha_backup_pricing_chart.webp)

_The chart above illustrates two critical cost factors: high availability multipliers and backup storage costs. AWS Aurora and Aiven offer the most economical high availability options, with Aurora at just 1.1x the base price and Aiven including it in their base pricing. For backup storage, Google Cloud SQL is the only provider charging extra ($0.08/GB-month) after 7 free backups, while all other providers include backups in their base pricing with various retention periods._

## Cost Optimization Strategies

### Long-Term Commitments

| Provider     | Commitment Options          | Maximum Discount | Flexibility                    |
| ------------ | --------------------------- | ---------------- | ------------------------------ |
| AWS          | 1-3 year Reserved Instances | 62%              | Limited to specific instance   |
| Google Cloud | 1-3 year Committed Use      | 57%              | Flexible across instance types |
| Azure        | 1-3 year Reserved Capacity  | 55%              | Limited to specific instance   |
| DigitalOcean | None                        | N/A              | Pay-as-you-go only             |
| Aiven        | Annual commitments          | Custom pricing   | Limited flexibility            |
| PlanetScale  | Annual commitments          | Discounts for consumption and AWS/GCP Marketplace | Custom                         |

_For predictable, stable workloads, commitment-based discounts from major cloud providers offer substantial savings. AWS provides the highest potential discount but with less flexibility than Google's commitment model._

### Serverless and Variable Workloads

| Provider     | Serverless Option                | Minimum Cost       | Scaling Granularity |
| ------------ | -------------------------------- | ------------------ | ------------------- |
| AWS Aurora   | Aurora Serverless                | Pay per ACU-second | 0.5 ACU increments  |
| Azure        | Flexible Server (preview)        | Hourly billing     | Preset tiers        |
| Google Cloud | None (only auto storage scaling) | Full instance cost | N/A                 |
| DigitalOcean | None                             | Full instance cost | N/A                 |
| Aiven        | None                             | Full instance cost | N/A                 |
| PlanetScale  | None                             | Full instance cost | N/A                 |

_For variable or unpredictable workloads, AWS Aurora Serverless offers the most mature consumption-based model, potentially reducing costs during periods of low activity. Azure is developing similar capabilities but with less granularity._

## Regional Availability and Data Residency

| Provider         | Number of Regions                 | Data Residency Controls | Regional Pricing Variations |
| ---------------- | --------------------------------- | ----------------------- | --------------------------- |
| AWS RDS/Aurora   | 27+ regions                       | Strong                  | 10-30% variation            |
| Google Cloud SQL | 24+ regions                       | Strong                  | 5-20% variation             |
| Azure MySQL      | 30+ regions                       | Strong                  | 5-25% variation             |
| DigitalOcean     | 8 regions                         | Limited                 | Uniform pricing             |
| Aiven            | 90+ regions (via cloud providers) | Strong                  | Uniform pricing             |
| PlanetScale      | 18 regions (via cloud providers)  | Strong                  | 5-20% variation             |

_Regional availability directly impacts data sovereignty compliance. The hyperscalers offer the most comprehensive regional coverage, while Aiven leverages underlying cloud providers to offer the widest deployment options with consistent pricing across regions._

## Conclusion

The MySQL hosting market in 2025 offers diverse pricing models catering to different priorities:

1. **AWS and Google Cloud** provide granular control with complex pricing structures.
2. **Azure** balances feature richness with moderate pricing complexity.
3. **DigitalOcean** emphasizes simplicity and predictability at the expense of some flexibility.
4. **Aiven** offers multi-cloud flexibility with straightforward pricing but at a premium for higher tiers.
5. **PlanetScale** starts at a higher price, but includes high availability by default and offers better price to performance options with locally-attached NVMe.

## References

**Official Pricing Pages**

1. [AWS RDS MySQL Pricing](https://aws.amazon.com/rds/mysql/pricing/)
1. [AWS Aurora Pricing](https://aws.amazon.com/rds/aurora/pricing/)
1. [Google Cloud SQL Pricing](https://cloud.google.com/sql/pricing)
1. [Azure Database for MySQL Pricing](https://azure.microsoft.com/en-us/pricing/details/mysql/)
1. [DigitalOcean Managed Databases Pricing](https://www.digitalocean.com/pricing/managed-databases)
1. [Aiven MySQL Pricing](https://aiven.io/pricing)
1. [PlanetScale Pricing](https://planetscale.com/pricing)

**Cost Optimization Guides**

1. [AWS RDS Cost Optimization](https://aws.amazon.com/blogs/database/best-practices-for-amazon-rds-cost-optimization/)
1. [Google Cloud SQL Cost Optimization](https://cloud.google.com/blog/products/databases/optimize-cloud-sql-costs)
1. [Azure MySQL Cost Optimization](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-cost-optimization)
1. [Multi-Cloud Database Strategy Guide](https://aiven.io/blog/multi-cloud-strategy-for-databases)


Compare the price of the mainstream managed MySQL hosting providers

The
Bytebase Blog

Explore the standard for database development

Solutions & Platform

Comparisons

Legal

Resources

Company