First impressions are that it looks and feels very similar to Ylastic, but straight from the horses mouth (is tha a saying?  i think it is).  Even though I have some level of attachment and commitment to Ylastic, practicality says that I should be using Amazon’s console – especially since it’s free.  The only saving grace right now is that the AWS console supports EC2 – but Amazon promises support for it’s other services coming very soon.

Ouch!  I really hope Ylastic can come up with a way to differentiate itself from Amazon’s offering.  I hate to see when innovative and useful startups get obscured by one of the big boys without an M&A deal going down.

If you have an AWS account, you should be able to access your management console from here: https://console.aws.amazon.com/

Many of you have asked us to let you know ahead of time about features and services that are currently under development so that you can better plan for how that functionality might integrate with your applications. To that end, we are excited to share some early details with you about a new offering we have under development here at AWS — a content delivery service.

This new service will provide you a high performance method of distributing content to end users, giving your customers low latency and high data transfer rates when they access your objects. The initial release will help developers and businesses who need to deliver popular, publicly readable content over HTTP connections. Our goal is to create a content delivery service that:

 

• Lets developers and businesses get started easily – there are no minimum fees and no commitments. You will only pay for what you actually use.
• Is simple and easy to use – a single, simple API call is all that is needed to get started delivering your content.
• Works seamlessly with Amazon S3 – this gives you durable storage for the original, definitive versions of your files while making the content delivery service easier to use.
• Has a global presence – we use a global network of edge locations on three continents to deliver your content from the most appropriate location.

 

You’ll start by storing the original version of your objects in Amazon S3, making sure they are publicly readable. Then, you’ll make a simple API call to register your bucket with the new content delivery service. This API call will return a new domain name for you to include in your web pages or application. When clients request an object using this domain name, they will be automatically routed to the nearest edge location for high performance delivery of your content. It’s that simple.

We’re currently working with a small group of private beta customers, and expect to have this service widely available before the end of the year. If you’d like to be notified when we launch, please let us know by clicking here.

Sincerely,

The Amazon Web Services Team