Elastic Beanstalk runs with Amazon EC2, S3, Elastic Load Balancing, Auto-Scaling and Simple Notification Service on the Amazon Linux AMI.Elastic Beanstalk allows a developer to upload an application to Elastic Beanstalk using the AWS Management Console, API’s or the AWS toolkit for Eclipse and automatically deploys and provisions the necessary services required to run the application.

Developers upload their applications via a standard war file and after deployment the application can be accessed via an auto generated or custom url.

Management features that are standard in Beanstalk once an application is deployed include CloudWatch monitoring metrics, email notifications, runtime deployment of applications and the ability to restart Amazon EC2 application servers with one command.

After deployment, developers can adjust default application settings such as database options, storage services and load balancing with Elastic Beanstalk. One of the key features that will appeal to developers is the ability to pass environment variables through the Elastic Beanstalk console.

The beta iteration of Beanstalk is ready for Java Developers running Apache Tomcat and has initially been launched only in the AWS United States East Region. Once out of beta Amazon expects to release Beanstalk to multiple regions and for additional development stacks such as PHP.

The release of Beanstalk might affect the fortunes of PAAS providers like Rightscale, Elastra and Cloudkick (Although Cloudkick  was recently acquired by Rackspace) who have created Cloud Management solutions specifically for Amazon AWS. Pricing for Elastic Beanstalk service is free and users only pay for the managed resources such as EC2 and S3 that their deployed application use on AWS.

The initial lack of capabilities in the provider interfaces created the market for cloud consoles. The initial crop of cloud consoles, however, has grown beyond simply providing a better interface into the cloud. This market has evolved into cloud brokers that act as the trust layer between the customer and their cloud infrastructures. The evolution from cloud console to cloud broker occurred in less than a year. In 2008, the only way to access Amazon Web Services was a command-line tool or writing your own code. As a result, a number of people built their own custom web interfaces for accessing AWS and a number of third-party tools like enStratus appeared in the market to simplify the job.

As the market changed, the role of a pure console became obsolete. Amazon added a graphical console for AWS. Today, all cloud providers have some form of basic web interface into their services. Though most third-parties still provide better front-ends with more features than the provider consoles, the third-parties have become something much more significant: cloud management tools and cloud brokers.

A cloud management tool adds functionality beyond the simple management of raw cloud assets. RightScale, for example, provides robust auto-scaling beyond what AWS auto-scaling allows. enStratus, on the other hand, provides key management that enables complete encryption of data at rest and in transit in the public cloud without the cloud provider being able to gain access to your keys.

Cloud brokers offer yet another layer of functionality on top of cloud management tools. A cloud broker provides a single interface through which you can manage multiple clouds and share resources across clouds. A cloud broker provides the following capabilities:

• It provides a single interface for interacting with multiple clouds
• It operates outside of the clouds it controls and monitors those clouds
• It detects cloud failures and reacts in some appropriate way to those failures
• It can move infrastructure elements from one cloud (public or private) to another

A cloud broker is a critical piece of your public cloud infrastructure. Minimally, a cloud broker provides a solid business continuity strategy. Without a cloud broker, your infrastructure is at risk against failures in your cloud provider.

The ultimate failure is, of course, the cloud provider going out of business. Outside the cloud, you are somewhat isolated from vendors going out of business. For example, if your non-cloud infrastructure is built entirely on Windows, your Windows desktops and servers will still start up if Microsoft were to declare bankruptcy. If, on the other hand, your infrastructure is running entirely in Azure and you have no cloud broker, you go out of business along with Microsoft. If you are a public company, the argument that “Microsoft will never go out of business” is not sufficient for SOX compliance. Even if it were (or if you are a private company), you should keep in mind that no one ever thought Enron would go out of business or that GM would declare bankruptcy.

A cloud broker can spread your operations across multiple cloud infrastructures and enable real-time disaster recovery into a secondary cloud. If Amazon were to suddenly disappear for some arbitrary reason, enStratus can enable you to bring that infrastructure back up in Rackspace; for example, with little (or even no) data loss.

In the future, cloud brokers should evolve into brokers in the truest sense of the word “broker”. The Holy Grail in the cloud broker world is the ability to automatically decide the least expensive cloud components for efficiently operating your systems and move those components around different public clouds based on pricing and quality of service. Though we’re still a long way from that vision, cloud brokers are creating the building blocks that will make the vision possible.

George Reese is the CTO of enStratus™, the provider of the leading cloud management platform for enterprise applications. George is also the author of the #1 selling cloud computing book “Cloud Applications Architecture“. To learn more about enStratus visit www.enstratus.com