DomainController2 Timeout in Scenario 1 about quickstart-microsoft-activedirectory

[neilalex]

Hm, my repo was in a subfolder in the bucket, though not certain why that would make a difference. Around three months ago I remember having an issue using a bucket in us-east-2, which resolved after I tried us-east-1. Also, when cloning the repo, make sure to use --recursive so that the submodules come down?

 
Altogether, the steps I took were --

In S3:
Create bucket my-bucket-name in us-east-1
Create subfolder aws, and then subfolder aws-quickstart under that, both with AES-256 encryption

On a local machine (with git + AWS CLI installed, git set up for use with github), in some temp location:

git clone --recursive [email protected]:aws-quickstart/quickstart-microsoft-activedirectory.git
aws s3 cp --recursive quickstart-microsoft-activedirectory s3://my-bucket-name/aws/aws-quickstart/quickstart-microsoft-activedirectory

CloudFormation, Amazon S3 template URL:
https://my-bucket-name.s3.amazonaws.com/aws/aws-quickstart/quickstart-microsoft-activedirectory/templates/ad-master-1.template

CloudFormation, In the template itself:
Quick Start S3 Bucket Name:
my-bucket-name

Quick Start S3 Key Prefix:
aws/aws-quickstart/quickstart-microsoft-activedirectory/

 
As for Amazon's buckets via links in the Quickstart being broken, no official idea though I did see that #62 pointed that out too.

[neilalex]

If it means anything, I was able to run scenario 1 earlier today with no issues, using a custom bucket and ad-master-1.template. Repo was cloned when the tip was at 077aa1486.

I'd run into the issue you describe when using Amazon's bucket, and it almost seemed like the custom bucket would have the issue as well, as it took the job a solid 45 minutes to work through the DC2 step. Eventually it moved past that though?

[cdilga]

Was there anything special you had to do to get the custom bucket working well?
When I did it, I set the bucket name to my-completely-unique-bucket-name and the key to / and just uploaded the cloned repo - at 18c6b85

Are there implicit assumptions about the key being something other than bucket root / or anything similar?

Also, we can verify that using Amazon's buckets from links in the Quickstart are as of this moment broken?

[cdilga]

Thanks, this works!
What I didn't realise was the necessity to have the --recursive flag for the GitRepo, which interestingly fails at the same point 🤔

I think this issue should remain open until the AWS provided bucket can be updated to work.
However, perhaps updating the Readme or a wiki would help others to setup their own custom buckets and get the quick-start deployed.

I'm happy to do a PR to the Readme outlining the specific steps required to setup with a custom bucket as an intermediate step if that would be accepted and within the contribution guidelines

[neilalex]

Ah glad to hear it! I'm just a user though I'd fully support any notes around this in the readme -- definitely spent more time trying to figure that one out myself several months ago than I'd wanted. Sorry it didn't occur to me sooner

[virtlima]

@neilalex Thanks for the Suggestion, we try and add a reference to using your own S3 Buckets and the --recursive flag to grab all repos. sorry for the inconvenience. @cdilga where you able to get it running, seems so.

[davmayd]

Fixed by #114