Open service-workbench-collaborations opened 9 months ago
Have you found a solution to this issue? We are seeing a similar problem. We are trying to deploy in an existing VPC and the First EC2 is created successfully, however when CloudFormation creates the second EC2 it never continues. The EC2 is created successfully, but for some reason CloudFormation doesn't recognize it and it will eventually time-out.
There are a few issues that I found by looking at the cloudwatch logs on my runs. if you look at the error CREATE_FAILED, Received FAILURE signal with UniqueId i-################ it does not tell you much. Neither does the one that caused that which is from the nested cloudformation that that stack spawns. However, if you look into Cloudwatch logs for the microsoft-pki-TwoTierCAStack (the nested cloudformation that is spawned when you run this guy). I dont know if you guys had the same issues I had but this is what I encountered and what I did to workaround it. My first run through some errors because I only added my service account to AWS Delegated Enterprise Certificate Authority Administrators and not the AWS Delegated Administrator groups (both are required). With that done I started getting an error because Computer 'EC2AMAZ-XXXXXX' was successfully joined to the new domain 'mydomain.com', but renaming it to 'ENTCA1' failed with the following error message: The account already This is because the cloudformation only reverses the AWS stuff and not the AD stuff that it does. So, you need to delete both ENTCA1 from the computer's OU and from the DNS records. Once this was done I ran it again and I got the following error
Connecting to remote server ENTCA1 failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (ENTCA1:String) [], PSRemotingTransportException + FullyQualifiedErrorId : URLNotAvailable,PSSessionStateBroken
Now, this is the main reason that I believe its causing the majority of the issues here and I think that AWS needs to amend the requirements. Howerver before I go over this workaround there is something that needs to be done or this will not work if you got this error and remembering that cloudformation will not revert and windows changes, you will need to:
After all that was done I ran it again and everything worked.
Hopefully, this will work for you guys. I highly recommend looking into cloudwatch for the errors as they will be in the /aws/Quick_Start/whatever_you_named_this and as they are most likely related to windows and not cloudformation
I tried to Deploy into a new VPC using default CIDRs and IPs in us-east-1. With 3 combinations of AZs, us-east-1a/us-east-1c, or us-east-1a/us-east-1b, or us-east-1a/us-east-1b, I kept getting the same error: DomainController2, CREATE_FAILED, Received FAILURE signal with UniqueId i-################ :(