swift-aws-lambda-runtime | Swift implementation of AWS Lambda Runtime | Serverless library

Edit: Changed title to reflect the problem properly.

I am trying to pick the exact type definition of a specific property inside a interface, but the property is a mapped type [key: string]: . I tried accessing it using T[keyof T] because it is the only property inside that type but it returns never type instead.

is there a way to like Pick or Interface[[key: string]] to extract the type?

The interface I am trying to access is type { AWS } from '@serverless/typescript';

based on the aws documentation, maximum timeout limit is less that 30 seconds in api gateway.so hooking up an sagemaker endpoint with api gateway wouldn't make sense, if the request/response is going to take more than 30 seconds. is there any workaround ? adding a lambda in between api gateway and sagemaker endpoint is going to add more time to process request/response, which i would like to avoid. also, there will be added time for lambda cold starts and sagemaker serverless endpoints are built on top of lambda so that will also add cold start time. is there a way to invoke the serverless sagemaker endpoints , without these overhead?

I am trying to submit google dataproc batch job. As per documentation Batch Job, we can pass subnetwork as parameter. But when use, it give me

ERROR: (gcloud.dataproc.batches.submit.spark) unrecognized arguments: --subnetwork=

Here is gcloud command I have used,

I have created a SAM template with a function in it. After deploying SAM the lambda function gets added and are also displayed while adding lambda function trigger in cognito but when I save it gives a 404 error.

SAM template

Im using Serverless Framework to deploy a Docker image running R to an AWS Lambda.

I'd like to use CockroachDB Serverless for my Ecto application. How do I specify the connection string?

I get an error like this when trying to connect.

I have created a RDS cluster with 2 instances using terraform. When I am upgrading the RDS from front-end, it modifies the cluster. But when I do the same using terraform, it destroys the instance.

We tried create_before_destroy, and it gives error.

We tried with ignore_changes=engine but that didn't make any changes.

Is there any way to prevent it?

I am trying to deploy a REST API in AWS using serverless. Node version 14.17.5.

My directory structure:

When I deploy the above successfully I get the following error while trying to access the api.

We are a team of 5 developers working on a video rendering implementation. This implementation consists out of two parts.

1. A live video preview in the browser using angular + konva.
2. A node.js (node 14) serverless (AWS lambda container) implementation using konva-node that pipes frames to ffmpeg for rendering a mp4 video in higher quality for later download.

Both ways are working for us. Now we extracted the parts of the animation that are the same for frontend and backend implementation to an internal library. We imported them in BE and FE. That also works nicely for most parts.

We noticed here that konva-node is deprecated since a short time. Documentation says to use canvas + konva instead on node.js. But this just doesn't work. If we don't use konva-node we cannot create a stage without a 'container' value. Also we cannot create a raw image buffer anymore, because stage.toCanvas() actually returns a HTMLCanvas, which does not have this functionality.

• So what does konva-node actually do to konva API?
• Is node.js still supported after deprecation of konva-node?
• How can we get toBuffer() and new Stage() functionality without konva-node in node.js?