What would make AWS even better
41–50 of 70 posts
Re: What would make AWS even better
#42We 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
#43What about, "treat AWS workers better"? Pay your people for their on call hours! Let them work on side projects and games in their spare time! Give them more than seven paid holidays. Give them more than two weeks vacation! Only six weeks of paid parental leave? I would absolutely be willing to pay more for AWS if I knew that amount was going to treating the poor folks who built it all better.
15 PTO days. 6 personal days
Yes I work at AWS. I’m never on call and I haven’t worked for more than 40 hours unless I’m learning something new trying to figure out. I control my own calendar and I manage expectations for my projects.
I do work in ProServe though…
Re: What would make AWS even better
#44What about, "treat AWS workers better"? Pay your people for their on call hours! Let them work on side projects and games in their spare time! Give them more than seven paid holidays. Give them more than two weeks vacation! Only six weeks of paid parental leave? I would absolutely be willing to pay more for AWS if I knew that amount was going to treating the poor folks who built it all better.
I used to work in one of the DB services and we used to get 20+ pages (sev2) every day. Due to insane amount of pages every day, we used to have daily on-call rotations.
Re: What would make AWS even better
#45Earlier quoted context omitted.
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.
Thanks for this! I’m not sure I would have looked at CodeBuild
You can run and rest CodeBuild locally. Just download the Docker image and run the shell script.
https://docs.aws.amazon.com/codebuild/latest/userguide/use-c...
Re: What would make AWS even better
#46Earlier quoted context omitted.
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.
Re: What would make AWS even better
#47Re: What would make AWS even better
#48What about, "treat AWS workers better"? Pay your people for their on call hours! Let them work on side projects and games in their spare time! Give them more than seven paid holidays. Give them more than two weeks vacation! Only six weeks of paid parental leave? I would absolutely be willing to pay more for AWS if I knew that amount was going to treating the poor folks who built it all better.
https://www.amazon.jobs/en/landing_pages/pto-overview-us 15 PTO days. 6 personal days Yes I work at AWS. I’m never on call and I haven’t worked for more than 40 hours unless I’m learning something new trying to figure out. I control my own calendar and I manage expectations for my projects. I do work in ProServe though…
Re: What would make AWS even better
#49Completely 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
#50Lambda is insanely expensive is why they don’t allow long-running jobs. A 1GB allocation is $43/mo. And most lambda users are running 1 single task/process per lambda invocation.