IMO discounts would make aws better… the kind you get when you use more and can negotiate
What would make AWS even better
31–40 of 70 posts
Re: What would make AWS even better
#32We have a process where we strip out the text of PDFs and shove in to elastic. The lambda starts by counting the pages and if it’s 250 or less it handles the job. If it’s larger than that we make the lambda kick the job to a temp ec2 instance which takes over the job. Our cutoff is around 250 pages but it’s highly dependent on text density. It would be great if the lambda could handle running long. Id probably even b…
Use a step function and run a parallel task?
Re: What would make AWS even better
#33Re: What would make AWS even better
#34IMO 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 dedicated AWS guy or two.
Re: What would make AWS even better
#35We have a process where we strip out the text of PDFs and shove in to elastic. The lambda starts by counting the pages and if it’s 250 or less it handles the job. If it’s larger than that we make the lambda kick the job to a temp ec2 instance which takes over the job. Our cutoff is around 250 pages but it’s highly dependent on text density. It would be great if the lambda could handle running long. Id probably even b…
Since Lambda is just one of at least three ways to “launch a Firecracker task to do something”, I choose the right one.
For something like that, I would use CodeBuild. In essence all CodeBuild is a method to run a list of bash commands in a Linux Docker container.
Standard disclaimer: I work at AWS in Professional Services.
Re: What would make AWS even better
#36Completely scrap Cloudformation and CDK and come up with something that requires /less/ code - not more, and has resource changes applied in parallel where possible. CFn is pretty garage - CDK just makes it more complex.
Re: What would make AWS even better
#37Everyone complains about the 15 minutes problem on lambda, but am I the only that have a problem with the 250MB deployment size limit?
You can use Lambda to run Docker containers of sizes up to 10GB
https://aws.amazon.com/blogs/aws/new-for-aws-lambda-containe...
Re: What would make AWS even better
#38Make it possible to set actual cost limits, not alarms.
But then you wouldn't have the constant white knuckle anxiety that you could run up a five figure bill in 30mins by accidentally misconfiguring your infra deployment.
Re: What would make AWS even better
#39Long running lambda functions are called AWS Batch. It’s a relatively unknown service but pretty decent if you need something like a GPU or long running jobs and can tolerate a 90 second cold start.
exactly this.
we even made an interface in code that runs a given task on a lambda (backed by a docker image) or batch (backed by the same docker image) depending on cpu/mem/time constraints. the tasks themselves also send a message when they're done so you can just subscribe to that vs. long polling.
Re: What would make AWS even better
#40Make it possible to set actual cost limits, not alarms.
But then you wouldn't have the constant white knuckle anxiety that you could run up a five figure bill in 30mins by accidentally misconfiguring your infra deployment.
Don’t worry! You would replace that with a new white knuckle anxiety that misconfiguring your infra deployment would exhaust your four figure cost limit, causing AWS to helpfully shutdown ALL of your infra to avoid any accidental overspend.