You can access any S3 bucket through SSL on the s3.amazonaws.com domain (for which they have a wildcard cert), but you can't have SSL for your custom domain: https://stackoverflow.com/a/11203685/458614
This seems like such a huge hack, but for my single-page web app, what if I...
- Buy example.com with SSL cert
- https://example.com has a full-page iframe linking to https://example.s3.amazonaws.com/index.html
- Voilà
End users will never know the difference. Is there any reason not to do this?
As for why I would want to do this: I can have a tiny tiny tiny web server repeatedly serving up a 250 byte index.html file with only a full-page iframe pointing to S3, and that's it, and have everything else with the speed and reliability of S3.