On 2014-10-11 06:51, Edward Ned Harvey (lopser) wrote: > Like I said about it not being easy to uproot your server and *either* > upgrade to bigger hardware on their service, or migrating all your services > to another provider.
Three things: 1) If you been using a t1.small "for years", you've probably noticed that your bill went down. A 2 minute fix here is: a) stop your instance b) select a bigger non-burstable instance (you'll be limited based on your choice of hvm/pv AMI) c) start your instance For the price of what you used to pay when you started with the t1.micro, you can probably get an m3.medium or something along those lines that'll make you much happier. 2) If you use AWS services (ELB, S3, RDS etc...) you can pay your way out of trouble. You pay more, and it scales up, and the problems go away. You cannot uproot and go overnight, because the equivalent services from the other vendors use different API, but you knew that when you got in, that was the downside of being able to get going in minutes. 3) If you use AWS as a cloud infrastructure, then surely, you've automated the installs etc... You should be able to move to a different provider in a day or two. To be honest, you're so technical and picky about all the details that I don't understand why you don't rent a bunch of physicals from OVH or Peer 1, run VMWare, and run your own cloud. -- Yves. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
