29

I am aware that many similar questions have been posted and answered here but none of them is quite the same with what I am experiencing.

I have a Lambda function that handles incoming requests (GET and POST). I also set up an api gateway as public facing endpoint. Additionally, I set up custom domain following Set up Custom Domain Name for API Host Name

The testing call works in both of lambda and api gateway console. Everything also works using the invoke URL but not with the custom domain I've set up.

Here are some more details:

Invoke URL (Works) : 

https://{api gateway id}.execute-api.us-west-2.amazonaws.com/prod/endpoint

Custom domain endpint (Doesn't work): 

https://api.{my domain}.com/endpoint

Base Path Mapping: 

/endpoint   endpoint:prod

All Method Auth: 

Authorization None
API Key Not required

Route53:

A record as alias that points api.{my domain}.com to the cloudfront distribution domain name as alias target.

I'd really appreciate if anyone knows what's going out here.

Improve this question
4
  • Did you also setup a Route53-Record-Set which points to the CloudFront-Distribution? Commented Jul 4, 2017 at 5:42
  • @MaiKaY yes. I have an A record as alias for api.{my domain}.com. The alias target is the CloudFront distribution domain name Commented Jul 4, 2017 at 5:54
  • 1
    I guess you need to change your BasePath Mapping to: / endpoint:prod. Or try with the existing BasePath Mapping to access https://api.{my domain}.com Commented Jul 4, 2017 at 6:06
  • @jlai can you please mention the error you get or your request is not reaching the API gateway Commented Jul 4, 2017 at 6:50

4 Answers 4

Reset to default
49

I had met the same question several years ago and solved it by removing the 'stage' name from the URL.

  1. the URL of gateway API seems like the following:
https://{id}.execute-api.{region}.amazonaws.com/{stage}/todos
  1. if you have routed a custom domain https://api.xxx.com to gateway API {apiName}:{stage}, it seems like the following:
https://api.xxx.com

path: /
target: {apiName}:{stage}
  1. Finally, the correct way to call it is to remove the stage name:
// **remove stage name!!!!**

// Right
https://api.xxx.com/todos

// Wrong
https://api.xxx.com/{stage}/todos
Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

OMG YES! This was exactly my problem!!! I wrote about it here. Basically, the stage name is also replaced by the custom domain. (Note: I wish your answer was a bit clearer, because I didn't get it the first time I read it.)
Boom!! just removed stage name (dev) and it worked!!!
This is beautiful
stage name must be omitted just like you said, ty
30

I found the issue is misunderstanding of how base path mapping works.

All my configurations are correct.

My API resource is not under / but under /endpoint

To use the custom domain, instead of visiting https://api.{my domain}.com/endpoint, it needs to go to https://api.{my domain}.com/endpoint/endpoint

Of course this is silly and redundant.

I have two options. I either set up the base path mapping to / instead of /endpoint or I can just user the API resource / instead of /endpoint.

I go with the latter because if base path mapping is set to /, my api.{my domain}.com will only be able to host just one API (I can still use resources under the same API, but why wasting the extra layer of abstraction?).

This seems dump but I am still glad I figured it out.

Improve this answer

6 Comments

It's not clear why you would expect that a base path of /endpoint with a resource named /endpoint would result in any behavior other than requiring requests to go to /endpoint/endpoint, since the resource is accessed at base-path + resource.
I actually set up the api gateway using lambda's template and the template automatically places it under the name of the API instead of API's root. This is my first time using it so I didn't expect this behavior. I was anticipating that the resource is created right under the root of API, meaning the name of the API should just be the name of API and the root is used for the very first resource by default.
I see what you mean.
I ran into the same issue, also not realizing that lambda creates a nested resource in the gateway. I was receiving {"message":"Missing Authentication Token"}
yeah, jlai. Im agree with you. my api was "abcd12345.execute-api.us-east-1.amazonaws.com/Dev/resource" but when i create custom api domain name and add only stage, not path, then i can only access it by example.com/resource. its really silly.
|
1

Step 1: Map the A record from subdomain.yourdomain.com to API Custom domain/API Gateway domain name(API Gateway -> Custom domain names -> tab Configuration/Endpoint Configuration).

Step 2: From API Gateway/ API Custom domain - add the api mapping. Leave "path" empty.

End point format:

Original endpoint: https://{api gateway id}.execute-api.us-west-2.amazonaws.com/prod/endpoint

Endpoint with API custom domain: https://api.yourdomain.com/**endpoint**

Improve this answer

1 Comment

Thank you! This was the issue for me. I had originally added paths for each of my endpoints. I figured that maybe I should be leaving the path empty and tried that. But I didn't remove the others. Make sure you don't have mappings that are overriding the one with an empty path.
0

Another reason for this can be that your user, although admin, does not have a bloody CloudFrontFullAccess permissions! I just spent a couple of hours on it as I relied on serverless to do it for me and it worked perfectly on another project with different credentials, though. So double check the article! https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.