What would make AWS even better • Hacker News Board

Re: What would make AWS even better

#61

Post by philliphaydon » Sat, Sep 03, 2022, 9:15 AM UTC

paranoidrobot wrote: post #59

philliphaydon wrote: post #51

Earlier quoted context omitted.

I don’t think that’s right. You wouldn’t use 0.0.0.0/32 you would use the private subnet range so they have no direct access to the internet and use a nat gateway to give them access to the outside world but no inbound access. Edit: in the first example the servers should be in a private subnet. And not have a public ip allocated. They would require ssh hopping via a bastion or a vpn.

If your traffic is coming through a NLB, then the instances attached to the target group need to have 0.0.0.0/0 as the permitted source. (Assuming you want traffic from anywhere) If you dont believe me, try setting it up yourself. As for instances being on a private VPC/non-public IPs thats deployment specific. In any case, everything then complains about listening on strange ports with 0.0.0.0/0

I will try test it out this evening.

Re: What would make AWS even better

#62

Post by teilo » Sat, Sep 03, 2022, 2:46 PM UTC

At my company, I've seen too many developers trying to cram fairly complex Flask websites (providing business tools) into Lambda functions. They deploy, and then the users complain that the website, which used to be immediately available, now runs very slow, because every request is also initiating the Flask app from scratch. That's a ridiculous amount of overhead. Tools like this belong in ECS, not Lambda. Or rewrite as a SPA and use microservices. A classic case of hammer and screw.

Re: What would make AWS even better

#63

Post by mattbillenstein » Sat, Sep 03, 2022, 8:28 PM UTC

I feel like I'm the only engineer out there who just doesn't care for all the complexity of the modern cloud - like, I just run Ubuntu VMs on ec2, I don't use all the whizbang services, I just don't care.

And this model lets me be cloud agnostic for the most part - I run data workloads on gcp, dev/build workloads on linode, I've run bare metal in some places where I needed on-prem stuff. It's all just very much simpler than every cloud's flavor of doing everything slightly differently through different apis and tooling...

Re: What would make AWS even better

#64

Post by taf2 » Sat, Sep 03, 2022, 9:06 PM UTC

buscoquadnary wrote: post #34

taf2 wrote: post #31

IMO discounts would make aws better… the kind you get when you use more and can negotiate

Be an enterprise customer. Again AWS is great for small businesses just starting up that can make a lot of use of the free tier, and find the pay per use pricing attractive, and for massive corporations that only need one approved vendor that can service all their needs without going through the purchasing process again. It's the middle where you will get squeezed and not get a cost effective value without a dedicate…

how much does one need to spend to become an enterprise customer?

Re: What would make AWS even better

#65

Post by ManWith2Plans » Sun, Sep 04, 2022, 12:19 AM UTC

cbsmith wrote: post #47

rlayton2 wrote: post #33

Earlier quoted context omitted.

Total layer size is also restricted.

Restricted to 10GB . I'm sorry, but if you need more than that, you probably shouldn't be using Lambdas the way you are using Lambdas.

This isn't true. 10GB is the limit on docker backed lambda function sizes. Layers are capped to 256MB just like lambda functions.

A couple of weeks ago, I tried to deploy a lambda function that created Azure Subnets in python, and the Azure client was 265GB alone. My layer creation api call failed because of this.

Re: What would make AWS even better

#66

Post by philliphaydon » Sun, Sep 04, 2022, 3:47 AM UTC

philliphaydon wrote: post #61

paranoidrobot wrote: post #59

Earlier quoted context omitted.

If your traffic is coming through a NLB, then the instances attached to the target group need to have 0.0.0.0/0 as the permitted source. (Assuming you want traffic from anywhere) If you dont believe me, try setting it up yourself. As for instances being on a private VPC/non-public IPs thats deployment specific. In any case, everything then complains about listening on strange ports with 0.0.0.0/0

I will try test it out this evening.

I tried it out and I don’t know why but I feel like it’s complicated to me. Setting everything up with an application load balancer, public and private subnet’s and security groups all makes perfect sense. But the network load balancer makes me confused.

But adding it to my list of things to learn and understand better.

Re: What would make AWS even better

#67

Post by paranoidrobot » Sun, Sep 04, 2022, 8:46 AM UTC

philliphaydon wrote: post #66

philliphaydon wrote: post #61

Earlier quoted context omitted.

I will try test it out this evening.

I tried it out and I don’t know why but I feel like it’s complicated to me. Setting everything up with an application load balancer, public and private subnet’s and security groups all makes perfect sense. But the network load balancer makes me confused. But adding it to my list of things to learn and understand better.

> But the network load balancer makes me confused

yep, it just works differently from everything else.

Once you realise that, from a network traffic perspective, AWS wants you to pretend its just a magic straw delivering traffic from your source to your targets, and it's basically invisible to everything, then it started to click more for me.

That's why I want NLBs to support SGs. or at least a NLBv2 that does it.

Re: What would make AWS even better

#68

Post by robertlagrant » Sun, Sep 04, 2022, 4:30 PM UTC

Lucasoato wrote: post #6

robertlagrant wrote: post #2

Having just started with AWS, I would say: letting me make a Kubernetes cluster that doesn't require so many different cloud objects before it will start to function.

Poof: AWS Blueprint removes a lot of boilerplate code, pair it with terraform and that's it.

Poof?

Re: What would make AWS even better

#69

Post by leerob » Mon, Sep 05, 2022, 6:44 PM UTC

chrisweekly wrote: post #21

nowandlater wrote: post #8

For long running tasks I like to use CodeBuild, ECS Fargate (task) is also an option.

Pretty good experiences here with ECS Fargate for Dockerized Next.js runtime.

Glad to hear Next.js + Docker has been a smooth experience! Let me know if there's anything else we could do better.

Re: What would make AWS even better

#70

Post by cbsmith » Wed, Sep 07, 2022, 7:47 PM UTC

ManWith2Plans wrote: post #65

cbsmith wrote: post #47

Earlier quoted context omitted.

Restricted to 10GB . I'm sorry, but if you need more than that, you probably shouldn't be using Lambdas the way you are using Lambdas.

This isn't true. 10GB is the limit on docker backed lambda function sizes. Layers are capped to 256MB just like lambda functions. A couple of weeks ago, I tried to deploy a lambda function that created Azure Subnets in python, and the Azure client was 265GB alone. My layer creation api call failed because of this.

You're right. I forgot it was docker backed lambda rather than layers.

Out of curiosity, why didn't you use an Azure docker image to back your lambda function?