SQL Server BYOM on RDS: The Position Comes First
On 2 June 2026, AWS launched Bring Your Own Media for RDS for SQL Server. Software Assurance customers can reuse existing Enterprise or Standard licenses on the managed service instead of paying License Included a second time. You upload RTM media to S3, create a BYOM engine version, and launch with license-model set to bring-your-own-media. AWS License Manager can track usage. Microsoft still has to verify the licenses.
That’s the problem.
This is not a Microsoft-AWS handshake. It is an AWS path that still runs through a Microsoft form. SQL Server BYOM on Amazon RDS does not skip the license position. It makes the position the thing you have to produce before you move the database.
What AWS launched, and what Microsoft still has to confirm
AWS’s own What’s New post is the event. Customers who run SQL Server on-premises, on another cloud, or as self-managed SQL Server on EC2 can adopt RDS and reuse licenses they already hold, including Software Assurance, through Microsoft’s License Mobility program. They no longer have to buy additional SQL Server licenses, or wait for an agreement to expire, to get onto the managed service. BYOM integrates with AWS License Manager.
The User Guide is more precise than the announcement. Two models sit on RDS: License Included, where AWS provides the SQL Server license inside the hourly rate, and BYOM, where you provide the license through License Mobility and AWS does not charge a SQL Server license fee. You pay compute, storage, I/O, data transfer, and Windows OS. You must have SQL Server licenses with active Software Assurance. You download the Release to Manufacturing ISO from Microsoft, upload it to S3, and RDS installs from that media and applies cumulative updates. Supported editions for production BYOM are Enterprise and Standard, on SQL Server 2019, 2022, and 2025.
License compliance is yours. AWS License Manager reports vCPU usage. It does not confirm eligibility. Microsoft’s License Mobility page is the other half of the file. Eligible application-server licenses with active Software Assurance can be deployed in an Authorized Mobility Partner’s datacenter. Within ten days of deployment you complete the License Verification Form and send it to your Microsoft representative or reseller so Microsoft can confirm the licenses to you and to the partner. AWS is the host. Microsoft is the verifier.
Do not treat the AWS headline as a Microsoft policy change. Treat it as an AWS feature that still asks Microsoft to verify you.
License Mobility covered EC2. RDS was the second invoice.
License Mobility is how Software Assurance customers have been allowed to bring SQL Server to AWS on EC2. RDS was the exception. Managed meant License Included. License Included meant you paid again for a license you already held.
If you still run SQL Server on EC2 under License Mobility and on RDS under License Included, you have two commercial models for one product. One consumes the entitlement you already paid for. The other invoices you again.
BYOM does not invent a new Microsoft right. AWS built a way to consume media and licenses you already have, on the managed service, if you can get through the verification form. That is why the form is the story, not the console click. Eligibility is Microsoft’s. The upload is AWS’s. The license position is yours.
This is not a criticism of the teams who bought License Included because that was the only RDS path. Traditional SAM tools collect comprehensively and answer slowly. They were built to prove what is deployed, not to recast the same Enterprise or Standard licenses as EC2 mobility, RDS License Included, or RDS BYOM before a placement meeting. The gap is interpretation work. An analysis that arrives after the database is already on RDS is a document. One that arrives during the meeting is a decision input.
If that feels familiar, the problem is not your team’s maturity. A managed-service conversation is being answered with a “we have SQL Server licenses” slide.
Double-pay versus BYOM is a position, not a checkbox
Picture the room. Your CIO wants the next SQL Server estate on RDS because nobody wants to patch the box. FinOps wants to stop paying License Included on licenses you already own. Procurement wants to know whether Software Assurance is doing any work on this move. If SAM takes three weeks to say which Enterprise and Standard licenses sit under Software Assurance, which already sit on EC2, and which RDS instances are still License Included, the move happens without a position. Compute gets decided. License gets added later.
Do not let AWS frame this as “bring your media and stop paying twice.” Your sentence is narrower: which SQL Server licenses do we actually hold, which are under Software Assurance, which already sit on EC2 under License Mobility, and which RDS instances are still License Included.
“We have BYOM now” is not a number. A License Manager graph is not a position until it is reconciled to the entitlements Microsoft already verified.
The double-pay is real if License Included is still running on top of licenses you could assign through the form. That is a cost optimization question, not a console setting. It is not automatic. Microsoft’s verification form exists to confirm eligibility. Your file should, before you open the console.
A few constraints sit in the AWS docs and belong in the pack. In-place major version upgrades are not supported on BYOM. Engine versions are account- and Region-specific. SSAS and SSRS are out. Developer Edition is a non-production BYOM path, not a production shortcut. None of those is a reason to stay on License Included. All of them are reasons the placement has to be named, not assumed.
What to verify before SQL Server BYOM on Amazon RDS
Do this in the next thirty days, as a decision pack rather than a project. The event is the next RDS placement, not the AWS blog.
| What you produce | Why it changes the next move |
|---|---|
| SQL Server Enterprise and Standard licenses under Software Assurance, this week | BYOM is documented for those editions on the License Mobility path. A stale count is a document, not a position. |
| Which of those licenses already sit on EC2 under License Mobility | You need to know where the entitlement already lives before you point it at RDS. |
| Which RDS for SQL Server instances are still License Included | That is the second invoice. If you cannot name it, you cannot stop paying it. |
| License Mobility Verification Form status with Microsoft | Eligibility is Microsoft’s. AWS will not confirm it for you. |
| RTM media, version, and AWS License Manager usage against that file | Console plus License Manager is the AWS side. It is not a substitute for the Microsoft file. |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have a SQL Server BYOM position. You have a library.
Then say, in one page, which RDS instances you will leave on License Included, which you will put through BYOM, and which SQL Server workloads stay on EC2. Three paths. One product. A default is not a decision.
The decision layer, not another inventory
You already have discovery data, EA files, and an AWS bill. The gap is not another inventory. The gap is turning that estate into a decision: which SQL Server licenses are eligible, which are already assigned, which RDS instances are still License Included, and what should happen before the next move. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. A current Microsoft position from the SQL Server entitlements you already have is the point.
If you are heading into an RDS placement or a Software Assurance conversation and your current tools still need three weeks to turn “we have SQL licenses” into a License Included versus BYOM number, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “BYOL is now allowed on RDS.” AWS built the path. Microsoft verifies the licenses. The right question is: which Enterprise and Standard licenses are under Software Assurance, which already sit on EC2, which RDS instances are still License Included, and what does the License Mobility Verification Form actually confirm for this estate. That is a data question, not a sales question.
You still have to place the next instance. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
