-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Add support to specify a SNS topic that belongs to a different region #105
Comments
@DaichiUeura - I am seeking the same answer, may you tell me why you closed this? Was there a resolution? Thanks! |
@jolexa The reason why I closed this is that this seems to be not a SAM file issue. Here is the explanation from AWS support. This error happens when a SNS Topic and a SNS Subscription are created in different regions(i.e. Both needs to exist in a same region). If there is a SNS Topic declaration at Events property in a SAM file, a SNS Subscription is created in the region where a stack is created. To avoid the issue, we need;
|
Ok, thanks. I understand and was afraid that was the case. I think that SAM should be able to parse the region from the SNS TopicArn and be able to implicitly do the correct thing. That may be tricky with the cloudformation architecture. Would you mind 1) Updating this issue's title to say "Feature Request:" and 2) re-open the issue so that we can get a SAM maintainer's opinion/attention someday? |
@jolexa Done ;) |
Appreciate the feature request. SAM can't do much here because it can only meddle with resources we create in the template. Outside resources are pretty much a blackbox when it comes to SAM |
I created pull request to add description in specification #312 |
This should be possible now since Cloudformation has added a |
@DaichiUeura Can we reopen this? Given that it's now supported in CloudFormation? |
Reopening since CFN added support. |
I created a pull request to resolve this issue. |
Pending v1.14.0 release |
Closing this issue as this is released in v1.14.0 |
Hello,
I tried to set a SNS topic existed in a different region as a trigger like below. However CloudFormation said "Invalid parameter: TopicArn". Is this a current limitation or something like that?
The text was updated successfully, but these errors were encountered: