> For the complete documentation index, see [llms.txt](https://docs.e6data.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/product-documentation/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-unity-catalog.md).
# Configure Cross-account Catalog to Access Unity Catalog
To connect your e6data Workspace to a unity catalog and S3 data source in a different cloud account, please follow the steps below:
{% hint style="info" %}
This guide assumes:
* the e6data Workspace (clusters/compute) is installed in a cloud account named **Account A.**
* the unity catalog & S3 data stores are located in a different cloud account named **Account B.**
* Both **Account A** & **Account B** are in the same AWS region.
{% endhint %}
### Step 1: Create policies to access S3 data sources in **Account B**
1. Sign in to the **Account B** AWS Console.
2. Search for **IAM.**
3. In the navigation pane, choose **Roles**.
4. Click **Create role**.
5. Under **Select type of trusted entity**, choose **AWS account**.
6. Click on **Another AWS account** to enter the **Account ID**.
7. Enter the account ID of **Account A**.
8. Click **Next: Permissions**.
9. Attach the below policy to the role.
10. Replace the ARN of the S3 bucket/s containing the data.
**S3 & Hive Policy**
```
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:GetObject",
"s3:ListBucket",
"s3:GetObjectVersion"
],
"Resource": [
"arn:aws:s3:::EXAMPLE-BUCKET/*",
"arn:aws:s3:::EXAMPLE-BUCKET"
],
"Effect": "Allow"
}
]
}
```
* Click **Next: Add tags**.
* Optional: You can add tags to the role. Or leave these fields blank, and click **Next: Review**.
* Enter a **Role name** that follows your organization's naming convention.
* Click **Create role**.
1. Copy the ARN of the newly created role.
Step 2: Configure access in **Account A**
* In **Account B**, copy the ARN of the role created in
* Sign in to the **Account A** AWS Console.
* Create a policy and choose the **JSON** view.
* Replace the ARN with the ARN of the role created in **Account B**.
* Copy & paste the edited
* In **Account A**, attach the policy created in Step 3 to:
e6data\_engine\_role (e6data-workspace-\-engine-role)
**STS Policy**
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "sts:AssumeRole",
"Resource": "arn:aws:iam::ACCOUNT_B_ID:role/ROLENAME"
}
]
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.e6data.com/product-documentation/catalogs/create-catalogs/cross-account-catalog-access/configure-cross-account-catalog-to-access-unity-catalog.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.