1 Answer
- Newest
- Most votes
- Most comments
1
This ended up being very easy to accomplish. I had been focused on the custom domain part so much I overlooked that I could simply create a BasePathMapping. The following worked fine for me:
BasePath:
Type: AWS::ApiGateway::BasePathMapping
Properties:
BasePath: my-service
DomainName: !Ref DomainName # I pass this in as a parameter per environment.
RestApiId: !Ref MainApi # This is my AWS::Serverless::Api resource
Stage: default
Edited by: StealthSid2 on Jul 16, 2020 12:12 PM
answered 4 years ago
Relevant content
- Accepted Answerasked 6 years ago
- Accepted Answerasked 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
@StealthSid2, could you share your template.yml for two of your projects? I'm struggling to accomplish the same thing. I can get one project to use BasePathMapping with domain, but when I try to take the same approach in my second microservice project I get this error when trying to deploy in SAM:
api.hostname.com | Mapping already exists in stack arn:aws:cloudformation:us- east-1:...
Essentially it says the mapping already exists.