5 ms·
this is why as a frontend developer. Im scared to deploy to aws. there so many things in the dashboard to get wrong if you don’t know what you’re doing. and I d
by jalino23 4y ago
this is why as a frontend developer. Im scared to deploy to aws. there so many things in the dashboard to get wrong if you don’t know what you’re doing. and I don’t know what I’m doing. I stick to digital ocean and netlify
- rectang 4y agoI agree. The AWS interfaces are poorly designed, difficult enough to use well that "mistakes" are statistically guaranteed to happen. It is laughable to hold those who make S3 buckets public accountable yet underplay the contribution of interface design. It's as if the NTSB had a report template with only a single checkbox for "pilot error".
- nfRfqX5n 4y agoS3 buckets are private by default. I'm pretty sure it warns you very heavily when making items public too.
- ghaff 4y agoYeah, AWS lets you do things--especially related to billing--that can really burn you if you make a mistake or don't know what you're doing. But making S3 buckets public is something they've really put guardrails on over time.
- djitz 4y agoI’ve always found the main issue is not how easily you can make a bucket public, it’s knowing how to utilize a private bucket to serve assets or media in the first place.
- evntdrvn 4y agoThey are now, but IIRC that was not previously the case.
- everfrustrated 4y agoS3 Buckets have _always_ been private by default.
- stef25 4y agoS3 buckets are now very clearly labelled as being public, perhaps even private by default. Not so long ago this wasn't the case and various grey hat services would let you explore public buckets via a nice interface / API. What you could find was pretty shocking. The idea of "don't use it if you don't know how" still applies though. In this world so many things can go wrong if you don't understand what button does what but that's not an excuse imho - AWS isn't designed for non technical people.
- mwint 4y agoThis used to be worse than it is now. Today there’s all kinds of warnings about buckets that can be publicly accessed. It takes quite a bit of work to make one public, not something you’d do without knowing anymore.
- ranman 4y ago1) I think your opinion here is 3-4 years out of date. Check out the modern interfaces. 2) at a bank's scale it should not be using the console for anything in production.
- rbanffy 4y agoBanks also use Excel and VBA macros for a lot of things that deeply scare me. It feels like the planet’s financial systems are kept together by spit and prayer.
- jhugo 4y agoNever ever use the dashboard to configure your production deployments, on any cloud. From the moment you create the account, use automation (Terraform, provider-specific stuff like CF, whatever) to create resources. The learning curve is not that big, and you will have certainty about, and control over, what is running in your account.
- polishdude20 4y agoDoes AWS have a way to export your infrastructure to a terraform file? Like if I start doing things via the dashboard and later want to use terraform?
- VWWHFSfQ 4y agoTerraform has the ability to import it
- 8organicbits 4y agoIn my experience you need to find each resource one by one, and then import each one. Sometimes by name, some by ARN, some by something else. The import approach is time consuming.
- _petronius 4y agoNo, but Terraform has a way of importing it (via the `terraform import` command), although it is clunky to use for an account with lots of resources. CloudFormation (the AWS-provided IaC product) may have something, though.
- jhugo 4y agoI saw "aws-prod-infrastructure" and "terragen" on the AWS blog recently, which are claimed to solve this. I haven't tried them.
- karmajunkie 4y agoI've used terraformer. It generates a bunch of HCL that's useful but verbose, and you can target certain kinds of resources with it. It'll do in a pinch but can't say I loved it.