Hello,
we have launch our Directory Service and trying to launch Admin Ec2 instance to manage The users and all, but when we start the execution to launch admin EC2 instance it is failing on the step of domain join, and giving following error,
Step fails when it is verifying the command has completed. Command b1de3f81-5da6-4fc2-a199-f2426c67cf46 returns unexpected invocation result: {Status=[Failed], ResponseCode=[1], Output=[status:Failed, code:0, message:Domain Join failed, ComputerName:EC2AMAZ-0DB4A8N; Message:A WebException with status ConnectFailure was thrown.; ErrorCode:; ErrorType:Amazon.Runtime.AmazonServiceException; StatusCode:0, error: Domain join failed. ----------ERROR------- Failed to create domain computer account 'EC2AMAZ-0DB4A8N', Message=A WebException with status ConnectFailure was thrown.,ErrorCode=,ErrorType=Sender,StatusCode=0 Amazon.Runtime.AmazonServiceException: A WebException with status ConnectFailure was thrown. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 52.95.35.27:443
Though my Directory and instance are in same private subnet.
can anyone please help me to debug the actual cause of this issue?
So, the thing is actually we do not have public access, our environment needs be in private subnet only
Did you set the DNS name of the directory specified for Microsoft AD in the DHCP option set and the DNS address of Microsoft AD for the domain name server? https://docs.aws.amazon.com/vpc/latest/userguide/VPC_DHCP_Options.html
Sorry, i am not that aware about this, but when i do create this in my environment does it affect any other resources in my VPC?
Yes, EC2 running within the VPC will now query the DNS server configured in the DHCP option set.