Redshift Federated Query Secrets Manager

0

Hi All,

I hope everyone is doing well! I am attempting to create a federated query between Redshift and Aurora Postgres 14.

I am following the instructions on this page: https://docs.aws.amazon.com/redshift/latest/dg/getting-started-federated.html

I have created a Secret in Secret Manager containing a user with read-only permission to the Aurora Postgres.

At first, I could only view the Secret in Redshift once I added the following Key and Value: {RedshiftQueryOwner: 21 character string + email address}. I found this Key and Value from a Redshift Temporary Credentials secret when I was attempting to authenticate with temporary credentials (Redshift Query Editor > Change Connection > Create a New Connection > Temporary Credentials).

Whenever I use this secret, I get the following error: Redshift endpoint doesn't exist in this region.

Additionally, when I attempt to run the following query:

CREATE EXTERNAL SCHEMA test FROM POSTGRES DATABASE 'XXXXXXXXX' SCHEMA 'YYYYYYY' URI 'AAAAAAAAAAAAAAAAA.BBBBBBBBBBBBB.us-west-2.rds.amazonaws.com' PORT #### IAM_ROLE 'arn:aws:iam::AAAAAAAAAAAAA:role/BBBBBBBBBBBBBB' SECRET_ARN 'arn:aws:secretsmanager:us-CCCCC-D:AAAAAAAAAAAAA:secret:DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD'

The test schema has no resources to display.

In relation, to this question - https://repost.aws/questions/QU57rRRhZISXaDpv2KhKocMw/redshift-federated-query-error-code-25000 - I have enabled the Enhanced VPC Routing option.

I'm trying to figure out how to resolve this issue and would appreciate any assistance.

Best

No hay respuestas

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas