# Cross-account Catalog Access

[configure-cross-account-catalog-to-access-gcp-hive-metastore](https://docs.e6data.com/product-documentation/~/revisions/W5MExJCuvHiG1ioEcgOy/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-gcp-hive-metastore "mention")When an organization stores data in multiple cloud accounts, it may not be desirable to create e6data workspaces in each account.

Therefore, **Cross-account Catalog Access** support allows an e6data workspace to access metastores/catalogs irrespective of cloud account. Using this feature helps to reduce complexity and cost since a single e6data Workspace can now access catalogs and data sources in multiple cloud accounts.

{% hint style="info" %}
Please be mindful of the ingress/egress costs incurred & latency introduced when querying across accounts.
{% endhint %}

1. [Configure cross-account access to AWS Hive Metastore](https://docs.e6data.com/product-documentation/~/revisions/W5MExJCuvHiG1ioEcgOy/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-aws-hive-metastore)
2. [Configure cross-account access to AWS Glue](https://docs.e6data.com/product-documentation/~/revisions/W5MExJCuvHiG1ioEcgOy/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-aws-glue)
3. [Configure cross-account access to GCP Hive Metastore ](https://docs.e6data.com/product-documentation/~/revisions/W5MExJCuvHiG1ioEcgOy/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-gcp-hive-metastore) 

{% hint style="warning" %}
There is a known limitation that prevents same-account catalog queries from running after running a query in a cross-account catalog. This issue will be addressed in a future release.

Temporary workarounds:

* Disabling & re-enabling a Workspace allows same-account catalog queries to run again. 
* Maintain separate Workspaces for cross-account catalogs and same-account catalogs.
  {% endhint %}