1 Answer
0
Both REST and HTTP APIs are supported, but the CLI to create the mapping is in apigatewayv2. You should use the following command:
aws apigatewayv2 create-api-mapping --domain-name rimbleanalytics.com --api-mapping-key orders/v2 --api-id f3ho0c7zx0 --stage production
Relevant questions
API Gateway custom domain with base path missing from request
asked 10 months agoAPI HTTP Gateway path rewrite question
Accepted Answerasked 3 months agoValidate path param in AWS API Gateway through OpenAPI spec
asked 7 months agoCan I use API Gateway cache invalidation with a custom authorizer ?
asked 8 months agoCan't define an AWS API Gateway mapping template from the console
asked 2 years agoAPI Gateway -> Kinesis Mapping Issue
Accepted Answerasked 2 months agoDelete base path mapping in API Gateway doesn't work
asked 5 years agoAWS Api gateway for REST API does not work with multi-level base path mapping
asked 6 months agoAPI Gateway Mapping Template missing toJson
asked 6 months agoAPI Gateway mapping template transformation causes a precision error for exponential notation
asked a month ago
Hey Uri - thanks for the response but it does not work:
aws apigatewayv2 create-api-mapping --domain-name rimbleanalytics.com --api-mapping-key v1/orders --api-id f3ho0c7zx0 --stage productionAn error occurred (BadRequestException) when calling the CreateApiMapping operation: Only REGIONAL domain names can be managed through the API Gateway V2 API. For EDGE domain names, please use the API Gateway V1 API. Also note that only REST APIs can be attached to EDGE domain names.
Did not know you are working with Edge optimized APIs. From the documentation: To configure API mappings with multiple levels, your custom domain name must be regional and use the TLS 1.2 security policy.
This means that you can't achieve what you want as your custom domain name is edge optimized.