Anyone here use Amazon WorkSpaces?
1 10 May 2018 23:56 by u/obvious-throwaway-
I'm trying to better understand how DNS works with WorkSpaces and VPC in general. I know you can set external physical computers to join your domain using VPN, but it requires DNS to be enabled. The DNS name I used is also an external DNS name, so now when I make DNS requests for that name, it times out because it can't find it on the VPC network. I need to figure out how to tell it ask an outside DNS server when the local DNS server can't find something. I see something called Route 53, but I'm not sure if that's the route to go. Anyone familiar with VPC DNS and how it works?
2 comments
0 u/curomo 11 May 2018 00:48
Why do you want the workspace on the domain? It will affect how complex your solution needs to be.
If it's just user auth, then you can bridge your IAM auth to your domain. If you're doing advanced desktop management, you might find that it's easier to just manage the image and treat it as inmutable.
If you really need to be properly domain joined, I think you can give the workspace and address in your vpc where you have a domain controller.
And of course if you weren't talking about ad and just need a dns domain, you'll just do it all in route53
0 u/obvious-throwaway- [OP] 11 May 2018 01:32
AWS sets up two Linux domain controllers for the workspaces. I'm using these domain controllers as my sole domain controllers. Amazon manages these controllers, so it's like having 2 completely managed domain controllers.
I want to use these managed domain controllers to manage my whole network, I just need help with getting the DNS to forward through when it can't resolve locally.