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

Troubles with the AWS web console

old.reddit.com

Post reply on HN
Print view View original

231–237 of 237 posts

Re: Troubles with the AWS web console

#231

Post by omni »

cthalupa wrote: post #229
omni wrote: post #228

Earlier quoted context omitted.

A management UI showing me stale data sounds like a terrible experience, honestly

It works well enough for Netflix - https://medium.com/netflix-techblog/edda-learn-the-stories-o... - and Target ( https://tech.target.com/2017/04/07/how-and-why-we-moved-to-s... ) :). I've only ever used Edda as part of a Spinnaker setup, but there's no reason it couldn't be used with something else, or the same idea in general reused. You don't have to cache it for very long, but you get two benefits here: Being abl…

Just wanted to say thanks for replying with these links!

Re: Troubles with the AWS web console

#232

Post by com2kid »

scarface74 wrote: post #222
com2kid wrote: post #221

Earlier quoted context omitted.

I had never done any back end work before. In less than 2 hours I had auth'd https rest endpoints up and running with logging. Deploying new endpoints is as easy as exporting a function in my code and typing deploy on the command line. This isn't after some sort of complex configuration, it is after creating a new project via 1 cli command that asks for the project name and not much else! Google's cloud stuff, especi…

And you could do the same thing with lambda/DynamoDB/API Gateway just as easily by using one of the wizards. What you can do as a hobby project is much different than the parent poster who was trying to deploy an enterprise grade setup with an existing legacy infrastructure. How would you know if GCP is easy based on your limited experience? Not trying to sound harsh, as well as I know AWS, I would be completely loss…

I can't really explain how easy it is. There are no hidden charges, monthly usage is easy and clear to understand. For small to medium sized apps there isn't even any configuration. I'll be throwing tens of thousands of users, tiny I know, on a service that had 0 configuration done beyond typing its name. In fact I'm 100% sure my VMs on DO are going to give under load first.

To put it another way, there is a healthy industry of people whose sole job is to come in and figure out why AWS is billing too much.

FWIW I showed one of my friends at Amazon how easily I can create and deploy serverless code on Firebase, he admitted it is far easier than what AWS offers.

The downside of this is that options are fewer. If I want a beefier VM my choices are limited, and the way pooling and VM reuse is done is well documented and not at all under my control. It is like cloud on training wheels (TBF to gcp it is possible to opt-in to more complexity for many services, but the serverless function stuff is pretty bare bones on options, arguably as it should be)

But take auth for example. Firebase auth is amazing. Using it is beyond simple, and within the Google ecosystem everything just works so well.

Re: Troubles with the AWS web console

#233

Post by scarface74 »

com2kid wrote: post #232
scarface74 wrote: post #222

Earlier quoted context omitted.

And you could do the same thing with lambda/DynamoDB/API Gateway just as easily by using one of the wizards. What you can do as a hobby project is much different than the parent poster who was trying to deploy an enterprise grade setup with an existing legacy infrastructure. How would you know if GCP is easy based on your limited experience? Not trying to sound harsh, as well as I know AWS, I would be completely loss…

I can't really explain how easy it is. There are no hidden charges, monthly usage is easy and clear to understand. For small to medium sized apps there isn't even any configuration. I'll be throwing tens of thousands of users, tiny I know, on a service that had 0 configuration done beyond typing its name. In fact I'm 100% sure my VMs on DO are going to give under load first. To put it another way, there is a healthy…

Guess what? Do you really think that there aren’t GCP consultants for any serious development?

Lambda, cognito, api Gateway and DynamoDB is dead simple.

You’re not doing anything complicated. Just because you can set up a little hobby project doesn’t mean it would be any simpler for a real enterprise app.

The number of users as long as the Serverless offerings from cloud providers has everything you need isn’t complicated based on the number of users. All Serverless offerings are optimized for this.

There are also WordPress consultants, does that mean that Wordpress is complicated or that there are people without the capacity (time not intelligence) to learn it.

You don’t have to “explain” how easy it is. The Node tutorial I use to learn it used Firebase.

Re: Troubles with the AWS web console

#234

Post by ppod »

journalctl wrote: post #109
ppod wrote: post #52

I'm a solo academic researcher user and there's one thing even simpler than this that i can't stand: there is no way to check which EC2 resources are running all at once. You have to click on every single region in turn to see what is actually running. If you've had multiple types running across regions, trying shut everything down without closing the account is a real pain. I am not the only person with this problem…

Out of curiosity, why are you running multiple EC2 instances across more than two regions?

Honestly, because when I started I didn't understand AWS very well, which was my fault. But it definitely ended up costing me more money than I expected.

Re: Troubles with the AWS web console

#235

Post by pmart123 »

cameronbrown wrote: post #133
jrochkind1 wrote: post #106

Earlier quoted context omitted.

I bet GCS docs will not keep up with changes to GCS very well either, judging by other Google docs. Start out good, don't keep up with changes. AWS docs are relatively good at keeping up with changes.

Google's docs are the most inconsistent. The newer the service the better the documentation in my experience. The App Engine docs are like a rats nest, but the Firestore docs are really well done.

My guess is they now care a lot more about Google Cloud than previous product endeavors. I’d also guess that people at Google would put in a ton of effort on documentation to avoid having to speak to people on the phone.

Re: Troubles with the AWS web console

#236

Post by Can_Not »

makebelieve wrote: post #103
m0xte wrote: post #33

Earlier quoted context omitted.

For me that isn't the problem. It's mapping the several-thousand acronym riddled hairballs into reality. The reality matches no other reality which means the knowledge is probably useless in 20 years time, much as the knowledge I had of proprietary stuff then is useless now. My head has only a certain amount of space and motivation for ephemeral complexity hairballs like AWS. At this point I have to wonder if this is…

I second this. I found it easier to spin up servers on other services and run big install scripts than to try do decode Amazon's naming/acronym hell. The requirement to connect invented names to computational activity is big overhead. I guess each AWS service get's named it's own thing as it is developed and those names just stick forever. it is maddening. Reading the docs outloud often sounds like a weird technical…

It feels like they're trying to vendor lock your vocabulary.

Re: Troubles with the AWS web console

#237

Post by Can_Not »

whitepoplar wrote: post #96
aytekin wrote: post #83

Here is a startup idea for grabbing: Make a better interface for AWS/Google Cloud. Since their APIs covers everything this should be possible. Be the first UXaaS. A killer feature: a server by server breakdown of Google Cloud expenses. It is impossible to understand what you are paying for on Google Cloud. They lump everything together in an incredibly confusing bill.

I think that's why DigitalOcean is winning so much these days.

Imagine if DO had lambda.
Post reply on HN