Unable to connect redshift from emr

1

Hi, I am getting yarn does not exist error when Connecting redshift cluster from emr where both are in same vpc. Is there any connectivity missing or any step that I need to make sure ?

Mark
posta 7 mesi fa234 visualizzazioni
1 Risposta
3
Risposta accettata

Hello,

"FATAL: user "IAM:yarn" does not exist"

Here EMR is considering 'yarn' as a User which in turn trying to authenticate as DBUser using GetClusterCredentials API and add as a suffix for "IAM: ". It might be the case that if the user might not be exist or not provided in your URL. As you get user doest exist, your connectivity seems to be working fine. However, just in case you have not configured already then, You need to update the security group attached to the Redshift cluster to allow incoming traffic from EMR cluster by adding below inbound rules for EMR Master and EMR Slave Security Group and test the connectivity,

telnet redshift-cluster-1.xxxxxxxxx.xxxxxxxx.redshift.amazonaws.com 5439

Then try the following connection/compare with your connection URL,

df1 = spark.read.format("jdbc").option("url", "jdbc:redshift://<redshift endpoint:5439/<Database_Name>?user=<Admin_Username>&password=<Admin_Password>").option("dbtable", "public.category").load()
df1.printSchema()
df1.show()

If a user named DbUser exists in the database, the temporary user credentials have the same permissions as the existing user. If DbUser doesn't exist in the database and AutoCreate is true, a new user named DbUser is created. -

https://docs.aws.amazon.com/redshift/latest/APIReference/API_GetClusterCredentials.html

AWS
TECNICO DI SUPPORTO
con risposta 7 mesi fa
profile pictureAWS
ESPERTO
verificato 7 mesi fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande