-
Notifications
You must be signed in to change notification settings - Fork 426
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
Improved documentation for snowflake_system_get_aws_sns_iam_policy #2181
Comments
Hey @chriselion. Thanks for creating the issue. You are right: an example for The behavior and the reasons behind Would you like to propose any more additions? |
Thanks @sfc-gh-asawicki - the docs for The docs give a good explantion of the "why" but not really the "how" - even with that information, using the results from |
Add missing documentation that should resolve - #1087 - added descriptions for the `SNOWFLAKE_IAM_USER` and `AWS_EXTERNAL_ID` fields in stage - #2181 - added simple example and custom description with links for the snowflake_system_get_aws_sns_iam_policy to show how it could be used with AWS - Add missing parts for the Issue creating guide + FAQ - Pull out the SDK error to common package + usage in places where errors were compared with string instead of predefined error
Hey @chriselion, |
Closing due to long inactivity and the fact that the documentation was adjusted. |
Is your feature request related to a problem? Please describe.
The documentation for
snowflake_system_get_aws_sns_iam_policy
(link) doesn't give an example of how to call it (which isn't that bad), and doesn't explain how it should be used in the bigger picture.Describe the solution you'd like
I assume the primary motivation for
snowflake_system_get_aws_sns_iam_policy
is to grant access to an SNS topic that is receiving S3 bucket notifications (at least that's what I'm using it for). In this case,snowflake_system_get_aws_sns_iam_policy
is a potential foot-gun, because if you pass it blindly to anaws_sns_topic_policy
, it will conflict with anyaws_sns_topic_policy
's that grant the S3 bucket permission to publish on the topic. Instead, you need to combine the two policies withsource_policy_documents
Describe alternatives you've considered
An alternative data source that just provides the IAM user ARN (e.g. "arn:aws:iam::123456789001:user/vj4g-a-abcd1234" from here) might be easier to work with in general, since the user can insert than into their own policy JSON.
Additional context
The way that I ended up setting up the SNS policy looked like this
The
source_policy_documents
was the tricky part (at least for me).The text was updated successfully, but these errors were encountered: