1. We have set more than 500 resources (N lambdas and 1 API Gateway) in the cloudformation template yaml. 2. Because there are more than 500 resources, you cannot use sam deploy to AWS 3. We will split the resource into at least two templates and deploy them to separate cloudformation 4. But I hope that the lambdas in these two cloudformations share the same API Gateway 5. The actual practice is to set N lambdas and an API Gateway (testApi) in the first template yaml. The Events->getEndpoint->Properties->RestApiId of N lambdas: !Ref testApi 6. Question, in the second lambda in template yaml, how to set RestApiId to point to testApi template

AWS::Serverless::Function RestApiId specifies the API Gateway ID that is not in this cloudformation

We have set more than 500 resources (N lambdas and 1 API Gateway) in the cloudformation template yaml.
Because there are more than 500 resources, you cannot use sam deploy to AWS
We will split the resource into at least two templates and deploy them to separate cloudformation
But I hope that the lambdas in these two cloudformations share the same API Gateway
The actual practice is to set N lambdas and an API Gateway (testApi) in the first template yaml. The Events->getEndpoint->Properties->RestApiId of N lambdas: !Ref testApi
Question, in the second lambda in template yaml, how to set RestApiId to point to testApi template

Sujets

Balises

Langue

English

demandé il y a un mois104 vues

1 réponse

Ces réponses sont-elles utiles ? Votez pour la bonne réponse pour aider la communauté à bénéficier de vos connaissances.

Hi JasonKao,

please refer to this walkthrough on how to create a cross-stack reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/walkthrough-crossstackref.html which will allow you to reference the API Gateway resource from the first stack in the second one.

EXPERT

répondu il y a un mois

JasonKao
il y a un mois
After querying SAM-related documents [1], I found that the document has the following description: RestApiId: This cannot reference an AWS::Serverless::Api resource defined in another template. This also means that other RestApiId cannot be referenced in the current template.

Reference documents: [1] https://docs.amazonaws.cn/en_us/serverless-application-model/latest/developerguide/sam-property-function-api.html#sam-function-api-restapiid
ben-from-aws EXPERT
il y a un mois
Please be aware that the documentation and restriction that you linked to are specific to SAM (Serverless Application Model) with is a basically an extension of CloudFormation.
JasonKao
il y a un mois
Yes, I use SAM Deploy CloudFormation.