Single Storage Integration Per AWS Landing Account

urn:js:virtue:aspire:standard:3.2

TL;DR

We should have only a single Snowflake storage integration per AWS landing account.

Definition

To avoid multiple storage integrations for a landing account we should create a single integration that is able to access all buckets (existing and new) in the account. The AWS role used by the integration should have the required AWS API access privileges scoped to all S3 resources in the account.

External stages created in Snowflake can then specify the bucket and prefix they require and state the account integration for use.