← Back to Blogs

MICROSOFT WORKLOADS ON AWS

Windows Workloads in the Cloud

Moving Windows applications to AWS requires a plan for compute, databases, identity, licensing, and operations. Start with the workload requirements and validate the complete application before production cutover.

Understand the application stack

Document Windows Server versions, IIS applications, SQL Server databases, Active Directory dependencies, file shares, scheduled tasks, certificates, and third-party components. Identify unsupported software and applications that depend on fixed server names, network paths, or local storage.

Plan the target architecture

Compute and networking

Select an Amazon EC2 configuration and network design that fit the workload, access requirements, and expected demand.

Databases

Evaluate SQL Server on EC2 or a suitable Amazon RDS configuration against application compatibility and administration needs.

Identity and access

Plan directory integration, administrative roles, authentication, and access approvals.

Operations and protection

Define patching, monitoring, logging, backups, restore tests, and incident responsibilities.

Review licensing before choosing a configuration

Evaluate licence-included options and the eligibility of existing licences with the relevant vendors and your licensing adviser. Bring-your-own-licence rights vary by product, agreement, acquisition date, and hosting arrangement. Validate these conditions before using them in a cost model.

Choose the migration path

AWS Transform MGN, formerly AWS Application Migration Service, supports rehosting eligible servers to Amazon EC2. Database migration may require a separate approach, including compatibility checks and data validation. Select the tools after assessing application dependencies and target requirements.

Validate cutover and recovery

Test application functions, identity integration, database connections, scheduled tasks, and external interfaces. Confirm monitoring and backups in the target environment. Agree on the maintenance window, acceptance checks, recovery steps, and rollback conditions. Downtime depends on the workload and migration design.

Manage the environment after migration

Use appropriate AWS tools for monitoring, configuration, and administration. Restrict administrative access, review permissions, track patch status, and test recovery procedures. Compare resource sizing and costs with observed demand before committing to longer-term purchasing arrangements.

Work with an experienced team

Anjana Cloud9 Solutions holds the AWS Microsoft Workloads Consulting Competency. Our experienced cloud architects and engineers support assessment, migration planning, implementation, and operational handover for Windows application environments.

Official resources

Continue reading

Migrating On-Premises Workloads to AWS

Read article →

Navigating Success with AWS Well-Architected

Read article →

Planning a similar project? Talk to our team.