gateway-api | Hummingbot Gateway is an open-source project | Cryptography library

I am having trouble sending specific JWT authorization claims information derived from the Authorization header of a request to an API Gateway REST API endpoint (with non-proxy Lambda integration). The endpoint is secured with a Cognito User Pool Authorizer with Login with Amazon as the identity provider. From the Cloudwatch execution logs of API Gateway, I can see the JWT authorizer claims:

I built a simple HelloWorld API using a lambda function and APIGateway. I'm using Cloudformation.

The lambda function runs fine when I run it using aws lambda invoke.
The API runs locally using sam local start-api.

But when I deploy it using sam deploy (after using package of course), the API returns status code 500.

This is the log that I get when I try to test it.

I am building my app on AWS and my app uses websocket like this:

Frontend WebSocket client ---> AWS API Gateway Websocket API ----> Backend in EC2 instance.

Now, in order to let my backend Express code know how to send message to a particular client, I have let it know the connectionId of a websocket client / a user. I am following these two answers:

• https://stackoverflow.com/a/59220644/3703783
• https://stackoverflow.com/a/65112135/3703783

which have explained very clearly.

Below is my configuration in AWS API Gateway WebSocket API:

What I did was using Request Template, matching all incoming requests, to transform the content which will be sent to my integration endpoint as the body of the request. Eventually I want to keep the original request, while adding attributes (like Connection Id) on top of it. For testing purpose, I set the following template:

I am building my app on AWS and yy app uses websocket like this:

Frontend WebSocket client ---> AWS API Gateway Websocket API ----> Backend in EC2 instance

Here is how it works:

With AWS API Gateway, WebSocket API takes action set by my $connect integration. In my current configuration, I have set the VPC Link integration with HTTP Method Any on the target url. When the Frontend tries to make a websocket connection with the API Gateway, WebSocket API's $connect method is triggered and the AWS WebSocket API calls my backend HTTP endpoint /connect.

Frontend: ReactJS / Javascript Native Websocket: In my component that uses websocket:

I have a gateway configured for my project, and i added the security options in the route and it's works:

My function thats generate the jwt token:

Goal:
I have set up a Google API Gateway. The backend for the API is a cloud function (written in python). The cloud function should query data from Google BigQuery (BQ). To do that, I want to create a BQ Client (google.cloud.bigquery.Client()). The API should be accessed by different applications using different service accounts. The service accounts have permission to access only specific datasets within my project. Therefore, the service accounts/applications should only be able to query the datasets they have the permission for. Therefore, the BQ Client within the cloud function should be initialized with the service account that sends the request to the API.

What I tried:
The API is secured with the following OpenAPI definition so that a JWT signed by the service account SA-EMAIL is required to send a request there:

I want to design a microservice system. I see it this way. I send all requests to the spring-gateway-api.

Then he sends it to the service (let's call it order) But how can I dynamically increase/decrease the number of instances of the order service. What should I do if the sping-gateway-api service starts dying from the number of requests?

How are such issues resolved?

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:

I have a problem with my HTTP integration for an AWS API Gateway that uses WEBSOCKET

These are the main characteristics of my configuration (it can be viewed in detail in the cloud formation template at the end of the post):

• Api Gateway Websocket
• Route selection expression $request.body.action
• Disabled execute api endpoint because I'm using a custom domain, although it does not seem to make any difference if I use the Api Gateway direct url instead
• Routes $connect, a send and a $disconnect
• Integration type is HTTP_PROXY
• The integration Uri (and here is the interesting part) is a URL that points to my custom domain, and the DNS resolves as ANOTHER Api Gateway in my AWS account (an HTTP one) that integrates with a private ALB through a VPC_LINK and reaches a web service in an ECS cluster (I guess this is irrelevant now).
• Bot Api Gateway, the http one and the websocket one, use a custom domain api.mycompany.io and ws.mycompany.io with a TLS certificate *.mycompany.io
• The HTTP services run in a private subnet, but they're perfectly reachable from internet. I can send http requests and get back responses.

When I do