Nice work but seriously can you please avoid using acronyms?!? You have plenty of space to write
Simple Storage Service
Rather than making me scroll down to find out what KMS stands for!
Cheers
Open Guide to Amazon Web Services
121–130 of 133 posts
Re: Open Guide to Amazon Web Services
#122A good edition, but I wish there was a place for horror stories about this tech. For instance, we can't launch or than 4 or 5 containers a second on our ecs clusters.
Are you measuring by placement, by container is running, or by container is fully initialized?
Re: Open Guide to Amazon Web Services
#123Does anyone here use x1.32xlarge instances? If so what kind of stuff are you doing with it? That thing looks beastly
applied ML research here also -- a lot of interactive (but highly parallelizable) modeling, graphing. Using medium-size data sets around 3-4GB in ram, by the time you forked it a few times, you easily end up beyond the m4.10xlarge or c4.8xlarge limits.
IMO theres an awkward space between small data and big data where it isn't really worth spending a long time to treat it like a real "big data" problem, and the x1 instance gives you an easy-out.
Re: Open Guide to Amazon Web Services
#124> A single EBS volume allows 10k IOPS max. To get the maximum performance out of an EBS volume, it has to be of a maximum size and attached to an EBS-optimized EC2 instance. Out of date; EBS volumes can be up to 20k IOPS per volume and what is "maximum size"? To get the maximum performance out of a volume depends on workload, the instance size you've attached it to (rather than EBS Optimization) and the number of IOP…
Any IOP on EBS is measured in 16kb granularity. Not the same as block size but helpful to know because it lets you set your read ahead and other values to not lower than 16kb. At least this was the case for many years. Trying to find the official docs now.
Re: Open Guide to Amazon Web Services
#125> A single EBS volume allows 10k IOPS max. To get the maximum performance out of an EBS volume, it has to be of a maximum size and attached to an EBS-optimized EC2 instance. Out of date; EBS volumes can be up to 20k IOPS per volume and what is "maximum size"? To get the maximum performance out of a volume depends on workload, the instance size you've attached it to (rather than EBS Optimization) and the number of IOP…
Might be more helpful to make a PR, rather than comment here. It'll take about the same amount of time.
Re: Open Guide to Amazon Web Services
#126A 15-minute scan read of this - specifically the sections on the stuff I've worked with the most - suggests this is a very, very good addition to the official documentation. I would as a minimum recommend anybody/everybody considering AWS to read and think about the "When to use AWS" section. Whilst it is an excellent set of tools that have completely changed the economics of deploying software, there are times when…
> There are a bunch of apps I'm thinking about building at the moment where I realise a hybrid approach is best: some of GCP's stack, some of AWS', and a small amount of my own bare metal. Knowing when to choose which is not intuitive and comes with time, but there are big, big clues that will help the uninitiated in that section of this open guide. unless you have a metric shitton of money to blow, there's never a g…
uh.... i use similar approaches. they cost a few dollars a month.
you're a metric shitton of idiot.
Re: Open Guide to Amazon Web Services
#127Wow, the link to http://www.ec2instances.info/ alone is so helpful. I wish I'd had this set of resources a year ago when I spent weeks trying to understand AWS' own documentation.
I will also add https://www.cloudorado.com/ for those who want to also compare against other clouds.
Great link; i wish i had this years ago! Thx for this contribution!
Re: Open Guide to Amazon Web Services
#128Although I'm familiar (high-level only) with numerous topics/services related to AWS, I'm still doing things the legacy way on providers like Digital Ocean (which I'm 100% happy with), and by no means a guru of AWS...So this guide looks awesome for someone like me!
Kudos to the authors and contributors!
Re: Open Guide to Amazon Web Services
#129Earlier quoted context omitted.
Been using opsworks for about a year now and while it has very significantly streamlined our provisioning/deployment tasks, "nothing but love" is not quite how I'd describe it. It does have some warts.
Biggest wart we have is that it randomly picks a machine to run migrations on, if it's a deploy with migrations.
I actually solved this with our custom deploy script. We choose the machine that runs the migrations.
The necessity of building and maintaining a custom deploy script is the biggest wart for us (though I admit that the API is pretty good, and said script has not had that much maintenance overhead).
Re: Open Guide to Amazon Web Services
#130Earlier quoted context omitted.
Right? I wish Amazon were just running a page like that themselves.
Which aspect of it do you find the most useful? * All of the instance types on one page? * All of the per-type facts in one row? * Sorting? Let me know and I will share it with the team.
If you want to answer the question "What's the cheapest way to get 16gb of ram and 4 cores?" (or the same for a 1 year term) then having a list you can filter and sort is much more helpful than Amazon's pricing pages.