EC2 SQL Server Windows to Linux Migration

Running SQL Server on AWS#

MS SQL, short for Microsoft SQL Server, is widely used, and a worthy contender to MySQL, PostgreSQL, and Oracle. You may think, as I did, that MS SQL would be a Windows only product. I had no idea that MS SQL could run on Linux. Apparently, this has been the case since mid 2017! Clearly Microsoft has evolved from the Steve Ballmer days. 

You can run MS-SQL on AWS infrastructure in two main ways, on a self-managed EC2 instance or on RDS for Microsoft SQL Server. Since RDS is a managed service, you have no exposure to the underlying operating system. In this blog post we are going to focus on the first case – MS SQL on EC2 instances. Many of these instances are running Microsoft Windows. And, while the is well supported on AWS, it comes with an extra cost that you may not need to pay.

This Finder/Fixer will help you identify EC2 instances running Windows and MS-SQL, and propose and calculate potential savings for moving these instances to Linux. I’ll state right up front, this is a Finder only. Since these are self-managed EC2 instances, we cannot automate moving the SQL instances. But we can calculate the potential savings, which will let you know if the effort of making the change is worthwhile. Finding is read-only: CloudFix uses your cost and usage data to identify the instances and estimate the savings, and each one appears in your Recommendations. You then decide whether to migrate, and make the change yourself.

CloudFix Finder Demo#

You will find this in the Medium category, under “SQL Server Migration Windows to Linux.”

A Look at the Numbers#

Why the Extra Cost?#

• Premium: Windows instances cost 30-100% more than Linux equivalents
• Cost Driver: Premium primarily reflects Windows Server licensing fees
• Scaling Impact: Absolute price difference increases with instance size, though percentage difference typically decreases (100%+ for small instances vs. 30-50% for larger ones) with instance size
• Instance Type Variations:
  • General Purpose: 20-40% Windows premium
  • Compute Optimized: 50-100% Windows premium
  • Memory Optimized: 30-50% Windows premium
• Consistency: Premium percentages remain largely consistent across AWS regions

A Pricing Experiment#

Considering a mid-sized production cluster of 5 instances, lets do a pricing experiment.

But wait, there’s more#

If there was only one database instance, the savings would still be substantial. Most organizations that we work with have many databases scattered across the accounts within the AWS organization. The calculation above is for a single cluster. If you are running a centralized FinOps team, it will be worth building the institutional knowledge for how to transition these databases from Windows to Linux. 

For a centralized FinOps team, the first step is to quantify the number of SQL Server Windows EC2 instances that are running within the organization: visit the CloudFix console and count the number of recommendations for this category. Survey the database owners and understand why they are running SQL Server, and if there are Windows-specific features that they need. Once you know which databases can be migrated, then you can build a migration strategy. If possible, implement a chargeback strategy, with internal pricing that incentivizes RDS for SQL Server rather than self-managed EC2 instances. Develop org-specific guidance for how to do this migration.

Migration Process#

It would be great to be able to make this one a one-click change. However, in order to switch from Windows MS-SQL there are a few things to check. Here is a non-exhaustive list of things to check:

• Unsupported or edition-specific SQL Server features in your databases
• Database file paths, which change from Windows-style to Linux-style locations
• Features that aren’t supported on Linux, such as FileStream
• Linked servers that depend on Windows-only providers
• COM objects or other Windows-dependent integrations that need Linux-compatible alternatives
• Authentication: SQL Server authentication, or Active Directory integration if you rely on Windows Authentication
• SQL Server Agent jobs that call Windows-dependent scripts
• Full-Text Search compatibility
• Database compatibility level (Linux support starts with SQL Server 2017)

Checking all of these things will involve a non-trivial amount of engineering effort. You need to figure out if this engineering effort is worth it. That is where we come in. By helping you understand the potential cost savings, you can decide if the switch is worth it.

Wrapping Up#

Databases are one of the most expensive parts of your cloud spend. Running MSSQL on Windows on EC2 is one of the most expensive ways to run a database on AWS. You are paying more for licensing,  your administrative costs are higher, your data storage costs more, and you lose all of the flexibility of the managed services. Unless you absolutely need this particular software stack, you should consider switching.

---

Ready to start saving on AWS? See how much you could cut from your cloud bill with a free cost optimization assessment, or explore CloudFix automated Finder/Fixers that eliminate waste across 30+ AWS services.

Related Articles#

• AWS Cost Optimization: The Complete Guide to Lowering Your Cloud Bill (2026)
• AWS Cost Optimization Tools: The Complete Comparison Guide (2026)
• RightSpend vs ProsperOps (Flexera): The Independent EC2 Discount Alternative
• Find Idle AWS Transfer Family Endpoints
• CloudFix Finder: SageMaker Rightsize Instances (Manual Fix)