Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing AWS Glue Catalog in different account using presto #726

Closed
niraj8241 opened this issue May 7, 2019 · 1 comment · Fixed by #748
Closed

Accessing AWS Glue Catalog in different account using presto #726

niraj8241 opened this issue May 7, 2019 · 1 comment · Fixed by #748

Comments

@niraj8241
Copy link

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?

@electrum
Copy link
Member

electrum commented May 7, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants