aws_ lightsail_ database cost estimation
A simplified managed database (MySQL/PostgreSQL) sold as a flat monthly bundle. The micro bundle is ~$15/month, all-in; HA bundles cost more.
An aws_
The appeal, like Lightsail instances, is predictability: unlike RDS, where instance, storage, IOPS, backups, and data transfer bill separately and vary, Lightsail databases are one fixed number. That suits small apps, prototypes, and simple workloads where predictable cost beats RDS's tuning knobs.
The trade-off is the ceiling: at scale, or when you need RDS's instance variety, read replicas, Reserved Instances, Multi-AZ tuning, or Aurora, RDS becomes more capable and cost-effective. Lightsail databases are the right tool for the small end, not the large.
c3x prices the database from bundle_
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "aws_lightsail_database" "app" {
relational_database_name = "app-db"
availability_zone = "us-east-1a"
master_database_name = "appdb"
master_username = "dbadmin"
master_password = var.db_password
blueprint_id = "mysql_8_0"
bundle_id = "micro_2_0"
}Pricing dimensions
What you actually pay for when you provision aws_.
| Dimension | Unit | What's being charged |
|---|---|---|
| Lightsail database | per month (bundle) | Flat monthly bundle covering compute, storage, and a transfer allowance. HA (_ha) bundles roughly double the price with a standby. $14.72/month for micro_2_0 (1 GB RAM) |
Sample C3X output
A micro_2_0 managed database (standard, single-AZ):
aws_lightsail_database.app
└─ Lightsail database (micro_2_0) 1 month $14.72
Monthly $14.72Optimization tips
Common ways to reduce aws_ cost without changing the workload.
Right-size the bundle
Difference between bundlesBundles ladder from micro to large. Start with the smallest that fits your data and connection needs; Lightsail makes upgrading straightforward, so don't over-provision the bundle upfront.
Use HA bundles only where you need a standby
~50% vs the HA bundleThe _ha bundles roughly double the price by adding a standby for failover. Use them for production that can't tolerate downtime; standard single-AZ bundles are fine for dev, prototypes, and non-critical apps.
Use Lightsail for small workloads, RDS for the rest
Workload-dependentLightsail's flat bundle wins for small, predictable databases. Once you need read replicas, instance variety, Reserved Instances, or Aurora, RDS becomes more capable and cost-effective at scale.
Delete unused databases
Full bundle cost per reclaimed databaseA Lightsail database bills its bundle whether or not it's queried. Reclaim dev, demo, and abandoned databases, there's no commitment to strand.
FAQ
How is a Lightsail managed database billed?
A flat monthly bundle that packages compute, storage, and a data-transfer allowance into one price, the micro_
Lightsail database or RDS, which is cheaper?
Lightsail for small, predictable databases, prototypes, simple apps, where the flat bundle is simplest. RDS becomes more cost-effective and capable at scale, when you need read replicas, instance variety, Reserved Instances, or Aurora.
How does c3x estimate the cost?
From bundle_
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_.