Skip to content

Create role for snoflake access to synapsedev data with fake extID to get roleArn #1028

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

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions sceptre/synapsedev/config/prod/snowflake-access.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
template:
type: http
url: https://{{stack_group_config.admincentral_cf_bucket}}.s3.amazonaws.com/aws-infra/v0.7.8/IAM/snowflake-bucket-access.yaml
stack_name: snowflake-access.yaml
parameters:
BucketArn: arn:aws:s3:::dev.datawarehouse.sagebase.org
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this makes me wonder why the role for this bucket isn't created in the same template that created the bucket?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting thought, the goal was for org-infra to adopt resources already deployed into the with a shared template (with the benefit that the template can be used for to give Snowflake access to any bucket/prefix in the org)

BucketPrefix: warehouse
SnowflakeAccountArn: arn:aws:iam::365909334157:user/m2nb0000-s
SnowflakeAccountExternalId: 0123456789