At its core, an AWS hybrid cloud is about enabling flexible, reliable and cost-effective IT infrastructure. Many organizations are now evaluating how they can mesh private and public resources into a setup that offers superior agility for development and testing, without raising (even lowering) total cost of ownership.
Many organizations are investing in the public cloud with the intent of saving money and boosting competitiveness. However, a recent survey conducted at the Amazon Web Services re:Invent conference found that IT managers and application developers still regard cost, performance, reliability, and security as the top concerns with using purely public infrastructure.
At the recent AWS Summit San Francisco, AWS SVP Andy Jassy made a point of saying that choosing between private and public clouds is not an all-or-nothing proposition. He said that when customers ask him if they need to be either "all in to AWS, or all in on a private cloud" he tells them the answer is no. He then went on to present six use cases organizations should consider when moving to the cloud. It was interesting to note that the first one on his list was dev & test.
When I talk to IT organizations about using Eucalyptus to set up a private or hybrid cloud, they often ask "How do I get started?" Recently, we've published a series of Reference Architectures which are specific to common use cases deployed in the field Let's take a look at how the Dev/Test Reference Architecture might be used as a framework for building a private or hybrid cloud for Dev/Test purposes.