I am planning to deploy an Active Directory and Domain Controller on AWS for my company. It will primarily be used for these:
- User Authorization (Login/Logoff Process)
- File Sharing / Management (Employee can share files with eachother)
- Deploying GPO (To enforce some IT policy i.e. USB Access, etc).
In addition to that, the Server will be acting as Sharepoint Server as well (that means it will need SQL and IIS).
What i am asking is.... [Please see edit]?
If it is a physical server, what i would do is:
- Buy the PC server.
- Install Windows Server (if it is not already there).
- Configure DHCP/DNS (and all other networking stuff).
- Install and Configure Domain Controller.
- Install and Configure Active Directory.
- Configure and Enforce GPO as needed.
And i will be doing all those stuff mentioned from above either from the physical machine or from remote connection.
PS: Yes i am aware of the implication of losing access to the Domain Controller (i.e Network outage). One way to mitigate this is by deploying a local cache storage on premise i suppose.
EDIT I really need AD/DC to manage logins, organizational hierarchy and policy (GPO). This seems to be the reverse of most server setup. I'd like to use a cloud based service to act as the primary Domain controller and in the future, also to provide local authentication to manage print/file service (if this is possible).
But i'd really like to know if it is possible? More importantly is it a good practice?
I don't mind using either Amazon or Azure.