This is so needed. I find Amazon's official documentation to be way too full of buzzwords and marketing speak. I just want someone to tell me what the thing does!
Open Guide to Amazon Web Services
91–100 of 133 posts
Re: Open Guide to Amazon Web Services
#92Earlier quoted context omitted.
Dynamo for the backend and ElasticCache (Redis) for some cache
Know of any good resources, links, etc for dynamo or going to figure it out as you go?
I had tried a lot of databases (postgres, mongo, couch and very recently Rethink) before trying out Dynamo. So I just jumped in, and started something basic, and read tutorials as I went along.
There's still a lot of stuff I don't fully know about (for about Read / Write volumes that is set - I left it at a default of 5) but I guess, I'll learn as I go along.
Re: Open Guide to Amazon Web Services
#93Wish there was more information about Elastic beanstalk - it always confuses me about how it works..
I've had the impression that elastic beanstalk (which I use) has suffered the fate of a few other Aws offerings in has been seen as less trendy than Docker/ECS. (See also: cloud search vs elasticsearch). But EB can do some things very well and very painlessly.
EB tends to work very well when you're requirements fit within its framework - and very badly when you try to do anything differently. We've moved to CodeDeploy because: EB was slow to deploy; often left applications in an 'unknown' state after deployment; ties application configuration to deployment; and generally felt fairly restrictive.
Re: Open Guide to Amazon Web Services
#94This is great. I've been working on AWS for close to 10 years now and an open guide is something I both need and want to contribute to. Many of us have simple goals on AWS. The official AWS docs are thorough, but are too technical. There are blog posts about anything, they can be hard to find or get out of date. I hope this open guide helps us all get our jobs done faster and easier!
I am relatively new to building larger apps. I've worked for a coulple years building with Drupal and hacking PHP. Now I only want to develope full stack JavaScript. I really enjoy it's messy nature. Last week I discovered that user uploaded files are not persistent on a Heroku hosted app. To solve that problem, I created an AWS S3 account which is the first time I've used AWS. I quickly figured out to exchange Node.js fs functions with the AWS SDK. Setting up a bucket and a test bucket easy. And, configuring IAM rules is intuitive.
You're right. Their docs are far beyond the scope of what I needed to get started. Interestingly, I would rather have Google searches about AWS show Stack Exchange answers but most of the first results are all Amazon documentation which is far more difficult to read and sort.
Re: Open Guide to Amazon Web Services
#95A 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…
Any advice on quickly learning when the different options you described are appropriate?
Re: Open Guide to Amazon Web Services
#96I would add as a VPC gotcha the use of the EIP_Disable_SrcDestCheck flag [1] to enable layer 2 capabilities. This is a feature that is only present in AWS. Neither Google Cloud Engine nor Microsoft Azure have it. So, if you craft an Ethernet packet modifying the destination address but not the destination IP in your local subnet, the packet will be sent to the computer by IP and not by MAC address as you expect in an Ethernet network.
[1] https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_N...
Re: Open Guide to Amazon Web Services
#97I 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. :)
Yep, not sure where this perception of "nobody's using it" comes from but I have been using it in 2 different companies in the last 3 years as well with nothing but love. In fact, if it were the case that "nobody's using it for good reasons", maybe we should ought to know the reasons?
Those of use contributing on the Guide so far have generally been companies where it's not used. I'd love to see a contribution (a few bullet points and/or links) that better covers the basics and reflects how/when it's useful.
Re: Open Guide to Amazon Web Services
#98Earlier quoted context omitted.
Yep, not sure where this perception of "nobody's using it" comes from but I have been using it in 2 different companies in the last 3 years as well with nothing but love. In fact, if it were the case that "nobody's using it for good reasons", maybe we should ought to know the reasons?
Those of use contributing on the Guide so far have generally been companies where it's not used. I'd love to see a contribution (a few bullet points and/or links) that better covers the basics and reflects how/when it's useful.
Re: Open Guide to Amazon Web Services
#99I 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. :)
Please write an update and submit a PR. I'm moving from Ansible to Chef and would love some real world advice on what Opsworks has to offer me without another dreaded POC. It's likely the original authors aren't using Chef or just use Chef server as I do now.
Yes, true. At the moment we don't have any OpsWorks expert contributors. Hope one of you can change that! https://github.com/open-guides/og-aws/issues/123
Re: Open Guide to Amazon Web Services
#100This is fantastic! Nice work.