One of the most common requirements clients have when moving to Amazon WorkSpaces is that it performs as well or better than their current solution. To meet this requirement, clients must often place an Active Directory Domain Controller within their AWS environment.
Let’s review several of the benefits of placing a Domain Controller within the AWS environment.
Benefit One: AWS architected designs include at least one Domain Controller per physical location.
Benefit Two: Placing a Domain Controller within AWS ensures optimized traffic across the Direct Connect or a site-to-site VPN.:
Benefit Three: Direct Connects or site-to-site VPNs are fixed quantities:
Benefit Four: Placing an Active Directory Domain Controller within the AWS solution is scalable, addressing the continuing changing and growing needs of the business. From an initial deployment or growth to thousands of Workspaces, configurations can be built to fit both today’s and tomorrow’s needs.
In addition to the four benefits, security and network access within Amazon WorkSpaces is always a consideration. From a security perspective, securing and managing a Domain Controller in AWS utilizes the same approaches, skills, and tools as an on-premises Domain Controller.
You read the business snapshots and goals from our clients. Sound familiar? We all know that Active Directory problems can inhibit performance and lead to a less-than-stellar desktop experience. Placing an Active Directory domain controller within AWS will provide an immediate performance benefit for Amazon WorkSpaces and any future AD-dependent services located within the AWS environment. Active Directory Domain Controllers in AWS are part of the toolbox to provide positive work experience.