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

121–130 of 237 posts

Re: Troubles with the AWS web console

#121

Post by camtarn »

nkozyra wrote: post #107
afpx wrote: post #101

Earlier quoted context omitted.

Approximately how much does one have to spend per month to get prioritized feature improvements? We spend about $200k per month, and AWS treats us like we’re unimportant. I would like to try Azure or Google a try, but neither seem to make it easy to transfer Petabytes.

I wouldn't expect those services to offer you much more personal attention, honestly.

Amazon does have vendor and seller managers who are allocated to specific vendors/sellers. I'm surprised that for a $2.4M/year AWS customer (presumably with the highest support level) that they wouldn't have a similar setup. That said, having personal attention from a manager is definitely not the same as getting features actually built for you.

Re: Troubles with the AWS web console

#122

Post by SilasX »

One of my pet peeves about it (might have since been fixed) is that AWS will gladly walk you through the wizard to set up an EC2 server, and only at the very end say “oh you don’t have permission to do that lol”.

I compared it to a bartender who immediately recognizes that you’re underage but offers you alcoholic drinks, gives you samples, asks about preferences, counts out your change, and only after all of that stops you from drinking it.

http://blog.tyrannyofthemouse.com/2016/02/some-of-my-geeky-t...

Re: Troubles with the AWS web console

#123

Post by cloakandswagger »

drchewbacca wrote: post #73
stevekemp wrote: post #19

Earlier quoted context omitted.

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.

I've never used S3 to host a website before so I decided to try this and see if it's really that complicated.

First, I searched for "host static website on S3" and found an AWS docs page with a walkthrough.

Then, I created an S3 bucket through the console. I uploaded a "hello world" index.html file to it.

Then I went to Properties, checked "Use this bucket to host a website" and gave it the name of my index file. When I clicked Save, I had a hosted HTML file that I could navigate to.

I'm struggling to see how it could be simpler than that. What exact problems did you run into?

Re: Troubles with the AWS web console

#124

Post by org3432 »

Terretta wrote: post #65
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…

Noting your verb tense, “I was”, I’m assuming you’re no longer in that role. This isn’t feedback, just discussion. I talked to Jassy after his keynote in 2018: “Your message says AWS is for ‘builders’. Why do you keep saying ‘just click and ...’ instead of ‘just call the API and’?” In short, to your point: AWS is for builders... who pay. And right now all the growth is in enterprise, where we don’t know how to make A…

> In short, to your point: AWS is for builders... who pay. And right now all the growth is in enterprise, where we don’t know how to make API calls from a command line.

Infact AWS's HSM devices intentionally don't have an API, as "security feature."

Re: Troubles with the AWS web console

#125

Post by drchewbacca »

cloakandswagger wrote: post #123
drchewbacca wrote: post #73

Earlier quoted context omitted.

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.

I've never used S3 to host a website before so I decided to try this and see if it's really that complicated. First, I searched for "host static website on S3" and found an AWS docs page with a walkthrough. Then, I created an S3 bucket through the console. I uploaded a "hello world" index.html file to it. Then I went to Properties, checked "Use this bucket to host a website" and gave it the name of my index file. Whe…

So this was a while ago and I fully admit it might have been me being stupid.

However when I was doing it I don't think there was a "Use this bucket to host a website" button. Instead you had to give the bucket a special type of permissions which meant anyone could see the contents but no one could write to it. I kept following the guide as closely as I could but I couldn't get it to take.

Re: Troubles with the AWS web console

#126

Post by peter_retief »

Well I am glad I am not the only one who struggles to understand what is going on with AWS. Everyone is all over the place with cryptic howto's. I think I may have even "lost" a running container at some point. Google cloud also seems to be out to confuse people, maybe its a strategy to stop users from escaping :)

Re: Troubles with the AWS web console

#127

Post by peter_retief »

jrockway wrote: post #2

I am pretty sure the AWS business model is to get you to write your own code that interacts with the API so that when you think about switching to another provider, you realize that you're throwing away months of work and decide not to. They also make the API requests take so many parameters that are specific to your particular use case that nobody will ever be able to write a generic tool that does what you want. Ev…

That occured to me as well

Re: Troubles with the AWS web console

#128

Post by cloakandswagger »

drchewbacca wrote: post #125
cloakandswagger wrote: post #123

Earlier quoted context omitted.

I've never used S3 to host a website before so I decided to try this and see if it's really that complicated. First, I searched for "host static website on S3" and found an AWS docs page with a walkthrough. Then, I created an S3 bucket through the console. I uploaded a "hello world" index.html file to it. Then I went to Properties, checked "Use this bucket to host a website" and gave it the name of my index file. Whe…

So this was a while ago and I fully admit it might have been me being stupid. However when I was doing it I don't think there was a "Use this bucket to host a website" button. Instead you had to give the bucket a special type of permissions which meant anyone could see the contents but no one could write to it. I kept following the guide as closely as I could but I couldn't get it to take.

Maybe it's been updated since then. This is the guide I followed: https://docs.aws.amazon.com/AmazonS3/latest/dev/HostingWebsi...

Re: Troubles with the AWS web console

#129

Post by turtlebits »

Terretta wrote: post #65
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…

Noting your verb tense, “I was”, I’m assuming you’re no longer in that role. This isn’t feedback, just discussion. I talked to Jassy after his keynote in 2018: “Your message says AWS is for ‘builders’. Why do you keep saying ‘just click and ...’ instead of ‘just call the API and’?” In short, to your point: AWS is for builders... who pay. And right now all the growth is in enterprise, where we don’t know how to make A…

The AWS APIs documentation is excellent, I have no qualms with it, other than some inconsistencies in payloads/naming across services.

The console should be for exploration/discovery and if you're actually building production infrastucture by pointing and clicking, well, shame on you.

Re: Troubles with the AWS web console

#130

Post by the__prestige »

afpx wrote: post #101
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…

Approximately how much does one have to spend per month to get prioritized feature improvements? We spend about $200k per month, and AWS treats us like we’re unimportant. I would like to try Azure or Google a try, but neither seem to make it easy to transfer Petabytes.

Have you tried databox? You can send up 80 TB in one shot. https://docs.microsoft.com/en-us/azure/databox/data-box-over...
Post reply on HN