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

71–80 of 237 posts

Re: Troubles with the AWS web console

#71

Post by scarface74 »

baseballMan wrote: post #68
scarface74 wrote: post #46

Earlier quoted context omitted.

The only part of the console that I absolutely hate is dealing with the Parameter Store. But I hate everything else about the parameter store too so there is that. CodePipeline is pretty bad too. There is no way you can create a cross account code pipeline from the console.

CloudWatch log filters are pretty bad too. I basically just use ctrl + f now in cw logs to find what I'm looking for.

Oh yeah. They are horrible. I agree completely. For C#, I use Serilog for logging to both a Cloudwatch sink and a ElasticSearch sink. Before I’ve used a Mongo sink.

Re: Troubles with the AWS web console

#73

Post by drchewbacca »

stevekemp wrote: post #19
drchewbacca wrote: post #4

I hate AWS so much. I spent 3 hours trying to get a bucket to host a static single page of html and failed completely. I use amazon polly. I wanted to know how many characters I was using each month. I spent 2 hours searching through hundreds of pages and literally couldn't find that information. I thought of trying to start a little text to speech service for dyslexics to make it easy to use Polly but one of the mai…

Uploading a single file to S3 seems like it should be a simple job, that is well-documented: https://docs.aws.amazon.com/AmazonS3/latest/user-guide/uploa... There are parts of AWS that are hard to use, and non-intuitive. But S3 didn't ever seem to be one of them, though perhaps I'm forgetting how hard it was initially. You might consider a "friendly" system for static hosting if raw-S3 is too hard though, such as net…

Yeah I managed to get the file into the bucket. However I couldn't get the permissions to let it be publicly visible despite working through several tutorials.

I ended up on Netlify, it's 1000x more my speed.

Re: Troubles with the AWS web console

#74

Post by redhale »

mk89 wrote: post #9
drchewbacca wrote: post #4

I hate AWS so much. I spent 3 hours trying to get a bucket to host a static single page of html and failed completely. I use amazon polly. I wanted to know how many characters I was using each month. I spent 2 hours searching through hundreds of pages and literally couldn't find that information. I thought of trying to start a little text to speech service for dyslexics to make it easy to use Polly but one of the mai…

If you hate AWS so much, wait until you use Azure. Worst support ever. UI not in sync with the az-cli, documentation super chaotic, lots of basic features from AWS not yet supported in Azure. From my experience, AWS has up-to-date documentation pages for everything. And when something is hard to understand from their docs, you can find really everything you need by searching on Google. Literally, everything. And if y…

My experience is exactly inverse to yours. IMO Azure's documentation, in general, is far superior to AWS's. And my experience with Azure support has been stellar.

Re: Troubles with the AWS web console

#75

Post by jjoonathan »

mlthoughts2018 wrote: post #69
sdan wrote: post #57

Earlier quoted context omitted.

Agree. Having used both GCP and AWS, I like GCP's UI a lot more than AWS's huge dropdowns and constant usage of the search bar.

I have to disagree. After using AWS & GCP, I find AWS “stays out of my way” much much better and has much better documentation. There are weird corners of GCP, like GCS “interop” mode and lack of full compatibility with S3 APIs that feel basically like Google is using dark patterns. AWS is head & shoulders the better cloud provider. Google is just cheaper.

I love when AWS console stays out of my way so much that I have to pick through its backend HTTP requests in the browser developer tools to figure out why it isn't working even though the UI shows no errors or perhaps even reports success. This is a regular occurrence.

My absolute favorite is when AWS console stays out of my way in a particular manner that hides expensive resources, with bugs in the per-resource console, the cost explorer, and the notifications systems conspiring with each other to deliver a lovely surprise at the end of the month. It's amazing what bugs can do when they work together!

Re: Troubles with the AWS web console

#77

Post by nickjj »

llimllib wrote: post #50
nickjj wrote: post #26

On the other hand, their CLI tool is very good. I wrote some video training material 3 years ago that goes over setting up an ECS cluster and I decided to use the CLI for just about everything. We interact with a number of resources (S3, load balancers, EC2, ECS, ECR, RDS, Elasticache, etc.) and other than a single flag to login to ECR it all works the same today. I'm happy I chose not to use the web console. The onl…

Their CLI manages to completely lock up my up to date MacBook Pro when simply downloading files and has very strange and conflicting choices of parameters. It is comprehensive, but I wouldn’t call it good

I can't say I've had the same experience here on Windows using WSL. It runs like a champ. I've also used it within Debian based Docker images on many occasions.

Re: Troubles with the AWS web console

#78

Post by KaiserPro »

I know many people will disagree, but I really miss the VMware fat windows client. (vsphere 5, before they ruined it with the weird flash hybrid that didn't work properly)

That, was a paragon of design reliability and speed compared to the AWS console.

What annoys me the most is the sheer weight of each page. If you have to context change, its multiple seconds before the page is useable.

A classic example is lambda. I click on the function, page reloads (no problem) 1-2 seconds later the page is fully rendered, I can _then_ click on the monitoring tab, another couple of seconds, and then I can jump to the latest log, in cloudwatch.

Cloudwatch can get fucked. Everything about it is half arsed. Search? all of the speed of splunk, combined with its reliability, but none of the usefulness.

The standard answer is "you should use Cloudformation" I do, it too is distilled shart. (anything to do with ECS can cause a 3 hour, uninterruptible hang, followed by another timeout as it tries to roll back.)

It also lazy evaluates the acutal CF, which means that parameter validation happens 5 minute in. Good fucking job there kids.

What I really want is a QT app in the style of the VMware fat client (you know with an inbuilt remote EC2 console, that'd be great...) that talks to AWS. The GUI is desgined by the same team, and is _tested_ before a release by actual QAs who have the power to block things until the change is released.

Re: Troubles with the AWS web console

#79

Post by kristianpaul »

KaiserPro wrote: post #78

I know many people will disagree, but I really miss the VMware fat windows client. (vsphere 5, before they ruined it with the weird flash hybrid that didn't work properly) That, was a paragon of design reliability and speed compared to the AWS console. What annoys me the most is the sheer weight of each page. If you have to context change, its multiple seconds before the page is useable. A classic example is lambda.…

You know that nothing stops you from using aws apis and making you own UI right?

Re: Troubles with the AWS web console

#80

Post by pmart123 »

adreamingsoul wrote: post #44

These comments are fascinating to me. I was responsible for designing, leading, and building the frontend for an AWS service. One of the challenges was with obtaining useful feedback from a diverse range of people. During the product definition phase, the majority of the feedback, input, and feature priority was for customers who were planning to dedicate a large budget towards using said service. I often felt that s…

Interesting. I’ve always found it befuddling as a generalist with a relatively high learning curve. I gave it the benefit of the doubt until Google Cloud started rolling out its updates with far better documentation and interfaces. That said, AWS has way better customer support.
Post reply on HN