AWS SAM and the changes in resource ARNs with each deployment

Question

I see that one SAM deployment over another, that the previous resources are deleted, and new resources are created. Now, the new resources that are created are actually not the same resources, and have a different ARN than before.

This causes some problems that I am facing right now. Say that we have non SAM resources which require set for for the SAM resources.

Like for example, we have an SNS which is subscribed by our API gateway. Now after the deployment the ARN of the API gateway changes, and we'd require to subscribe again.

There are more problems like this that I am facing, but this is the gist of it.

Any help appreciated!

Answer 1

The ARN of the resource can remain same if the name of the resource is specified in the template. Since the name now remains the same, the ARN too will remain the same, even after multiple deployments.