You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, this is not an issue but I am trying to access aws glue catalog using presto which is situated in a different account. I can access the Glue catalog in the account where the presto instance is running using the below configuration:
connector.name=hive-hadoop2
hive.metastore = glue
While looking at the properties list. I don't seem to find any option to provide access/secret key to access Glue in a different account. Is this a limitation?
The text was updated successfully, but these errors were encountered:
This is a current limitation, but should be easy to add. If you're interested in working on this yourself, it should be just adding them to GlueHiveMetastoreConfig and using them in GlueHiveMetastore to create the AWS client (with a BasicAWSCredentials).
In the latest 310 release, we did add hive.metastore.glue.iam-role which allows you to choose the IAM role to assume for connecting to Glue. I'm not sure if this helps in your situation.
Well, this is not an issue but I am trying to access aws glue catalog using presto which is situated in a different account. I can access the Glue catalog in the account where the presto instance is running using the below configuration:
connector.name=hive-hadoop2
hive.metastore = glue
While looking at the properties list. I don't seem to find any option to provide access/secret key to access Glue in a different account. Is this a limitation?
The text was updated successfully, but these errors were encountered: