aws-lambda

问题 I was following this medium blog to try to establish a connection to a MSSQL db from a lambda function. I used lambci/lambda:build-python3.8 image to build the container. I followed all the steps mentioned and was able to successfully run the python test script that verifies the connection. Below is the content of the zip file inside the container. However, when I zip it up and upload to lambda, I am receiving below error. START RequestId: 6f3ec44e-aac0-4cc3-b5ed-f8935c4dff4d Version: $LATEST

问题 I have a use case in which I have to verify that the payloads sent to Kinesis firehose are indeed being sent. In order to do that I came up with the chain Firehose -> Firehose Data transformation(using lambda) -> DDB -> Check for payload in DDB (the payload is the hashkey in the DDB). I have to define this entire chain in one shot programatically. The data transformation is the same as http://docs.aws.amazon.com/firehose/latest/dev/data-transformation.html. I am doing all this since I cannot

问题 I have a use case in which I have to verify that the payloads sent to Kinesis firehose are indeed being sent. In order to do that I came up with the chain Firehose -> Firehose Data transformation(using lambda) -> DDB -> Check for payload in DDB (the payload is the hashkey in the DDB). I have to define this entire chain in one shot programatically. The data transformation is the same as http://docs.aws.amazon.com/firehose/latest/dev/data-transformation.html. I am doing all this since I cannot

问题 I have found out that my and my colleagues lambda doesn't return data we anticipate. After what I have already found, we used deprecated invokeAsync which returnes only statusCode . I have upgraded aws-sdk to the newest version and change the invocation code to use invoke with InvocationType: 'RequestResponse' as that should give us the returned value. Lambdas code itself looks good, its an async function without arguments. Im not using the callback here (3rd argument of handler), as we are

问题 I have found out that my and my colleagues lambda doesn't return data we anticipate. After what I have already found, we used deprecated invokeAsync which returnes only statusCode . I have upgraded aws-sdk to the newest version and change the invocation code to use invoke with InvocationType: 'RequestResponse' as that should give us the returned value. Lambdas code itself looks good, its an async function without arguments. Im not using the callback here (3rd argument of handler), as we are

问题 I have found out that my and my colleagues lambda doesn't return data we anticipate. After what I have already found, we used deprecated invokeAsync which returnes only statusCode . I have upgraded aws-sdk to the newest version and change the invocation code to use invoke with InvocationType: 'RequestResponse' as that should give us the returned value. Lambdas code itself looks good, its an async function without arguments. Im not using the callback here (3rd argument of handler), as we are

问题 We are using Amazon connect which uses the "Get customer input" interact block to use the Amazon Lex which internally connects to Lambda so the flow will be like Amazon Connect -> (using Get Customer Input, It connects to Amazon Lex) Amazon Lex -> (In Amazon Lex, the intent is pointed to Amazon Lambda) Amazon Lambda Amazon connect -> Amazon Lex -> AWS Lambda The flow works for all the intents as expected. but for a particular flow, We need to upload the file from lambda to S3 and return the

问题 I want to be able to call a API gateway endpoint from within cloudformation and parse the response from the output and pass in relevant information to one of the other service in the cloudformation. I have an api endpoint https://123x123x.execute-api.eu-west-2.amazonaws.com/myendpoint/tenants with x-api-key: b8Yk6m63rq8XRnMDKa2PeWE3KvBcU7ZyFIn0Vvrty Content-Type: application/json which returns { "tenants": [ { "tenantId": "tenant-1234", "AZ": "us-west-2c", "tenantUsers": 24, "instanceType":

问题 I want to be able to call a API gateway endpoint from within cloudformation and parse the response from the output and pass in relevant information to one of the other service in the cloudformation. I have an api endpoint https://123x123x.execute-api.eu-west-2.amazonaws.com/myendpoint/tenants with x-api-key: b8Yk6m63rq8XRnMDKa2PeWE3KvBcU7ZyFIn0Vvrty Content-Type: application/json which returns { "tenants": [ { "tenantId": "tenant-1234", "AZ": "us-west-2c", "tenantUsers": 24, "instanceType":

问题 I'm creating a CloudFormation template to deploy an EKS node group using the AWS::EKS::Nodegroup CloudFormation resource. It looks like you can create tags for the node group resource specifically, but cannot change the name of the EC2 instances that are deployed as part of the node group. From the AWS documentation, it looks like tags are not propagated to other resources the node group deploys (such as EC2 instances). Does anyone know of a way on how we can update the name of the EC2