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 . Looking forward to […]
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.
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
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. Learn more about vpclinks here : https://cloudnamaste.com/understanding-vpc-links/ Above image created using napkin.ai Read about it here and start using
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
This article focuses on Troubleshooting API Gateway Private API. Following are the common causes of restricted access to Private API Before you start troubleshooting API Gateway Private APIs, enable API Gateway CloudWatch Access and Execution logs. Refer: Enable API Gateway CloudWatch Logs Logging SettingsLog level, choose INFOLog full requests/responses data Set to True Note: If
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
