Great explanation! I'd add one important consideration from a cross-cloud architecture and data governance perspective.Before implementing OpenSharing with AWS Glue, I would clarify exactly what the source team means by "no replication or ingestion i...
Thanks for clarifying! It sounds like you've already made a good architectural decision by separating workloads based on their refresh requirements.Since continuous ingestion was too expensive, I wouldn't recommend switching approaches without first ...
Great discussion. I think there is another architectural consideration worth exploring before changing the gateway configuration.Does the 15-minute freshness requirement apply to all 80 tables, or only to a subset of business-critical tables?If only ...
Interesting, the public internet issue does sound very similar to the original case.For the S3 403, though, I would troubleshoot it separately first because it could be a Unity Catalog / AWS authorization issue rather than the same outbound restricti...
One additional diagnostic could help distinguish a workspace-level trial restriction from a standard serverless egress policy.Since serverless network policies currently require Enterprise tier, and the default policy is only applied to Enterprise wo...
