arize-ingestion-key tag, label, or metadata value from the connector setup dialog. See Data Fabric.
One prefix per space
Each connector is scoped to one Arize AX space. Give each space its own bucket or prefix, and scope IAM policies to it.Reuse identity provider groups
SAML SSO role mappings map identity provider groups to Arize AX spaces and roles. The same groups can grant cloud storage access, so one membership controls both.- Define a group per team in your identity provider, for example
team-alpha. - Map the group to the team’s space with a SAML role mapping.
- Map the same group to a cloud IAM policy that reads only
your-bucket/team-alpha/*.
Prefix-scoped IAM policies
The Arizearize-data-fabric role or service account needs write access across all prefixes. These policies are for people and analytics tools that read only their team’s prefix.
- Amazon S3
- Google Cloud Storage
Query-time controls
Warehouses can restrict a user who already has bucket read access.- AWS Lake Formation enforces column-level and row-level permissions for Athena and Redshift Spectrum.
- BigQuery IAM controls access to external tables independently of the GCS bucket.
- Snowflake RBAC restricts which roles can query each external table.