4 ms·

S3 can HTTPS for static hosting if it's done through CloudFront. Are there other reasons to not use S3 for static web hosting?

• DVassallo 7y ago
  No CI/CD — You have to set it up yourself. Once you use Netlify/Zeit, you will never use S3 for static hosting again.
  • chickenpotpie 7y ago
    That's great if all my company makes is static websites, but if we have a bunch of other CI/CD for other projects, I'm not going to introduce a new tool for people to use to make an already simple pipeline simpler.
  • zomglings 7y ago
    Setting up a CI/CD pipeline to publish a static website to S3 using (for example) GitHub actions is pretty much a triviality.
  • nostrebored 7y ago
    Setting up CI/CD via CodePipeline for a static website is trivial. Beyond that, Amplify Console offers an extremely easy experience deploying static websites, with built in blue/green deployments. https://aws.amazon.com/blogs/aws/amplify-console-hosting-for-fullstack-serverless-web-apps/ https://aws.amazon.com/blogs/aws/amplify-console-hosting-for...
  • NikolaeVarius 7y ago
    The CI/CD pipeline is "aws s3 cp"