#apigw — Public Fediverse posts

@kaitoedter check here

https://serverlessland.com/patterns/apigw-lambda-authorizer-sam-nodejs

If you want to pass, for example, some custom data to the downstream lambda, you should use the Context, but you need a custom template for it with #apigw

If you do it in #rust, I wrote something here https://dev.to/aws-builders/api-gateway-to-a-lambda-function-using-lambda-proxy-and-non-proxyintegration-with-openapi-specs-5eak

#aws #serverless

@kaitoedter check here

https://serverlessland.com/patterns/apigw-lambda-authorizer-sam-nodejs

If you want to pass, for example, some custom data to the downstream lambda, you should use the Context, but you need a custom template for it with #apigw

If you do it in #rust, I wrote something here https://dev.to/aws-builders/api-gateway-to-a-lambda-function-using-lambda-proxy-and-non-proxyintegration-with-openapi-specs-5eak

#aws #serverless

Currently, no observability services can track #eventbrige or a chain like #apigw to #sns to #sqs. Pipes' arrival makes it even worse. I am happy about #cloudwatch EMF. It is overall cheaper than paying third-party services, and I can track all I want.
I do not have a nice ServiceMap, but I have all I need for a dashboard.

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html

#aws #serverless #eda

Currently, no observability services can track #eventbrige or a chain like #apigw to #sns to #sqs. Pipes' arrival makes it even worse. I am happy about #cloudwatch EMF. It is overall cheaper than paying third-party services, and I can track all I want.
I do not have a nice ServiceMap, but I have all I need for a dashboard.

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html

#aws #serverless #eda

The #eda part is made of:
#APIGW to #SNS or #EventBridge to #SQS to #lambda
Still checking, but the response from Lambda to the user with IoT looks slower, not by much when you are using SNS than Sync operation. When I use EventBridge, it is kind of a second later.
The power of #serverless

The #eda part is made of:
#APIGW to #SNS or #EventBridge to #SQS to #lambda
Still checking, but the response from Lambda to the user with IoT looks slower, not by much when you are using SNS than Sync operation. When I use EventBridge, it is kind of a second later.
The power of #serverless

Moving from synchronous #apigw to fat #lambda that calls in parallel #eventbridge #dynamodb #s3 #stepfunctions #sqs #sns to fully #eda lambda that calls just #dynamodb and fan-out with #sns gave me just an 8% increase in term of scalability. #eda with #eventbridge is the same as the fatty 😭

Moving from synchronous #apigw to fat #lambda that calls in parallel #eventbridge #dynamodb #s3 #stepfunctions #sqs #sns to fully #eda lambda that calls just #dynamodb and fan-out with #sns gave me just an 8% increase in term of scalability. #eda with #eventbridge is the same as the fatty 😭

I do not envy the poor person who should test my case.
- AWS IoT Core publishing issue from Lambda
- APIGW VTL fun
- OpenSearch mystery filtering
I am with you and eternally grateful for the job that you are doing
#aws #serverless #apigw #iot #opensearch

I do not envy the poor person who should test my case.
- AWS IoT Core publishing issue from Lambda
- APIGW VTL fun
- OpenSearch mystery filtering
I am with you and eternally grateful for the job that you are doing
#aws #serverless #apigw #iot #opensearch