Windows and SQL Server licensing on AWS
Understand license-included versus bring-your-own-licence for Windows Server and SQL Server on AWS, when Dedicated Hosts and License Mobility apply, how to model the cost of staying on Windows against moving to Linux or PostgreSQL, and how to track licences with AWS License Manager. Informational, not legal advice.
Assumes: .NET 10 LTS · AWS CLI v2 · AWS License Manager · Amazon EC2 Dedicated Hosts · AWS CDK v2 (C#) · Terraform AWS provider v6 · Region us-east-1. Verified against official sources on 2026-11-18.
Learning objectives
By the end of this lesson you can:
- Explain the three licensing routes for Microsoft software on AWS: license-included, bring your own licence (BYOL) with License Mobility, and BYOL on dedicated infrastructure.
- Describe why SQL Server licensing is counted differently on shared tenancy (vCPUs) and on Dedicated Hosts (physical cores), and what that does to cost.
- Build a transparent cost model that compares staying on Windows and SQL Server with moving to Linux and PostgreSQL, including the one-off conversion cost.
- Verify at the AWS billing layer whether an instance is running license-included or BYOL.
- Use AWS License Manager to track licence use, and design a Dedicated Host with CDK (C#) or Terraform, without deploying it.
- List the questions that must go to Microsoft licensing specialists and your legal team.
Not legal or licensing advice
Microsoft licensing terms are contractual and change over time. This lesson explains how the AWS side works and how to model cost. Your organisation's eligibility (Software Assurance status, agreement type, purchase dates, version) is a question for your Microsoft licensing adviser and your legal and procurement teams. Every eligibility rule below is marked ⚠ VERIFY: confirm it against current Microsoft product terms and AWS documentation before relying on it.
Prerequisites
- Migration assessment and portfolio discovery — the inventory that tells you how many instances and which editions
- Rehosting with AWS Application Migration Service — the launch template carries a licence type
- RDS for SQL Server and PostgreSQL
- Pricing models — On-Demand, Savings Plans, Reserved capacity
- Tools: .NET 10 SDK or Docker. No AWS account is needed for the model.
Why this matters in banking
Harbourline's finance director asks one question: "will AWS be cheaper than the data centre?" For a Windows and SQL Server estate, the honest answer depends more on licensing than on compute. On AWS, a Windows instance is priced with or without a Windows licence, and a SQL Server instance with or without SQL Server. Those licence components can be larger than the hardware. A migration business case that ignores them produces a bill nobody forecast. A migration that misreads licence eligibility creates a compliance exposure that surfaces in an audit, which for a regulated bank is a reportable problem.
Licensing is also the strongest financial argument for the modernisation lessons in this module: every Windows server turned into a Linux container and every SQL Server turned into PostgreSQL removes a recurring licence line.
The idea in plain language
When you run Microsoft software in a cloud you need a licence for it. There are three ways to get one:
- License-included (LI). AWS provides the licence and you pay for it in the hourly price. Nothing to track; no commitment; the highest unit price.
- BYOL with License Mobility. You already own licences with active Software Assurance (SA). Microsoft's License Mobility rights let you use eligible server products (SQL Server is the main one) on shared infrastructure. You pay AWS only for the instance and keep paying Microsoft for the licence and SA.
- BYOL on dedicated infrastructure. For products without mobility rights (notably Windows Server), you may bring eligible licences if you run them on hardware dedicated to you: EC2 Dedicated Hosts (or dedicated instances). Dedicated Hosts expose physical sockets and cores, which also changes how SQL Server is counted.
Analogy: Renting a car. License-included is the rental company's price with insurance built in. BYOL with mobility is using your own insurance policy on any rental car. BYOL on dedicated hardware is leasing a car that only you drive and using your own policy, which the insurer only accepts under specific conditions.
What problem the AWS options solve
| Option | What you pay AWS | What you manage | Honest limits (⚠ VERIFY each against current terms) |
|---|---|---|---|
| License-included, shared tenancy | Instance plus licence in the hourly rate | Nothing | Highest unit price. Very flexible: short-term and spiky workloads fit well |
| SQL Server BYOL + License Mobility, shared tenancy | Instance with Windows included; SQL Server not charged | SA, licence counting by vCPU, evidence of mobility verification | Requires active SA on eligible licences, and the process Microsoft defines |
| Windows Server BYOL on Dedicated Hosts | Dedicated Host (per host per hour) | Licence eligibility, host capacity, placement, licence tracking | AWS guidance indicates eligibility is limited to licences purchased before October 1, 2019 (or added as a true-up under an enrolment effective before that date), and that Windows Server 2019 is the latest BYOL version, so Windows Server 2022 on Dedicated Hosts must be license-included |
| SQL Server BYOL on Dedicated Hosts | Dedicated Host | Licence per physical core instead of per vCPU | Can reduce licence counts for dense, steady workloads; wasteful for small or spiky ones |
| Managed: RDS for SQL Server | Instance plus licence (license-included) | Almost nothing | Licence-included only for most configurations; check current options for BYOL-like models ⚠ VERIFY |
| Convert away | Linux and PostgreSQL pricing | The conversion project | One-off cost and risk; removes the recurring licence line |
The AWS prescriptive guidance that this lesson draws on notes that a Windows licence is roughly half of a Windows instance's price, and that licensing SQL Server at physical-core level on a Dedicated Host can reduce the number of core licences compared with counting vCPUs in shared tenancy. Both effects depend on workload density and your agreement, so model them rather than assume them.
Microsoft / Azure comparison
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Azure Hybrid Benefit (Windows and SQL Server with SA) | License Mobility (SQL Server, shared tenancy) and Dedicated Host BYOL (Windows) | Azure Hybrid Benefit is a toggle on the VM. On AWS, Windows BYOL needs dedicated hardware and more conditions. Do not assume parity |
| Azure Reserved Instances plus Hybrid Benefit | Savings Plans or Reserved capacity, plus licence type | AWS commitment discounts apply to the instance; the licence component handling differs by option ⚠ VERIFY |
| Azure dev/test pricing | SQL Server Developer edition (free for non-production per Microsoft terms ⚠ VERIFY) on EC2, plus Linux | Non-production licence-included Windows costs add up; consider smaller or Linux non-prod |
| Azure SQL Managed Instance pricing | RDS for SQL Server pricing | Edition and Multi-AZ double instance cost; check which licence modes are offered |
| Azure Cost Management licence reporting | AWS License Manager, Cost Explorer filters by platform | License Manager tracks usage against rules you define; Cost Explorer shows spend |
| Software Assurance as a shared asset | Same SA contract, different cloud rules | SA benefits that apply in Azure do not automatically apply on AWS |
Architecture
Governance view. Licensing is a control as well as a cost. Keep a register of which workload runs under which licence, who approved it, which contract and purchase it relies on, and when it is reviewed. License Manager enforces counting rules and produces reports across accounts through AWS Organizations; the register is evidence for an audit.
Step-by-step implementation
Gather the facts
From the assessment: number of servers, vCPUs, edition of SQL Server (Standard or Enterprise), Windows edition, utilisation and criticality. From procurement: agreement type, SA status, purchase dates, versions and core or CAL licensing. Record gaps.
Classify each workload
| Workload | Likely route |
|---|---|
| Spiky or short-lived (test, migration rehearsals) | License-included |
| Steady SQL Server with SA | BYOL with License Mobility, or Dedicated Hosts if dense |
| Steady Windows estate with eligible legacy licences and high density | Dedicated Hosts with BYOL |
| Windows web tiers that can be ported | Port to .NET 10 on Linux and remove the licence (.NET Framework to modern .NET) |
| SQL Server with simple T-SQL | Evaluate PostgreSQL or Babelfish (SQL Server database migration) |
Model three scenarios
Use the code below: all license-included (baseline), a BYOL mix, and a conversion programme. Make every number an input and show the assumptions, because the committee will challenge them.
Review eligibility
Send the shortlisted scenarios to your Microsoft licensing adviser and legal team. Record their written answers in your evidence bucket.
Implement and tag
Set the licence type in the launch template (or AMI) and tag instances by licence route. For Dedicated Hosts, allocate hosts, set host resource groups with License Manager, and plan capacity across at least two Availability Zones for production workloads.
Verify on the bill
Check in the EC2 console or CLI that instances show Windows BYOL where intended, and use Cost Explorer filtered by platform to spot accidental license-included spend. Review monthly.
AWS Console instructions
- EC2 → Instances → select an instance → Details: the Platform details field shows
Windows(license-included) orWindows BYOL. - EC2 → Dedicated Hosts → Allocate Dedicated Host (instance family, AZ, quantity, auto-placement, host recovery), then Actions → Launch instances onto host.
- License Manager → Customer managed licenses → Create license configuration (licence counting type such as vCPU, Core or Socket, a count, and whether the limit is hard), then associate it with AMIs, instances or host resource groups.
- License Manager → Reports (cross-account usage through Organizations).
- Cost Management → Cost Explorer → filter by Service: EC2, group by Platform and Usage type.
AWS CLI
# See which licence mode an image or instance uses. UsageOperation RunInstances:0800 means Windows BYOL
# and RunInstances:0002 means Windows license-included (per AWS prescriptive guidance).
aws ec2 describe-instances --profile learn-sandbox --region us-east-1 \
--query "Reservations[].Instances[].{id:InstanceId,platform:PlatformDetails,usage:UsageOperation}" --output table
# Define a licence configuration that counts cores and blocks over-use (hard limit).
aws license-manager create-license-configuration \
--name hl-m13-sqlserver-ent-cores \
--license-counting-type Core \
--license-count 48 --license-count-hard-limit \
--tags Key=Project,Value=cea-lab Key=Lab,Value=m13-licensing Key=Environment,Value=learn Key=Owner,Value=your-name \
--profile learn-sandbox --region us-east-1
# Show spend by platform over a month (Cost Explorer API calls cost about USD 0.01 each ⚠ VERIFY).
aws ce get-cost-and-usage --profile learn-sandbox --region us-east-1 \
--time-period Start=2026-10-01,End=2026-11-01 --granularity MONTHLY --metrics UnblendedCost \
--filter '{"Dimensions":{"Key":"SERVICE","Values":["Amazon Elastic Compute Cloud - Compute"]}}' \
--group-by Type=DIMENSION,Key=PLATFORM⚠ VERIFY the PLATFORM dimension and the usage-operation codes against your account's billing data before building reports on them. A VM Import licence type of Auto is equivalent to the license-included option and can cause unexpected spend if you intended BYOL; set the type deliberately.
Infrastructure as Code
Design-only: a Dedicated Host is billed per host per hour from allocation until release, whether or not instances run on it, so do not deploy these stacks in the learning account. Use cdk synth, terraform validate and terraform plan to see the shape.
using Amazon.CDK;
using Amazon.CDK.AWS.Budgets;
using Amazon.CDK.AWS.EC2;
using Constructs;
namespace Harbourline.Migration.Infra;
public sealed class LicensingStack : Stack
{
public LicensingStack(Construct scope, string id, IStackProps? props = null)
: base(scope, id, props)
{
// One Dedicated Host for a Windows/SQL Server BYOL cluster. Production would use two hosts in two AZs.
_ = new CfnHost(this, "SqlHost", new CfnHostProps
{
AvailabilityZone = Fn.Select(0, Fn.GetAzs()),
InstanceFamily = "r5", // ⚠ VERIFY the family against the Dedicated Host configuration table
AutoPlacement = "off", // explicit placement keeps licence-bound workloads on licensed hosts
HostRecovery = "on"
});
// A guard rail: alert when monthly EC2 compute spend nears the planned figure.
_ = new CfnBudget(this, "Ec2Budget", new CfnBudgetProps
{
Budget = new CfnBudget.BudgetDataProperty
{
BudgetName = "hl-m13-ec2-compute",
BudgetType = "COST",
TimeUnit = "MONTHLY",
BudgetLimit = new CfnBudget.SpendProperty { Amount = 20, Unit = "USD" },
CostFilters = new Dictionary<string, object>
{
["Service"] = new[] { "Amazon Elastic Compute Cloud - Compute" }
}
},
NotificationsWithSubscribers =
[
new CfnBudget.NotificationWithSubscribersProperty
{
Notification = new CfnBudget.NotificationProperty
{
NotificationType = "ACTUAL",
ComparisonOperator = "GREATER_THAN",
Threshold = 80,
ThresholdType = "PERCENTAGE"
},
Subscribers = [new CfnBudget.SubscriberProperty { SubscriptionType = "EMAIL", Address = "finops@example.com" }]
}
]
});
Amazon.CDK.Tags.Of(this).Add("Project", "cea-lab");
Amazon.CDK.Tags.Of(this).Add("Lab", "m13-licensing");
Amazon.CDK.Tags.Of(this).Add("Environment", "learn");
Amazon.CDK.Tags.Of(this).Add("Owner", "your-name");
}
}Complete code
A licensing cost model. Every price is an input (in a real study you pull them from the AWS Pricing Calculator for your Region); the starting figures are the monthly on-demand costs the AWS prescriptive guidance gives for a c5.xlarge instance running 24 hours a day, and are used here only as illustrative inputs, not as current prices.
// Illustrative monthly on-demand prices for one c5.xlarge (AWS prescriptive guidance example).
var prices = new Prices(
LinuxOnly: 127m,
WindowsLi: 259m,
WindowsSqlStdLi: 609m,
WindowsSqlEntLi: 1353m);
var estate = new Estate(
WindowsAppServers: 40,
SqlStandardServers: 8,
SqlEnterpriseServers: 4,
Months: 36);
// Inputs from Procurement and the licensing adviser. All fictional.
var assumptions = new Assumptions(
SqlSaMonthlyPerServerStd: 150m, // SA + licence amortisation per server per month (Standard)
SqlSaMonthlyPerServerEnt: 600m, // same for Enterprise
PortedWebFraction: 0.6m, // share of Windows app servers ported to Linux containers
PortProgrammeOneOff: 150_000m, // engineering and testing cost of the port
PostgresFraction: 0.5m, // share of SQL Server servers converted to PostgreSQL
ConversionOneOff: 200_000m); // schema/code conversion, rehearsal, reconciliation
var results = new[]
{
Model.AllLicenseIncluded(prices, estate),
Model.SqlByol(prices, estate, assumptions),
Model.ConvertWhatYouCan(prices, estate, assumptions)
};
Console.WriteLine($"{"Scenario",-34} {"Monthly run",14} {"One-off",12} {estate.Months + " months total",18}");
foreach (var r in results)
Console.WriteLine($"{r.Name,-34} {r.MonthlyRun,14:C0} {r.OneOff,12:C0} {r.Total(estate.Months),18:C0}");
var baseline = results[0];
foreach (var r in results.Skip(1))
{
var saving = baseline.MonthlyRun - r.MonthlyRun;
var payback = saving > 0 ? r.OneOff / saving : (decimal?)null;
Console.WriteLine($"{r.Name}: saves {saving:C0} per month; payback {(payback is null ? "never" : $"{payback:F1} months")}");
}
public sealed record Prices(decimal LinuxOnly, decimal WindowsLi, decimal WindowsSqlStdLi, decimal WindowsSqlEntLi);
public sealed record Estate(int WindowsAppServers, int SqlStandardServers, int SqlEnterpriseServers, int Months);
public sealed record Assumptions(
decimal SqlSaMonthlyPerServerStd, decimal SqlSaMonthlyPerServerEnt,
decimal PortedWebFraction, decimal PortProgrammeOneOff,
decimal PostgresFraction, decimal ConversionOneOff);
public sealed record Result(string Name, decimal MonthlyRun, decimal OneOff)
{
public decimal Total(int months) => OneOff + MonthlyRun * months;
}
public static class Model
{
// Baseline: everything license-included on shared tenancy, no change.
public static Result AllLicenseIncluded(Prices p, Estate e) =>
new("All license-included (rehost)",
e.WindowsAppServers * p.WindowsLi
+ e.SqlStandardServers * p.WindowsSqlStdLi
+ e.SqlEnterpriseServers * p.WindowsSqlEntLi,
0m);
// SQL Server BYOL with SA on shared tenancy: Windows still included, SQL Server paid to Microsoft instead.
public static Result SqlByol(Prices p, Estate e, Assumptions a) =>
new("SQL Server BYOL (eligibility review!)",
e.WindowsAppServers * p.WindowsLi
+ e.SqlStandardServers * (p.WindowsLi + a.SqlSaMonthlyPerServerStd)
+ e.SqlEnterpriseServers * (p.WindowsLi + a.SqlSaMonthlyPerServerEnt),
0m);
// Port a share of web servers to Linux containers and convert a share of SQL servers to PostgreSQL.
public static Result ConvertWhatYouCan(Prices p, Estate e, Assumptions a)
{
var portedWeb = (int)Math.Round(e.WindowsAppServers * a.PortedWebFraction);
var remainingWeb = e.WindowsAppServers - portedWeb;
var convStd = (int)Math.Round(e.SqlStandardServers * a.PostgresFraction);
var convEnt = (int)Math.Round(e.SqlEnterpriseServers * a.PostgresFraction);
var monthly =
portedWeb * p.LinuxOnly + remainingWeb * p.WindowsLi
+ convStd * p.LinuxOnly + (e.SqlStandardServers - convStd) * p.WindowsSqlStdLi
+ convEnt * p.LinuxOnly + (e.SqlEnterpriseServers - convEnt) * p.WindowsSqlEntLi;
return new Result("Port web tier + convert half of SQL", monthly, a.PortProgrammeOneOff + a.ConversionOneOff);
}
}With the inputs above, the baseline is 40 x 259 + 8 x 609 + 4 x 1,353 = USD 20,644 per month. SQL Server BYOL lowers it to about USD 17,068 with no one-off cost (if eligible). The conversion scenario lowers the run cost to about USD 13,096 (a saving of roughly USD 7,500 per month) but costs USD 350,000 up front, a payback of about 46 months. Over 36 months it is still the most expensive scenario; over 60 months it beats the baseline but not BYOL. That is why the decision is not obvious, and why the model must be honest about both sides.
Code explained line by line
Pricesholds one price per configuration. The price differences reveal the licence component: Windows adds about 132 per month over Linux in this example, SQL Standard about 350 more, and SQL Enterprise about 1,094 more.EstateandAssumptionsare separate records: the estate comes from discovery, the assumptions from procurement and engineering. Separating them keeps the model reviewable.Model.AllLicenseIncludedis the baseline and the answer to "what if we do nothing clever".Model.SqlByolreplaces the SQL component of the price with the SA and licence amortisation the organisation already pays. It is a cost model, not an eligibility check: the name carries the warning.Model.ConvertWhatYouCansplits servers into ported and remaining groups withMath.Round, then adds the one-off programme costs, kept separate from the monthly run cost so payback can be computed.Result.Totaladds one-off cost to run cost over the horizon. Choosing the horizon (36 months here) changes the answer; show the committee several.- The payback line divides one-off cost by monthly saving and says "never" when there is no saving, instead of dividing by zero or a negative number.
Security considerations
⚠ Learning shortcut — not for production
The model uses illustrative prices and fictional assumptions, and the IaC is design-only. For a real decision, use current Region-specific prices from the AWS Pricing Calculator, the actual contract values from Procurement, and written confirmation of licence eligibility from your Microsoft licensing adviser. A model that looks precise but rests on an assumed entitlement is worse than none.
- Compliance, not just cost. Using a licence you are not entitled to run in AWS is a contractual and audit exposure. Keep eligibility evidence with the register.
- Dedicated Hosts and physical access. Dedicated Hosts give you exclusive hardware, which can also support some regulatory isolation requirements. That is a separate control question, not a side effect to assume.
- Licence tracking is an inventory. License Manager data reveals software versions across your estate; restrict it to the licensing and security teams.
- Cost guard rails. Budgets and alerts catch accidental license-included launches. Use SCPs or tag policies to enforce a licence-route tag on Windows instances if your governance requires it.
Banking use case
Harbourline's model shows that the 40 Windows application servers and 12 SQL Server servers cost about USD 20,700 per month license-included. Procurement confirms active SA on the SQL Enterprise cores but not on Standard, and the Windows licences were bought after 2019, so Windows BYOL on Dedicated Hosts is not available. The decision: use BYOL with License Mobility for the four Enterprise servers (subject to written adviser confirmation), license-included for Standard and for Windows, and fund the web-tier port and the reporting database conversion as the main way to remove licence cost over time. The monthly Cost Explorer review tracks any license-included drift, and License Manager reports go into the quarterly risk review.
Common mistakes
- Assuming Azure Hybrid Benefit rules apply on AWS. They do not; each cloud has its own conditions.
- Dedicated Hosts for small estates. The host is billed in full whether or not it is full. Use them for dense, steady workloads.
- Ignoring Windows when focused on SQL Server. For web tiers, the Windows licence is the main line; porting removes it.
- Choosing the licence mode by accident. Defaults in import tools and AMIs can silently select license-included.
- Comparing against on-premises hardware only. Include licences, SA, hardware refresh, data centre costs and people on the on-premises side too, to be fair both ways.
- Forgetting non-production. Test and rehearsal environments often outnumber production; license-included Windows there adds up. Consider Developer edition where the terms allow, and stop-start schedules.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Bill higher than forecast for Windows | Instances launched license-included instead of BYOL, or Auto licence type | Check Platform details and usage operation; correct the launch template |
| Cannot launch BYOL instance on shared tenancy | Windows BYOL requires dedicated infrastructure | Use a Dedicated Host, or switch to license-included |
| License Manager hard limit blocks a launch | Count of cores or vCPUs exceeded | Review utilisation, raise the entitlement, or release unused instances |
| Dedicated Host shows low utilisation | Wrong family or size, or too many hosts | Right-size placement; consolidate; consider shared tenancy |
| Cost Explorer shows no PLATFORM groups | Dimension or filter incorrect | Check available dimensions in the console and adjust |
| Model shows "never" for payback | Conversion costs more than it saves at current assumptions | Test more aggressive scenarios, a longer horizon, or fewer conversions |
Cost and cleanup
Cost: free for the model and design work. The IaC is design-only: a Dedicated Host bills hourly from allocation until you release it (the AWS guide's example hosts cost on the order of USD 8,000 per month each), so do not deploy. If you create a License Manager configuration or a budget, they cost nothing themselves ⚠ VERIFY the first-budget allowances.
# Delete the licence configuration and budget if you created them.
aws license-manager delete-license-configuration --license-configuration-arn arn:aws:license-manager:us-east-1:123456789012:license-configuration:lic-0123456789abcdef --profile learn-sandbox
aws budgets delete-budget --account-id 123456789012 --budget-name hl-m13-ec2-compute --profile learn-sandbox
# If you ever allocated a Dedicated Host, release it (instances must be stopped or moved first).
aws ec2 release-hosts --host-ids h-0123456789abcdef0 --profile learn-sandbox --region us-east-1
# Confirm nothing tagged Project=cea-lab remains.
aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab --profile learn-sandboxExercises
- 🟢 Guided: Run the model. Change
Monthsto 12, 36 and 60, and write down how the ranking of scenarios changes. - 🟡 Challenge: Add a fourth scenario, "Dedicated Hosts for SQL Enterprise", where four Enterprise servers share two hosts at a monthly price you choose as an input, plus per-core SA. Show the break-even point against shared-tenancy BYOL.
- 🔴 Live problem: The CFO wants a single number for "licence savings from AWS" in the board paper next week, but Procurement cannot confirm SA status for half the SQL Server estate. Write the one-page response: what you can say, what you cannot, and what you need by when.
Assignment
Write licensing-options-paper.md: the estate summary, three costed scenarios from your model with all assumptions, an eligibility question list for your licensing adviser, a licence register template (workload, route, contract reference, approver, review date) and a recommendation.
Solutions
With the sample inputs, the conversion scenario is the most expensive at both 12 and 36 months, because its one-off cost is not yet paid back. At 60 months it beats the all-license-included baseline but still not the BYOL scenario. The ranking changes with the horizon alone.
Why: one-off costs are paid once and savings recur, so the horizon is the most sensitive assumption. A committee should see more than one.
Add Result DedicatedHostsSqlEnt(Prices p, Estate e, Assumptions a, decimal hostMonthly, int hosts, decimal saPerCoreMonthly, int coresPerHost) where SQL Enterprise cost is hosts * hostMonthly + hosts * coresPerHost * saPerCoreMonthly. Break-even is where this equals the shared-tenancy BYOL cost servers * (windows + SA per server). Solve by iterating the number of servers or by dividing the difference.
Why: a host has a fixed cost and a fixed number of cores to licence, so it wins only when enough instances share it. Below that density, shared-tenancy BYOL is cheaper.
Knowledge check
Answer: Windows Server lacks License Mobility, so the permitted BYOL scenarios require dedicated infrastructure such as Dedicated Hosts. AWS guidance also lists date and version limits on eligible licences ⚠ VERIFY current terms.
Answer: On a Dedicated Host you can license by physical cores. In shared tenancy you license by the vCPUs of each instance, which can add up to more cores than the host has for a dense workload.
Answer: The EC2 console Platform details field or the CLI shows Windows BYOL (usage operation RunInstances:0800), versus Windows (license-included, RunInstances:0002).
Answer: It tracks licence usage against rules you define, can enforce hard limits, manages Dedicated Host placement and produces cross-account reports. It does not decide whether you are entitled to use a licence.
Interview questions
- Is AWS cheaper than on premises for Windows and SQL Server? Not automatically. The answer depends on licence route, utilisation and what you can retire or convert. Present a model with assumptions and horizon.
- How would you reduce Windows licensing cost without changing the application? Right-size instances, schedule non-production, use BYOL where eligible, consider Dedicated Hosts for dense steady workloads, and downgrade editions where features allow.
- Who signs off licence eligibility? Procurement and a Microsoft licensing specialist, with legal review. Engineering supplies facts and the cost model.
Certification practice
A company has active Software Assurance on its SQL Server licences and wants to reduce the cost of running SQL Server on EC2. Which statement is most accurate?
A. SQL Server must always be license-included on AWS. B. The company may be able to use License Mobility to bring eligible SQL Server licences to shared tenancy, subject to Microsoft's terms. C. SQL Server licences can never be brought to AWS. D. Dedicated Hosts are required for every SQL Server BYOL scenario.
Answer: B. License Mobility is the route for SQL Server with SA on shared tenancy. A and C are wrong; D is wrong because Dedicated Hosts are an option (physical-core counting), not a requirement.
A bank's steady Windows Server and SQL Server Enterprise workloads run densely on a few powerful servers. It has eligible licences and wants to minimise licence count and cost on AWS. What should the architect evaluate?
A. EC2 Dedicated Hosts with BYOL, licensing at physical-core level, tracked with AWS License Manager, compared against shared-tenancy options. B. Lambda for every database. C. The smallest possible shared instances for all workloads. D. S3 Glacier for licence storage.
Answer: A. Dense, steady workloads with eligible licences are the Dedicated Host use case; License Manager tracks usage. B and D are irrelevant, and C ignores the licence-count effect and likely performance needs.
Completion checklist
- I can name the three licensing routes and when each fits
- I ran the model with three different horizons
- I know which licensing questions go to a specialist, not to an engineer
- I did not deploy the Dedicated Host design and confirmed nothing is billing
Key takeaways
- Licensing is often larger than compute for Microsoft estates, so model it first.
- License-included is flexible and expensive; BYOL is cheaper only if you are eligible and manage evidence.
- Windows BYOL needs dedicated infrastructure; SQL Server with SA can use License Mobility on shared tenancy.
- The strongest long-term saving is removing the licence: port to Linux, convert to PostgreSQL.
- Eligibility is a legal question: get it in writing.
Further reading
- Bring licenses for Windows and SQL Server workloads (AWS Prescriptive Guidance) — source for the Dedicated Host and BYOL facts and example prices used here
- Next: Cut-over and rollback planning
Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.
Network migration and hybrid architecture
Design the network that carries a long migration: plan non-overlapping address space, choose Site-to-Site VPN or Direct Connect, connect with Transit Gateway, share DNS in both directions with Route 53 Resolver, extend Active Directory, and handle latency and bandwidth while applications live in both worlds.
Cut-over and rollback planning
Plan the night the bank switches over: choose a cut-over pattern, schedule freeze windows, define go/no-go criteria and rollback triggers before you need them, reconcile data, shift traffic gradually with weighted DNS, and assemble the evidence a change board and a regulator will ask for.