hbiz
asked on
amazon ec2 design
I have a project I'd like to migrate from traditional shared hosting to amazon ec2. I've read the documentation and I'm wondering how and which instances i should deploy given the following project needs :
A MySQL server keeping track of user data
A place to store uploaded user images
A front end flash and PHP environment running symfony
Should each of these be running on one micro server s3 backed or should they all have their own dedicated instances. Also is ebs backed a better idea or is it not worth the extra expense?
Thanks for your time
A MySQL server keeping track of user data
A place to store uploaded user images
A front end flash and PHP environment running symfony
Should each of these be running on one micro server s3 backed or should they all have their own dedicated instances. Also is ebs backed a better idea or is it not worth the extra expense?
Thanks for your time
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The project currently has:
-a MySQL server to store user data
-stores uploaded images from users. Images need to be retrieved later on using a url to the specific image.
-a flash and php frontend using symfony 1.4
-git based source control
- developer specific subdomains (ex: developerName.theproject.c
-requires SSL endpoints for parts of the site
My initial thought was to put the DB on it's own dedicated instance. The flash and php frontend on web server instances and store the uploaded images in a seperate EBS volume that's universally accessible. I would use cloudwatch to spawn new instances of the web server images when necessary and a load balancer to distribute the traffic.
Any suggestions?
Thanks for your time