1 Answer
- Newest
- Most votes
- Most comments
0
A similar error was reported in this GitHub issue.
This issue seems to be caused by the fact that there are a lot of resources here.
Does this apply in your case?
https://github.com/serverless/serverless/issues/9036#issuecomment-1047240189
https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1364
By the way, are you sure you are referencing the correct "ParentId" in "AWS::ApiGateway::Resource"?
Check to make sure you are not referring to the wrong resource.
Relevant content
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
yes, as I mentioned earlier Im using same serverless template till date, and It was working fine in the us-east-1 region, now I just changed the region and some parameters related to vpc and subnets then I started facing this, I am deploying many API gateway related resources in one go maybe that is causing this issue?
Yes, I think that is a conceivable possibility.