Ours is a B2B SaaS startup (LAMP stack). We are at a very early stage of the Startup. So, we don't need any dedicated hosting at this time. We have planned to use Amazon (not finalized though). In about a month's time we may need a Development environment (maybe on Amazon) for coding and testing and show to early customers.
For now, we want to get the website up and running - just with a sign-up page, and a simple blog - to attract traffic, do some A/B Testing. We want to scale up as we grow.
Can you advise what is the best plan for me ? Amazon EC2 is a good choice for a LAMP B2B SaaS for our current needs and upgrade it as we grow ?
There's really no "right" answer for this question. But of course there are a variety of popular choices.
At our company we're all in with Amazon AWS, and we're very happy with the flexibility and stability that has provided for us.
PS. You could also try starting A/B testing right away using Performable or any other service useful for A/B testing.
For now, we want to get the website up and running - just with a sign-up page,Right now, just set up a static web page on a 10 USD/month shared webhosting somewhere. Or use a service like Performable (they seem to be moving away from landing pages ?). And register for Google Webmaster tools, and start getting your website indexed. Then switch to your 'real' hosting platform when you're ready and cancel the shared hosting account.
and a simple blogSelf-hosted Wordpress takes some work. Hosted Wordpress is easy to get started with, but locks you in on the URL structure "blog.company.com" (because you need the separate hostname "blog" to point to the other provider). Think about SEO, how much energy you'll really invest in blogging, and your in-house sysadmin skills, and make a decision and move on.
Amazon EC2 is a good choice for a LAMP B2B SaaSSure it is. As would Linode, Rackspace dedicated servers, Rackspace Cloud, Gigenet servers, and a number of other hosting platforms be. Small- to mid-scale PHP hosting is ubiquitous.
What you should mainly think about is where you'll choose to split between in-house sysadmin responsibility (securing servers, patching servers, database administration, data backup), and external fully managed services.
(Nota bene: Amazon has completely different maintenance levels built into their different products. Their hosted load balancer and hosted MySQL are fully managed, but EC2 servers aren't managed by them at all (you must do backups, OS security patching, etc).)