aws-api-gateway

I have created and deployed an AWS API Gateway resource with the following structure including a custom HTTP Request Header 'X-header' dev (stage) /echo (resource) POST (method) Method Request - Headers: X-header OPTIONS (method) Method Request - Headers: X-header When I POST to the endpoint from Chrome, I get the following error. XMLHttpRequest cannot load https://fxxxx.execute-api.us-west-2.amazonaws.com/dev/echo . Request header field X-header is not allowed by Access-Control-Allow-Headers in preflight response. Chrome is doing a preflight check against the OPTIONS method. I can see the

I have an API deployed on AWS API Gateway. I will have multiple subscribers using my API and each customer would be unique. Is it possible that each customer will have a separate API key unique to him? Or will I have to create those many IAM users in order for them to be unique? If yes for the IAM users, then what is the upper limit of the number of users? I will be doing all this programmatically. By unique, if you mean that you should be able to identify which request came from who, then you can generate one API Key per subscriber. You can generate up to 10000 API keys per AWS account. More

I have a very basic lambda function written in Scala deployed to AWS Lambda. The function works just fine when I test it via the AWS Lambda console. Here's the function with some additional logging added for debug purposes. package com.spacecorpshandbook.ostium.lambda.handler import java.util import com.google.gson.Gson import temp.{ApiGatewayProxyResponse, Appointment, CancelResponse} /** * Amazon Lambda handler adapter for the Cancellation application */ class CancellationHandler { def cancelAppointment(appointment: Appointment): ApiGatewayProxyResponse = { System.out.println("++++

I'm looking a solution for my problem and maybe someone could give me some ideas. I have a API Gateway plugged to a aws lambda A. I have to handle cases like this: Lambda A should call lambda B and if there are any results, return to the API Gateway. Lambda A should call lambda B and if no results, it will call lambda C, and then return whatever the results are to the APi Gateway . So, my problem is how to chain these lambdas, because I don't want to have a huge lambda. At first, I thought about using Step Functions except that this works in a asynchronous mode, so no good for my case. I know

I'm attempting to integrate my lambda function, which must run async because it takes too long, with API gateway. I believe I must, instead of choosing the "Lambda" integration type, choose "AWS Service" and specify Lambda. (e.g. this and this seem to imply that.) However, I get the message "AWS ARN for integration must contain path or action" when I attempt to set the AWS Subdomain to the ARN of my Lambda function. If I set the subdomain to just the name of my Lambda function, when attempting to deploy I get "AWS ARN for integration contains invalid path". What is the proper AWS Subdomain for