Lambda provides an option to configure timeout value for a function to any value up to 15 minutes. When the specified timeout is reached, AWS Lambda terminates execution of your Lambda function. As a best practice, you should set the timeout value based on your expected execution time to prevent your function from running longer … Continue reading Troubleshoot AWS Lambda Timeout issues
Author: CloudNamaste
API Gateway Resource Policies
Thi API Gateway Resource policy troubleshooting guide is based on How API Gateway resource policy affect authorization workflow - https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-authorization-flow.html How to use this guide 1. Identify the Authorization workflow applicable for your Use case 2. Based on authorization workflow and If API is accessed from same account or cross account , refer the Table A … Continue reading API Gateway Resource Policies
Build APIs with Amazon API Gateway
I am happy to announce my first course on Building APIs with Amazon API Gateway on Udemy. This is my attempt to increase awareness and adoption of Amazon API Gateway service and build support and expertise across Global Community. I am aiming to add more and more content and support related to Amazon API Gateway … Continue reading Build APIs with Amazon API Gateway
Join CloudNamaste Discord community !!!
CloudNamaste Discord community is an initiative to start a Discord channel where you can ask your queries related to API Gateway and other AWS services and carry out discussions with like minded people. If you have any questions related to articles on this website please free to ask in the channel . Join here : … Continue reading Join CloudNamaste Discord community !!!
Minimum TLS version for API Gateway
The APIs created with Amazon API Gateway expose HTTPS endpoints only. API Gateway doesn't support unencrypted (HTTP) endpoints. TLS offers multiple versions and It is recommended to use the later versions of TLS protocol as they offer more security features. Therefore, It is a common requirement to enforce a minimum TLS version on API Gateway. … Continue reading Minimum TLS version for API Gateway
Understanding TLS Protocol
This article will help you in understanding TLS Protocol and difference between it's various versions. What is TLS? Transport Layer Security abbreviated as TLS is a cryptographic protocol designed to provide secure communication between web browsers and servers.TLS is a succesor of Secure Socket Layer (SSL) protocol. Sometimes, TLS is also referred as SSL. The … Continue reading Understanding TLS Protocol
Amazon API Gateway 504 : Execution failed due to a network error communicating with endpoint
Amazon API Gateway 504 : Execution failed due to a network error communicating with endpoint could be caused by networking problems with integration. In VPC Link Private Integration and HTTP Integration such errors can be seen. COMMON REASONS for Amazon API Gateway 504 : Execution failed due to a network error communicating with endpoint 1.) … Continue reading Amazon API Gateway 504 : Execution failed due to a network error communicating with endpoint
Enable API Gateway CloudWatch Logs
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 … Continue reading Enable API Gateway CloudWatch Logs
API Gateway General SSLEngine error
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 … Continue reading API Gateway General SSLEngine error
Amplify Console Build fails with FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed – JavaScript heap out of memory
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 … Continue reading Amplify Console Build fails with FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed – JavaScript heap out of memory