API Gateway Cloudwatch logs can help in troubleshooting issues related to request execution or client access to your API. This blog will help in understanding details to enable CloudWatch Logs for troubleshooting API Gateway REST API or WebSocket API Execution Logs vs Access Logs There are two types of API Gateway Cloudwatch logs: Execution logs […]
API Gateway General SSLEngine error is a common error in the API Gateway private integration (VPC Link) and HTTP Integration. In both these integrations the endpoint can be HTTPS and as a requirement the backend target must return a certificate trusted by certificate authorities supported by API Gateway. Here is a list of certificate authorities
Amplify console build failure FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed – JavaScript heap out of memory error could occur If application’s node module requires more memory than the default memory limit of node.js At the writing of this article, Default size of container used by Amplify Console for build is approximately 7
With Mock Integration Amazon API Gateway there are 2 common reasons for 500 Internal Server error. Check the mapping template in Integration Request and ensure that you are passing statusCode as an integer to the MOCK Integration endpoint. { “statusCode”: <Integer_Status_code> } Note: Make sure that status code is passed as integer not string. Correct
Amplify Console provides a feature called Live package updates. The default package build used by Amplify console comes with preinstalled dependencies. If you configure Live Package Updates It will override the version of the pre-installed dependencies including Amplify CLI and specify either a specific version, or always ensure the latest version is installed. Note: This
Amazon API Gateway supports certificate-based mutual Transport Layer Security (TLS) authentication . Mutual TLS authentication requires two-way authentication between the client and the server. When using Custom Domain Names for API Gateway and enabling mutual TLS on custom domain name, There is a restriction as mentioned in AWS Documentation To resolve this error, Create a
IP Address ranges provided by AWS is provided as a JSON file here. These address ranges keep on changing. The addresses listed for API_GATEWAY are egress only. For restrict/allow the traffic coming from API Gateway, Based on you are using a Regional or an Edge-Optimized endpoint you can whitelist entire IP address range of EC2
As per the documentation, For Rest APIs 29 seconds Integration timeout limit is a hard limit which means it can’t be increased. For HTTP APIs the Integration timeout limit is 30 seconds LAMBDA INTEGRATION Workaround:You can asynchronously Invoke your backend to return a HTTP 202 status code which means that the request has been accepted
Amazon API Gateway 504: Execution failed due to a timeout error Read More »
