Skip to content

DOC-3161-aws-role-arn-4.3 #328

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.

Sign up for GitHub

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

Open
AyeshaFirdausTG wants to merge 1 commit into
base: 4.3.0-dev
Choose a base branch
from
Open

DOC-3161-aws-role-arn-4.3 #328

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions modules/querying/pages/data-types.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -620,6 +620,15 @@ set s3_region = <REGION>;

These session parameters should be set within the GSQL Editor to enable read/write access to the specified S3 bucket for query results. Replace `<AWS_KEY_ID>` and `<AWS_ACCESS_KEY>` with your actual AWS credentials, and `<REGION>` with your S3 bucket's region (for example, `us-west-2`). If you don't set `s3_region`, it defaults to `us-east-1`.

In 4.3, you can also authenticate using AWS role assumption. Set the `s3_assume_role` session parameter to the role ARN:

[source, gsql]
----
set s3_assume_role="<RoleARN>";
----
Both methods provide identical functionality.


==== Output
Since S3 is a shared storage system, multiple nodes in a cluster can upload to the same bucket.
To avoid conflicts and ensure unique output files, the S3 path may include a suffix such as:
Expand Down