Skip to main content

Amazon EC2 goes live, past its beta!

AWS blog

Here's what's happening today:

  • Amazon EC2 is now in full production. The beta label is gone.
  • There's now an SLA (Service Level Agreement) for EC2.
  • Microsoft Windows is now available in beta form on EC2.
  • Microsoft SQL Server is now available in beta form on EC2.
  • We plan to release an interactive AWS management console.
  • We plan to release new load balancing, automatic scaling, and cloud monitoring services.

Let's take a look at each of these items in turn.

Production - After a two year beta period, Amazon EC2 is now ready for production. During the beta we heard and responded to an incredible amount of customer feedback, adding support for powerful features such as Availability Zones, Elastic Block Storage, Elastic IP Addresses, multiple instance types, support for the OpenSolaris and Windows operating systems, and (as of today) a Service Level Agreement. Regular EC2 accounts are allowed to run up to 20 simultaneous instances. Requests for hundreds and even thousands of additional instances are granted all the time and can be made here.

SLA - The new EC2 Service Level Agreement works at the Region level. Each EC2 Region (there's only one right now but there will be more in the future) is divided into a number of Availability Zones. The SLA specifies that each Region will be available at least 99.95% of the time. Per the SLA, a Region is unavailable if more than one of its Availability Zones does not have external connectivity.



AWS blog

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!