I have a question regarding deploying my app to S3 and serving it straight from there.
We have a platform that hosts events, so whenever we have events happening, they drive a lot of traffic to the various parts of our platform. Soon these will be ember apps that each serve a specific purpose.
Currently we are looking into hosting the apps on a LAMP stack and using apache .htaccess files to route all traffic to the
index.html page. I’ve done this a few times and I know it’s tried and tested in the community as well.
For this we will be using the S3 deploy plugin along with a custom one I’m making to zip the files and use a configuration script to launch new EC2 servers behind a load balancer and auto scaling group to make sure we’re prepared for high amounts of traffic when it occurs.
But I have seen people hosting their apps directly from S3, which seems intriguing to me as it will take a few steps out of the equation for us as we run the other PHP portions of our app (at least until it’s all been migrated to an ember-cli app).
By question is how does hosting an ember app in S3 scale in terms of when a large volume of traffic attempts to hit and use the app all at the same time.
Right now as I mentioned before we are preparing for this by allowing EC2 to provision new servers for us that will have our code, and use a load balancer that will point traffic to one of the several servers running at the time. How does that type of scenario play out when hosting on S3?
If you host this way I want to hear from you, how do you handle this? Specifically, when it comes to high traffic volume what is your strategy if any.
I welcome new ideas but we really want to try to stick with an all AWS solution so we really aren’t interested in using something else like Heroku, etc. Although if you make a good case for it I may be able to persuade my team that direction.