I am most probably missing something, hence the question. Once the AWS resources are set up then you can add the Aurora databases as external schemas in Redshift and start querying. while cross database queries (in ra3 node based clusters) and federated queries individually seem to work, together it seems that they wont work. Allow all outbound traffic in the Redshift cluster security group.Īdding Aurora database as an external schema in Redshift.In Account A create a secret in the SecretsManager and store the Aurora instance credentials.Īllow access to the secret for Account X’s root user(can also be the Redshift role) by adding the below resource policy to the secret. There are two types of snapshots: automated and manual. Cluster Snapshots Point-in-time backups of a cluster. Available on Redshift RA3 node types at no additional cost. In Account A create a Customer managed KMS key and add a grant to the Account X’s root user(can also be the Redshift role) with Decrypt & DescribeKey operations. Redshift Cross-database queries provide the ability to query across databases in a Redshift cluster, regardless of which database you are connected to. Grant select access to innodb_index_stats & innodb_table_stats for the aurora user in the aurora cluster. VPC Peering should be enabled between the accounts.Īmazon Redshift cluster should have a cluster maintenance version that supports federated queries.Īmazon Redshift cluster should have enhanced VPC routing enabled.
#Redshift federated query how to
In this blog I have explained how to setup Redshift to query across multiple Aurora instances cross-account.
Redshift federated query lets you query and analyse data across multiple operational databases directly. Access Amazon Redshift query editor v2 through federated authentication.
0 kommentar(er)
