http://kindlund.wordpress.com/2007/11/19/configuring-multiple-default-routes-in-linux/ Notes on how to get sane traffic flows for a linux box that has 2 network cards connected to the same network. NOTE: this is a required setup if you are using multiple network cards feature on AWS VPC
http://kindlund.wordpress.com/2007/11/19/configuring-multiple-default-routes-in-linux/ Notes on how to get sane traffic flows for a linux box that has 2 network cards connected to the same network. NOTE: this is a required setup if you are using multiple network cards feature on AWS VPC
http://kindlund.wordpress.com/2007/11/19/configuring-multiple-default-routes-in-linux/ Notes on how to get sane traffic flows for a linux box that has 2 network cards connected to the same network. NOTE: this is a required setup if you are using multiple network cards feature on AWS VPC
http://aws.amazon.com/security/penetration-testing/
http://aws.amazon.com/security/penetration-testing/ read this if you need to conduct pen and security testing on / from EC2 instances
http://openfoo.org/blog/amazon_ec2_underlying_architecture.html Some description of EC2 Internals. EC2s are XEN VMs, mine is currently using Xen 3.0.3-rc5-8.1.14.f , which appears to be F14 Xen package re-build on RHEl5.x (this is by looking at compiler version) . Some info in the article appears to a bit outdated
http://aws.amazon.com/message/65648/ Postmortem for the April-2011 EC2/EBS outage. It looks like a human errors plus unfortunate cascade of events lead to a requests storm that brought down EBS storage. Also, it appears that Amazon mis-estimated spare storage capacity needed for recovery from such events.
http://www.slideshare.net/adrianco/netflix-in-the-cloud-2011 Slides from Adrian Cockcorft, Netflix director of cloud systems about current state [for 2011] of Netflix’s AWS-based architecture
http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html Notes from netflix tech blog about some key points of their EC2-based infrastructure design. Note that netflix is not affected by the current EBS problems in AWS US-EAST region. Their key point seems to be to equally split your infrastructure between 3 AZs (availability zones) and run at ~30% capacity, so if 2 AZs fail (as we have now) you would still running in one AZ @ 90%
http://ec2disabled.com/ The subj. looks really bad!