apigateway | Programmable API gateway micro framework | REST library

Below is the my cloudformation template. I want to convert aws:SourceVpc into list in the resource policy document. I tried with spilt but cft below error.

Invalid policy document. Please check the policy syntax and ensure that Principals are valid. (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: xxxxx; Proxy: null)

Also devl and sdbx have 1 value where as others acnt and acpt have two values in mappings how can do it. Please suggest.

Output should like below. aws:SourceVpc: ["vpc-7830jkd", "vpc-a1236"]

I'm utilizing AWS's CDK to develop our API layer. Everything has worked so far, and now I am adding in caching. I enabled CacheCluster in the stage and I am trying to enable it for a handful of my endpoints. The problem I am facing is the CDK is changing the resource path from something like /v1/configuration to /~1v1~1configuration. I've tried escaping my /s, but that didn't fix my issue.

CDK C# Code

I have been pouring way too many hours into getting this to work, and I see that similar questions are posted here on SO but I have yet to find a solution that'll solve my problem.

I have created a REST API using the Serverless Framework. I now want to create an endpoint to which a user can send a POST request with an image as in the body as a form-data.

I have the endpoint here:

The endpoint uses a middleware uploader.single('param') and then passes the result to a function uploadImage.

The middleware looks as following:

The image is stored by library "multer":

But is broken

I read that you might need to add binaryMediaTypes to the apiGateway provider in serverless.ts, so I did as following:

Can anyone help me out with this?

i am not able to invoke express stepfunction using restapi apigateway action type with StartSyncExecution

thanks in advance

Using python boto3 I am trying to create a trigger point for my lambda function. Resource creation, put_method, put_integration take place properly. But under lambda function->configuration->triggers, I do not see API Gateway created, also if I try to test the API Gateway it throws "Internal Error". But, if I go to API Gateway->my_rest_api->resouurce->method->Integration Request, here based on the configuration that I provided "Use Lambda Proxy integration" will be selected, if I deselect, and revert back i.e select. The function behaves as expected. I am trying to automate AWS using boto3, this is hindering the process. Below is the function:

I have a Serverless application using Localstack, I am trying to get fully running via Docker. I have a docker-compose file that starts localstack for me.

I have a local Kubernetes install based on Docker Desktop. I have a Kubernetes Service setup with Cluster IP on top of 3 Pods. I notice when looking at the Container logs the same Pod is always hit.

Is this the default behaviour of Cluster IP? If so how will the other Pods ever be used or what is the point of them using Cluster IP?

The other option is to use a LoadBalancer type however I want the Service to only be accessible from within the Cluster.

Is there a way to make the LoadBalancer internal?

If anyone can please advise that would be much appreciated.

UPDATE:

I have tried using an LoadBalancer type and the same Pod is being hit all the time also.

Here is my config:

I am experimenting with an AWS API-Gateway integration with an S3 backend. I have noticed the switch between different mapping-templates in the integration-response does not appear to work.

In integration-response, I have the following mapping templates:

application/json:

There is a similar question but it does not use AWS::ApiGatewayV2::Stage, and I need the AutoDeploy that only the V2 seems to provide.

How do I enable CloudWatch logs and log full message data (as per the image) using CloudFormation in an AWS API Gateway?

I can't find anything at the documentation for the Stage https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigatewayv2-stage.html#cfn-apigatewayv2-stage-deploymentid

I am using an autodeployed stage. I am able to create the log groups, the IAM role to write logs in CloudWatch, but I can't enable the logging itself.