This MOF file is used in the step 7 to configure the domain controller. It uses the LCM-Config.ps1 script that is in the scripts folder.ĭc1InstanceId – This step gets the instance ID for the EC2 instance that has the Name tag value set to the ADServer1NetBIOSName parameter and outputs it for subsequent steps.ĬreateDC1Mof– This step generates a local encrypted MOF file on the first domain controller in the C:\AWSQuickstart\ directory. This step uses the install-ad-modules.ps1 script that is in the scripts folder in the GitHub repo.ĭcsLCMConfig – This step configures the LCM on each EC2 instance from step 1. This ensures that no clear text passwords are saved locally in this Quick Start. It also generates an encryption certificate to encrypt MOF files. As with the first two scenarios, you can choose to deploy the Quick Start into an existing VPC infrastructure.ĭcsInstanceIds – This step gets the instance IDs for EC2 instances that have the Name tag set to ADServer1NetBIOSName and ADServer2NetBIOSName parameters in the Quick Start and outputs them for subsequent steps.ĭcsInstallDscModules – This step installs the xActiveDirectory DSC module and the additional required DSC modules (NetworkingDsc, ComputerManagementDsc, xDnsServer) from the PowerShell Gallery on the instances that were identified by their instance IDs in step 1. AWS Directory Service takes care of AD DS tasks such as building a highly available directory topology, monitoring domain controllers, and configuring backups and snapshots. The AWS CloudFormation template for this scenario builds the base AWS Cloud infrastructure and then deploys AWS Managed Microsoft AD on the AWS Cloud. Scenario 3: Deploy AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD). You can also choose to deploy the Quick Start into your existing VPC infrastructure. As in scenario 1, you manage all AD DS tasks yourself.
The AWS CloudFormation template for this scenario builds the base AWS Cloud infrastructure for AD DS, and you perform several manual steps to extend your existing network to AWS and to promote your domain controllers.
Scenario 2: Extend your on-premises AD DS to AWS on Amazon EC2 instances. It doesn’t include AWS Directory Service, so you handle all AD DS maintenance and monitoring tasks yourself. The AWS CloudFormation template for this scenario builds the AWS Cloud infrastructure, and sets up and configures AD DS and AD-integrated DNS on the AWS Cloud. Scenario 1: Deploy and manage your own AD DS installation on the Amazon EC2 instances.
0 kommentar(er)
