Non-Production RDS SQL Server Using Standard or Enterprise Edition Instead of Developer Edition

Balazs Engedi

CER:

CER-0322

Service Category

Databases

Cloud Provider

AWS

Service Name

Amazon RDS

Inefficiency Type

Inefficient Configuration

Explanation

Amazon RDS for SQL Server uses a License Included pricing model where the hourly instance rate bundles Microsoft SQL Server licensing fees on a per-vCPU basis. When non-production workloads — such as development, testing, staging, QA, or UAT environments — run on Standard or Enterprise editions, they incur these per-vCPU licensing charges even though the workloads do not require a production-grade license. SQL Server licensing is a major component of the total RDS instance cost, and this overhead scales directly with the number of virtual CPUs provisioned.

Since December 2025, Amazon RDS for SQL Server supports Developer Edition, which includes all Enterprise Edition features but is licensed by Microsoft exclusively for non-production use. Developer Edition instances incur only AWS infrastructure costs with no SQL Server licensing fees. Prior to this capability, customers had no option to use Developer Edition on standard RDS and were forced to pay for Standard or Enterprise licenses even in non-production environments. Organizations with multiple non-production environments running Standard or Enterprise editions now have a significant opportunity to eliminate unnecessary licensing costs by migrating to Developer Edition.

Developer Edition on RDS is provisioned through a Custom Engine Version (CEV) approach, which requires a one-time setup per SQL Server version. While this adds initial complexity compared to standard RDS instance creation, the ongoing licensing savings can be substantial — particularly for organizations running several non-production SQL Server instances across development, testing, and staging environments.

Relevant Billing Model

Amazon RDS for SQL Server billing is based on a License Included model with the following cost dimensions:

Per-instance hourly charges — bundling AWS infrastructure costs and Microsoft SQL Server licensing fees into a single rate, billed per-second with a 10-minute minimum following billable status changes
SQL Server licensing component — charged on a per-vCPU basis, meaning licensing costs scale directly with the number of virtual CPUs provisioned on the instance
Storage, I/O, data transfer, and backup storage — billed separately from compute and licensing

Developer Edition instances are charged only for AWS infrastructure — there are no SQL Server licensing fees. Standard and Enterprise editions include per-vCPU licensing charges in the hourly rate. Because the licensing component represents a significant portion of the total RDS SQL Server instance cost, eliminating it for non-production workloads can yield meaningful savings. For current rates by edition and instance class, see the Amazon RDS for SQL Server Pricing page.

Detection

Identify all RDS for SQL Server instances running Standard or Enterprise editions across the organization's accounts and regions
Assess which of these instances serve non-production purposes such as development, testing, staging, QA, or UAT by reviewing environment tags, naming conventions, or consulting application teams
Evaluate the vCPU count provisioned on each non-production instance to understand the scale of per-vCPU licensing charges being incurred
Review whether any non-production instances rely on features or configurations not supported by Developer Edition on RDS, such as Multi-AZ deployments or read replicas
Confirm the instance class families in use, as Developer Edition on RDS currently supports a limited set of instance class generations
Examine whether existing non-production instances are covered by Reserved Instance commitments that may affect the timing or approach of migration

Remediation

Set up the Custom Engine Version (CEV) for SQL Server Developer Edition by obtaining the SQL Server installation media from Microsoft, uploading it to an S3 bucket, and creating the CEV — this is a one-time setup per SQL Server version and region
Migrate databases from existing Standard or Enterprise edition instances to new Developer Edition instances using native backup-and-restore, as edition downgrades are not supported via snapshot restore — create a new Developer Edition instance, perform native backups of databases on the source instance, and restore them to the target
Update application connection strings to point to the new Developer Edition instance endpoint, or rename the original instance and assign its identifier to the new instance to preserve the endpoint
Validate that all databases, logins, security configurations, and application functionality work correctly on the Developer Edition instance before decommissioning the original
Delete the original Standard or Enterprise edition instance after successful validation to stop incurring licensing charges
Establish a governance process to ensure new non-production RDS SQL Server instances are provisioned with Developer Edition by default, preventing recurrence of unnecessary licensing costs

Relevant Documentation

Submit Feedback