Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Boilerplate

github.com

Post reply on HN
Print view View original

21–30 of 62 posts

Re: AWS Boilerplate

#21

Post by benreesman »

flyinprogrammer wrote: post #8

I'm curious to see if they improve upon the Rube Goldberg machine that is validating PRs with CodeBuild's lack of support for branches in 2020: https://aws.amazon.com/blogs/devops/validating-aws-codecommi...

To the best of my knowledge most of the big shops are using “master ships everywhere, in-progress stuff is behind feature flags”.

There are pros/cons to this of course, but if you’re doing any A/B testing or bandit optimization you’re kind of stuck with it in one form or another. If you’re not doing any A/B or bandit then it’s probably a young enough project that you can do whatever you want.

Re: AWS Boilerplate

#23

Post by sunilkumarc »

Nice. This boilerplate can really help people get started quickly. Well done :)

On a different note, recently I was looking to learn AWS concepts through online courses. After so much of research I finally found this e-book on Gumroad which is written by Daniel Vassallo who has worked in AWS team for 10+ years. I found this e-book very helpful as a beginner.

This book covers most of the topics that you need to learn to get started:

If someone is interested, here is the link :)

https://gumroad.com/a/238777459/MsVlG

Re: AWS Boilerplate

#24

Post by nixgeek »

Initial reaction to seeing HN showing me “AWS Boilerplate (github.com)” was I thought AWS had launched a new service and it was potentially open source.

Please consider renaming to something like ‘Boilerplate for AWS’ since it would avoid confusion that this is something official from AWS, and because such a name is less likely to cause trademark issues per the AWS Trademark Guidelines.

https://aws.amazon.com/trademark-guidelines/

Re: AWS Boilerplate

#25

Post by whalesalad »

nixgeek wrote: post #24

Initial reaction to seeing HN showing me “AWS Boilerplate (github.com)” was I thought AWS had launched a new service and it was potentially open source. Please consider renaming to something like ‘Boilerplate for AWS’ since it would avoid confusion that this is something official from AWS, and because such a name is less likely to cause trademark issues per the AWS Trademark Guidelines. https://aws.amazon.com/tradema…

Yeah, my first thought was oh shit Amplify has been replaced here we go again.

Re: AWS Boilerplate

#26

Post by whalesalad »

williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

For folks who want a tool to help them accomplish this, I have heard good things about cookiecutter: https://github.com/cookiecutter/cookiecutter

Re: AWS Boilerplate

#27

Post by whalesalad »

jlj wrote: post #22

AWS Amplify is in a similar space. It supports several frameworks and the development workflows and infrastructure management are built in to the project. https://aws.amazon.com/amplify/

I urge fellow readers to try and plan out your entire app arch on Amplify before committing to it.

I have found it to be a pain in the ass because it tends to want to do everything for you leaving assets/buckets/things like `aws-amplify-23094139-85-3981759387593745983475-us-east-experiment-project` all over your account. I have been using AWS for over 10 years, so I tend to like to keep a clean house and name most of my things, or at least have them follow a sane convention. I also like to know what is being created.

Oh and the dev/stage/prod branching strategy is a nightmare.

Re: AWS Boilerplate

#29

Post by cactus2093 »

I'm not really sure who this is for. It seems quite complex and opaque, for anyone who is well versed in AWS infrastructure I think you'll spend more time untangling this tool and trying to extend it beyond the exact use cases the author thought of than it would take you to set an app up yourself using your preferred config management toolchain.

For anyone not very familiar with AWS infrastructure, this is a very direct path to being in way over your head with a bunch of infrastructure you have no idea how to manage once it's set up. You'd surely be better off using a more managed setup like Heroku, or taking the time to read some AWS tutorials and set up only the things that you need, making sure you understand the different pieces along the way.

It makes me think of the Standards XKCD [0], I'm sure this project started out with good intentions thinking that "working with AWS SDKs is too complex, we'll make a few simplified make command to rule them all" but all they've managed to do is make yet another, extremely limited, but still opaque and complex tool.

[0] https://xkcd.com/927/

Re: AWS Boilerplate

#30

Post by fludlight »

freehunter wrote: post #18
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

This is why I love opinionated frameworks, why I love hand-holding tutorials, why I love abstractions. I don’t like code. I don’t like writing it, I don’t like reading it, I don’t like thinking about it. A mechanic doesn’t love his crescent wrench, he loves working on engines. The wrench is just a tool. What I enjoy is the final product and seeing a project come together as time goes on. “The right tool for the job”…

I feel the same way about rust’s standard lib, which is pretty sparse compared to, say, python and go. Finding libraries for common tasks is the most stressful part of an otherwise stress-free language (first world problems, I know). I get that it’s a trade off, and I get why the designers chose this path, but I would have preferred it the other way.
Post reply on HN