Amazon's virtual private cloud service has been advanced to public beta.
It claimed that it is a ‘secure and seamless bridge between a company's existing IT infrastructure and the Amazon Web Services (AWS) cloud' and will enable enterprises to connect their existing infrastructure to a set of isolated AWS compute resources via a virtual private network connection.
It will also extend existing management capabilities such as security services, firewalls, and intrusion detection systems to include their AWS resources. Features include the ability to create a virtual private cloud (VPC) on AWS's scalable infrastructure, and specify its private IP address range from any block you choose.
Users can also divide their VPC's private IP address range into one or more subnets in a manner convenient for managing applications and services that they run in their cloud.
The company has said that will move users of its EC2 cloud computing platform to access the cloud as a beta service and customers will only incur charges after the service is activated.
From a security standpoint, functionality allows the extension of existing security and management policies within your IT infrastructure to a users cloud as if they were running within your infrastructure.
It said that as a user's cloud can exist behind a corporate firewall, corporate applications can be seamlessly moved into the AWS cloud without changing how users access your applications. It also claimed that by using Amazon VPC for disaster recovery, you can have all the benefits of a disaster recovery site at a fraction of the normal cost.
In terms of pricing, users are charged for each ‘VPN Connection-hour' in which the VPN Connection is available for your use, and for the data transferred via the VPN Connection. There is no charge for data transferred in until the 30th June 2010, while data transferred out is charged at $0.17 per GB for the first ten TB per month.
Steve Moyle, CTO and founder of Secerno, claimed that regardless of the pricing model for computing power, there is absolutely no correlation with the level of security provided.
He said: “My take on this is broadly positive, as it is getting closer to the true cloud model of ‘pay per drink' where the price of the drink is dependent on how many other drinkers there are (and the size of the barrel). All of this, however, is completely orthogonal to whether the drink is toxic or not (or whether other drinkers are not spitting in the barrel themselves).
“We need to ensure that all drinkers only use special drinking-straws with filters built in like those at istraw. These ‘virtual cloud straws' are simply filtering firewalls that only permit 'clean and safe drink' to pass the lips of the drinker. Now, a security drinking straw that also runs in the cloud, is flexible and can be powered on a 'pay per filtering' model fits the vision of the cloud.”