- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Are there any concerns with the architecture approach I have taken so far?
You cannot use WorkSpaces with Shared VPC, Shared Managed AD.
How do I bypass/fix the issue I am facing with Registration of AD?
In order to make this work for your setup, you need to setup AD Connector for WorkSpaces. This will require you to enable traffic routing to the AWS Account/VPC where the Managed AD is deployed. You can achieve this with VPC Peering or Transit Gateway.
When attempting to do so, the only subnets displayed on the register window are a private and public subnet which are in the same AZ.
Amazon WorkSpaces is not supported in all available AZ in certain regions. In US-EAST-1, the only AZ that is supported by Amazon WorkSpaces are use1-az2, use1-az4, and use1-az6. You can find this AZ mapping in RAM for the account.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren