API Gateway API Mappings deployed through CDK do not work until modified via console

0

We have a CDK v1.152.0 stack that has a RestApi with an api mapping to a custom domain (created using the RestApi and BasePathMapping CDK constructs). The API Gateway fronts a Fargate cluster which is load balanced (created with the ApplicationLoadBalancedFargateService CDK construct). We are seeing unusual behavior related to the api mapping.

When the stack is first deployed via CDK, the API ID based URL (i.e. https://<api-id>.execute-api.<region>.amazonaws.com/<stagename>) works. However, the URL that uses the custom domain and api mapping does not - it returns Forbidden.

At this point, either of the following 2 actions will allow both the API ID based URL as well as the custom domain/api mapping based URL to function properly:

  1. Modify the api mapping path value via the console to an invalid value, then change it back to the valid value
  2. Completely delete the api mapping for this API via the console.

We don't understand why this is necessary (and especially - how the custom domain/api mapping URL can continue to work at all once the API Mapping record is deleted through the console). We've been able to duplicate the behavior described above consistently.

Has anyone experienced similar behavior or know a reason why the api mapping would need to be touched through the console before it works properly?

1 個回答
0

Hello,

Thank you for reaching out to us.

In order to troubleshoot this issue further, could you please provide steps to reproduce this issue. I would also recommend to open a support case with API ID and custom domain to investigate on this issue further.

AWS
支援工程師
已回答 2 年前
  • Thanks. A day after posting this message we opened a support ticket and are pursuing the matter that way.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南