order of deployment for shared authorizer across all API gateways

[s1mrankaur]

I am using the Serverless framework and we will have multiple microservices for tenants, users, and such.

Each microservice will have its own API gateway. I do want to ensure that APIs remain independently deployable and would like to limit the dependency to the minimum.

In the case of an independent API gateway for each service, the serverless.yml file in each of the folders of microservices will define the API gateway. I intend to share the lambda authorizer. Once lambda authorizer is deployed, it's arn should be stored in SSM and will be fetched at API gateway definition in the serverless.yml file. The ARN will be available only if the authorizer gets deployed first.

How can we make sure that lambda authorizer is deployed before the API gateways?

2. Similarly, when microservice A calls microserviceB, How do we ensure that microserviceB gets deployed first? (This without specifying the order of deployment in the CI/CD pipeline)