1 Answer
- Newest
- Most votes
- Most comments
0
Hi, you could try the following steps:
- Enable Network Connectivity: Ensure your office machines can reach AWS AD using a Site-to-Site VPN or AWS Direct Connect.
- Set Up DNS: Point your office network’s DNS server to the AWS Directory Service-provided IP addresses.
- Join the Domain: Configure your Windows 11 machines to join the AWS AD domain.
- Test Domain Login: Create a test user in AWS AD and verify you can log in from an office machine. This keeps the solution brief and focused. Let me know if it helps to solve the issue.
answered 2 months ago
Relevant content
- Accepted Answerasked 3 years ago
- Accepted Answerasked 4 years ago
- asked 3 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
ok, I tried creating a "site-to-site VPN", but I'm using the "ER605 Omada Gigabit VPN Router" from TP-LINK Do you know of any tutorials that help me with exactly what I need?
Seems this scenario should be divided into 2 separate issues: VPN Setup and Domain join for Windows machines.
For the VPN part, you should check with your vendor if your device supports the recommended requirements documented at https://docs.aws.amazon.com/vpn/latest/s2svpn/CGRequirements.html afterwards you should check the getting started documentation to setup VPN connections https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html
Once you have established the tunnel into you VPC, than you can address the Join Domain part, make sure to review the use case that best matches your planned use of AWS Managed Microsoft AD https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ms_ad_use_cases.html
Hope this helps.