From 0ad86f5e269194a8fc36ed8a1bfe0098c219084d Mon Sep 17 00:00:00 2001 From: AyeshaFirdausTG Date: Wed, 15 Apr 2026 01:17:11 +0530 Subject: [PATCH] DOC-3161-aws-role-arn-4.3 --- modules/querying/pages/data-types.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/modules/querying/pages/data-types.adoc b/modules/querying/pages/data-types.adoc index a6abdcbb..f75276ad 100644 --- a/modules/querying/pages/data-types.adoc +++ b/modules/querying/pages/data-types.adoc @@ -620,6 +620,15 @@ set s3_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 `` and `` with your actual AWS credentials, and `` 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=""; +---- +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: