
Learn how to establish cross-account access between Amazon Redshift and SageMaker Studio using VPC peering, IAM role chaining, and SourceIdentity for secure multi-account ML workflows.


<div><p>This article provides a step-by-step guide to establish cross-account access between Amazon Redshift and Amazon SageMaker Studio using VPC peering.</p><ul><li>Set up SageMaker Studio with VPCOnly mode in consumer account for security</li><li>Enable SourceIdentity on SageMaker domain to propagate user profile names</li><li>Create IAM role in Redshift producer account for SageMaker to assume</li><li>Update SageMaker execution role to assume Redshift producer account role</li><li>Establish VPC peering connection between Redshift and SageMaker VPCs</li><li>Configure route tables and VPC endpoints for secure connectivity</li><li>Query Redshift from SageMaker Studio using AWS SDK for pandas library</li><li>Solution enables cross-account data access without manual data movement</li></ul><p>This approach allows organizations with multi-account architectures to securely access Redshift data from SageMaker Studio while maintaining audit trails through CloudTrail and user identity tracking.</p></div>


Related articles