31–40 of 133 posts
The "use IAM roles for EC2" recommendation is a bit sketchy. The current security zeitgeist, not just after Colin's post but also after DerbyCon and Black Hat, is that EC2 roles are dangerous and, when under attack, not very predictable.
I still don't get why Opsworks is not getting more love? I guess people don't like Chef? Opsworks has enabled hassle free deployments for us over the past three years or so at no additional cost. :)
I've a few questions for AWS experts :
The only container orchestration that is open source seems to be Kubernetes. Is it easy to run on AWS?
What's the equivalent of Azure "Service Fabric" in the AWS world? (and in the Google Cloud?)
Does anyone here use x1.32xlarge instances? If so what kind of stuff are you doing with it? That thing looks beastly
The special sub-category of those are huge RDBMS instances - a pretty common choke point in growing companies with weaker engineering teams. Some of those companies would pay basically any price to keep those DBs running.
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 you should use Google Cloud, times you should use bare metal, times you should use Heroku. AWS is a complex beast. Heroku is simple, but has limitations.
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.
Also, if you're looking to the future, the AWS Lambda and Google Functions stuff is perhaps the most exciting stuff to start building knowledge up of now if you're a developer, I think.
WHY: Google still doesn't handle anchor-links very well. You have 1000 amazing articles on a single page. Each section (e.g.: "High Availability on AWS") would be a great resource for someone searching on that topic in Google. But when you put it all on one page Google infers "1/1000th of this page is about high availability on AWS" and gives better rankings to a page that is 100% about high availability on AWS.
I'm sure it would be pretty simple to write a script that breaks up topics into individual pages. I love the style of having it all on one page but I think it would be a waste of your hard work not to get all this great writing in front of search.
Does anyone here use x1.32xlarge instances? If so what kind of stuff are you doing with it? That thing looks beastly
Earlier quoted context omitted.
Do you have links to the DerbyCon and Black Hat talks? And could you clarify what "when under attack, not very predictable" means?
An attacker who compromises an EC2 instance can quietly grab the instance role credential and use it even after losing access to the instance itself.