21–30 of 42 posts
Earlier quoted context omitted.
If there's confusion about the concept of regions, it seems to be coming from Amazon themselves. They couldn't just call it the Ohio region?
Is that really an issue? Sometimes I get the number suffixes confused (like us-west-1 and us-west-2). Additionally, would you refer to the Sydney region or the New South Wales region?
FreeBSD 10.3-RELEASE ami-780a501d
FreeBSD 11.0-RELEASE ami-88154fed
Earlier quoted context omitted.
Clickable - https://www.google.com/maps/search/40.103706,%20-83.199873 - https://www.google.com/maps/search/40.061121,%20-83.134998 - https://www.google.com/maps/search/40.094640,%20-82.751469 All 3 points: https://www.google.com/maps/dir/40.103706,+-83.199873/40.061...
Zooming in with satellite view shows that all three sites seem to not only have identically sized/shaped buildings, but they're also oriented the same way (long axis running east/west). Any theories on why? Something to do with cooling perhaps?
[1] http://www.ase.org/resources/model-commercial-building-effic...
As someone who works with a fairly large EC2 infrastructure, I find the move towards EBS-only instance types somewhat alarming. For me, the main draw of EBS is to ensure data is retained in the case of instance failure, but it comes with significantly lower performance than instance-store SSDs and is more expensive. I've resisted EBS for the most part, and all of my servers are treated as disposable, but AWS is obvio…
Anyway! Provisioned IOPS are sufficient for most workloads; if they're not for yours, you might consider a ramdisk (expensive) or going bare metal on physical servers (cheap).
I really wish there was an API that allowed me to just get a list of all available regions including their descriptive names. As it stands, when AWS adds a region I have to make manual updates to update my systems. AWS has APIs for everything else, why not a comprehensive API for regions and their descriptive names? EDIT: for the downvoters - please specify exactly the REST API call that I make to get regions and the…
Interesting tidbit in the announcement: Data between the US-East-1 and US-East-2 regions is priced at the lower inter-AZ rate ($0.01 per GB, or half price). That's pretty great if you're looking to add a layer of regional redundancy.
But it's only a penny, right? How much could it matter? It actually matters a lot. At both my previous and current employers, a surprisingly large portion of our hill comes from data transfer across AZs. All the microservices, all the memcache hits, and all the database replication add up quickly.
As someone who works with a fairly large EC2 infrastructure, I find the move towards EBS-only instance types somewhat alarming. For me, the main draw of EBS is to ensure data is retained in the case of instance failure, but it comes with significantly lower performance than instance-store SSDs and is more expensive. I've resisted EBS for the most part, and all of my servers are treated as disposable, but AWS is obvio…
Also, complementing toomuchtodo's comment, there's also now EBS types focused on almost all kinds of workloads: sc1 for cold data/archiving, st1 for workloads optimized for sequential scans (a Confluent benchmark even reported that Kafka ran better with st1 EBS than instance storage), io1/PIOPS for databases and gp2 for everything else.
Anybody done a ping between EC2 instances in us-east-1 (N. Virginia) and us-east-2 (Ohio)? Curious to see what the latency is.