Compatibility with cloudfront

[florent-blanvillain]

Is it possible to use this adapter with cloudfront (and s3) ?

It seems that cloudfront doesn't use the Index Document specified by ember-deploy-s3-index on revision activation. Can anyone confirm please ?

As a non satisfying workaround, I wanted to set manually the "Default Root Object" of my Cloudfront distribution to the latest index.html revision (something like myapp:6512e6a.html), but cloudfront does not accept the colon character.

[timiyay]

Has anyone found an automated workaround for this issue? It's turning out to be a dealbreaker for serving your Ember index over HTTPS. Using a custom domain for an S3 static website, and serving it over HTTPS, requires Cloudfront.

UPDATE: it appears that this issue might be avoidable. At present, my Cloudfront distribution doesn't have a Default Root Object, which is resulting in the S3 website Index Document being used instead (which is what we want).

[LevelbossMike]

I can't confirm this to not work because I was using this plugin before on a client application with exactly the same setup that you are describing @florent-blanvillain

I also setup a test project for the new addon https://github.com/ember-cli-deploy/ember-cli-deploy-s3-index which serves index.html as the default root object and this also works as expected.

What you can't do is to tell cloudfront to cache the activated index.html. Actually you can but then you have to invalidate the cache on activation of another revision which takes a long time. You can use other CDNs instead to do that (e.g. Fastly) but Cloudfront won't work in a great way in this regard. I am currently in the process of writing this up and including this in the README of https://github.com/ember-cli-deploy/ember-cli-deploy-s3-index. You can follow ember-cli-deploy/ember-cli-deploy-s3-index#15 for progress on this