AUTHOR: http://aws.typepad.com/aws/2011/03/new-approach-amazon-ec2-networking.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« IAM Now Available for Amazon CloudFront | Main | Now Available: Windows Server 2008 R2 on Amazon EC2 »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef0147e13e32bd970b

Listed below are links to weblogs that reference A New Approach to Amazon EC2 Networking:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Simon

Hi Jeff,

Whats the ETA on IPV6 support?

Simon

Dear Jeff,
We are a small startup and I'm looking to host all the IT in the cloud.
Is it possible to install Active Directory on Windows 2008 Server running on EC2 instance, to place it under the Virtual Private Cloud, all the workstations will added as a members of this domain and will work transparently via VPN from internet.
Thanks,
Simon

Pve

Great stuff. Congrats to Werner and his team!

Now, what about your roadmap for IPv6 integration?
I'd like to see two features in particular.
1. Public IPv6 internetfacing addresses on EC2 hosts, S3 and Cloudfront.
2. 'private' IPv6 connections to above that are restricted to a certain IPv6 subnet (i.e. my datacenter or client lan). 'private' between quotes, because you can use public IPv6 address space.
Remember that with IPv6 there is no real need for NAT or VPN. Everything can be handled on the address or routing level.
This really simplifies network design and troubleshooting.

Roland

What about IPv6?

Michael Klatsky

Are the limitations on instance types still in place, specifically regarding Cluster computes?

Andy

My first question was going to be "What about ipV6", but I see several others beat me to it.

Cloudcontroller

This is quite a block-bluster pack of features to unveil in one release. Especially excited about VPC with Internet and VPN access- at Cloud Controllers we have a client replicating their Windows file server to a failover Windows server on AWS. Replication takes place over a flaky Cisco VPN client for Windows. We had to do it this way simply because this server's function is high availability over the PUBLIC internet- should their office suffer catastrophic equipment failure or nature disaster occurs, they would access their files on this server through a webdav application. Now we can securely replicate their server by using the "VPC with Internet and VPN access" deployment model - we'll get a more reliable VPN connection between their on-premise router and VPC while still providing public internet access. Good times.

neal

can you provision a VPC on dedicated hardware or this is still multi-tenant?

GJG

Does Amazon EC2 support private line connections to/from a datacenter hosted by Terramark?

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30