About 270,000 results
Open links in new tab
  1. AWS API Gateway: User anonymous is not authorized to execute API

    Step - 2: Ensure that the API Gateway has whitelisted the AWS Account in the Resource Policy. Step - 3: If the IAM User has been created recently it will take around 5 - 10 mins for the policy …

  2. amazon web services - Why does API Gateway not pass through …

    I need to create an API Gateway that acts as a proxy to a third party client API. I followed exactly what is in this AWS Tutorial. The API Gateway I created is configured to use a custom domain. …

  3. How to pass array query params to AWS API Gateway?

    Aug 5, 2015 · 4 If anyone is using OpenAPI 3.0 spec in AWS Api Gateway then you need to define this in your x-amazon-apigateway-integration like so.

  4. How can I set the AWS API Gateway timeout higher than 30 …

    Jan 22, 2019 · 75 Unfortunately there isn't a way to increase the API Gateway timeout to longer than 29 seconds. This is a limitation of the gateway. The reason you can set the lambda …

  5. How enable CORS in api gateway aws - Stack Overflow

    Nov 17, 2024 · I’m setting up an API using AWS API Gateway and Lambda, and I’m facing CORS issues when making requests from my frontend. While reviewing the setup, I noticed …

  6. amazon web services - AWS API Gateway - Stack Overflow

    In AWS API Gateway, I have a GET method that invokes a lambda function. When I test the method in the API Gateway dashboard, the lambda function executes successfully but API …

  7. aws api gateway - Execution failed due to configuration error: …

    Jan 7, 2019 · I am building a serverless application using AWS Lambda and API Gateway via Visual Studio. I am working in C#, and using the serverless application model (SAM) in order …

  8. AWS API Gateway returns 500, but only sometimes

    Feb 20, 2023 · I am also getting inconsistent results from AWS API Gateway. If I send the same request from Postman too many times, I start having None in my request body, where it is …

  9. AWS API Gateway: Status Code 413, Request Entity too large

    May 26, 2016 · aws-lambda aws-api-gateway asked May 26, 2016 at 23:12 Mandeep Singh 8,254 21 69 106

  10. API Gateway CORS: no 'Access-Control-Allow-Origin' header

    Feb 4, 2016 · Finally, tell DNS how to find your API gateway: create an A record in Route 53 from your api sub-domain to the AWS API Gateway resource You won't see the API available in …