BasePathMapping

描述

CREATE_FAILED                         AWS::ApiGateway::BasePathMapping      MyApiBasePathMapping

Resource handler returned message: 
Mixing of REST APIs and HTTP APIs  
on the same domain name can only be 
accomplished through API Gateway's  
V2 DomainName interface. Currently, 
WebSocket APIs can only be attached 
to a domain name with other         
WebSocket APIs. This must also      
occur through API Gateway's V2      
DomainName interface. (Service:     
ApiGateway, Status Code: 400,       
Request ID: 5187005f-3413-47bb-b777 
-6c98784001d0

贡献者指南

技术栈

javascripttypescriptnodejsaws

领域

backendapicloud

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Basic AWS API Gateway knowledgeFamiliarity with serverless express examples

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

40

研究方向

Examine the serverless express repository, focusing on the 'basic starter api gateway v2 typescript' example. The issue arises from mixing REST and HTTP APIs on the same custom domain. To resolve, update the example to use the API Gateway V2 DomainName interface for BasePathMapping. Check the AWS CloudFormation template in the example and ensure the domain name is configured using AWS::ApiGatewayV2::DomainName and AWS::ApiGatewayV2::ApiMapping instead of AWS::ApiGateway::BasePathMapping. Review any existing documentation or issues for similar guidance. Consider creating a PR that modifies the example or adds a note in the README about this limitation.