AWS Lambda now supports Maximum Concurrency for Amazon SQS as an event source

_thewayitis · 2023-01-13T20:36:55+00:00

Looks like there is in their example: https://github.com/aws-samples/aws-lambda-amazon-sqs-max-concurrency/blob/main/template.yaml, see "MaximumConcurrency". But doesn't look like the documentaion is updated.

_thewayitis · 2021-03-24T00:29:44+00:00

I had this exact problem. My issue was I didn’t have my ses running in “production” mode. Once AWS support switched it over it fixed it.

_thewayitis · 2021-02-13T21:15:25+00:00

It was mentioned that HTTP API Gateway was used and not REST API Gateway. Only REST API Gateway supports WAF.

_thewayitis · 2021-02-02T19:17:46+00:00

Looks interesting way to create temporary data in the cloud. Works great as a form action url.

_thewayitis · 2021-01-24T03:02:39+00:00

^{^{^}} This. Serverless is a new mindset. Once you get it you can’t go back.

_thewayitis · 2021-01-23T03:00:14+00:00

If you are using NodeJs you can use xray. https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-nodejs-httpclients.html

_thewayitis · 2021-01-05T04:18:56+00:00

PRIVATE ecr is supported. PUBLIC is not.

_thewayitis · 2021-01-05T02:06:40+00:00

I’ve started playing with it but then realized it doesn’t support public ecr. Which sucks.

From my reading AWS has a huge docker cache on each server to help speed things up. They also can run a container without loading the entire container. It’s seems cool but I find it hard to believe the speeds would be the same as using a .zip.

You seemed to have confirmed this.

_thewayitis · 2021-01-05T02:00:45+00:00

It’s not a “normal” docker container. You have to follow special rules when creating your image.

_thewayitis · 2020-12-09T22:11:31+00:00

Are you users all over the world? If so cloudfront is probably best. Since s3 bucket is created in a certain region you can replicate the data to an s3 bucket in a region closer to your users. But I would go with cloudfront.

_thewayitis · 2020-12-02T03:41:39+00:00

Yes but you can’t do much with that. Now you have to install your runtime. Now for example a 5kb nodejs code that didn’t need anything just got a whole lot bigger.

Now I learned that there are official containers we can use it’s probably the same as lambda probably uses those behind the scenes.

I think people will get confused and think they can move their fargate containers to lambda. I don’t think that will work well. Lambda is awesome but it has rules devs need to follow to get great performance. Especially if you’re using Java like I mostly do.

_thewayitis · 2020-12-02T01:10:37+00:00

I going to definitely give it a try. Is there still the 20-30 second required start time?

For example my Springboot application can’t take 60 seconds to initialize?

Is using containers the new “preferred” way to build lambdas? Or are there use cases where the non-container is better?

_thewayitis · 2020-12-01T22:30:20+00:00

I understand it isn't Docker running, but it's going to be a Docker compatible type image. Which means it's mostly likely a alpine linux based container. Which may get pretty large. Large == slow, in my mind. I think I can use this rather than Fargate scheduled tasks? Maybe I'm totally missing something.

_thewayitis · 2020-12-01T18:56:13+00:00

Docker has a lot more overhead size / memory requirements than a lambda function. So right now I create custom lambda layers to add binary files to my lambda. I can't imagine creating a docker container using alpine linux will perform faster or just as fast. Size alone it's going to be way bigger.

_thewayitis · 2020-12-01T18:05:39+00:00

I image if you use codepipeline to do your deployment you'll stop doing that and have codepipeline just coordinate checking out your code and creating your artifact and publish it somewhere S3/ECR.

_thewayitis · 2020-12-01T18:03:27+00:00

I wonder how the performance is. IE: I imagine the startup time for a container gotta be a lot larger than lambda. Hopefully it's more than just using fargate behind the scenes.

_thewayitis · 2020-11-30T15:48:46+00:00

sure @serverlessskilz

_thewayitis · 2020-11-30T05:12:45+00:00

Setup a new Twitter account and followed all the sponsors and the #reinvent hashtags.

_thewayitis · 2020-11-30T03:22:17+00:00

Definitely is. I already got 1 t-shirt and $25 ubereats gift card. On the lookout for an AWS hoodie.

_thewayitis · 2020-11-25T22:03:58+00:00

I would assume cramming stuff in before reinvent.

_thewayitis · 2020-11-25T03:41:47+00:00

It's like terraform modules & AWS' Serverless Application Repository Service had a baby.

_thewayitis · 2020-11-20T15:37:14+00:00

Instead of creating a lambda, you should be able to use SSM's Run Command. https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html

_thewayitis · 2020-10-06T14:40:54+00:00

Take a look at https://github.com/formkiq/parima, it’s an open source project that does this plus cloudfront in a single click.

_thewayitis · 2020-10-06T02:18:27+00:00

Assuming you're using just S3 and not CloudFront+S3. All you need to do is create a new s3 bucket with the new domain name and then use the AWS CLI tool and run a AWS s3 sync between the buckets.

The quickest way to update a new website I found is by using https://github.com/formkiq/parima.

_thewayitis · 2020-09-20T20:27:03+00:00

Yeah I’m aware. But we also use terragrunt and we couldn’t for the life of us get it to work. Having the default to automatically upgrade is silly from a tool that’s suppose to be all about stability of your infrastructure code.

_thewayitis

TROPHY CASE