Matt

You can already [configured a private S3 bucket](https://github.com/awslabs/amazon-eks-ami/blob/master/scripts/install-worker.sh#L24-L25). Is there a reason that's insufficient for your use case?

I want to verify that there are no outstanding concerns/issues, and I'll try to get this merged this week.

Per #1045, we're making volume type configurable in make arguments, which will cause this PR to not work. If you want to update it based on that change (hopefully merged...

We've been discussing this internally. The blocker has been that the `awscli` version in the `yum` repos is fairly out of date, and while we're working on installing the `awscli`...

From poking around the code and seeing your info above, it's not apparent to me what went wrong yet. Would it be convenient to add additional logging? Would be curious...

> Not really for our configuration; would have to set up a whole custom build pipeline where we currently use the upstream image. A repro would make it a lot...

Do this happen consistently? Did you try manually cleaning up the SG to see why it was failing? I'm curious what is hanging around, causing this issue. [Here's a post...

I see. Can you share the config you're using to create the service with any private details changed? If you can provide yaml that consistently reproduces this (assuming the issue...

@kishorj Can you describe the issue we discussed here? Or create a different tracking issue in lieu of this one?

We've updated our release to do this.