Failed to write to configured query result bucket due to missing s3:ListBucket permission on the bucket

The error you're encountering suggests that there's an issue with the permissions for the S3 bucket where your query results are being saved. While the result S3 bucket setting is indeed typically global within a collaboration, the permissions required to access and write to that bucket can sometimes vary depending on the specific actions being performed.

The s3:ListBucket permission is crucial for many S3 operations, including writing new objects to the bucket. This permission allows the service to list the contents of the bucket, which is often necessary before writing new data.

There are a few potential reasons why you might be seeing this error for some templates but not others:

1. Role or policy changes: It's possible that the IAM role or policy associated with the service trying to write to the S3 bucket has been modified recently, affecting only the newer templates.

2. Bucket policy changes: The S3 bucket's policy might have been updated, potentially restricting access for certain operations.

3. Cross-account access: If the S3 bucket is in a different AWS account than the one running the queries, there might be additional permission requirements that aren't met for the new template.

4. Template-specific permissions: Some templates might require additional permissions based on the complexity or nature of the query being run.

To resolve this issue, you should:

1. Check the IAM role or policy associated with the service running these queries. Ensure it has the necessary permissions, including s3:ListBucket, for the result S3 bucket.

2. Review the S3 bucket policy to make sure it allows the appropriate access from the AWS account or IAM role running the queries.

3. If cross-account access is involved, verify that all necessary permissions are in place on both the bucket side and the IAM role side.

4. Consider temporarily granting broader S3 permissions (like s3:* for testing purposes) to isolate whether it's specifically an s3:ListBucket issue or a broader permissions problem.

Remember to follow the principle of least privilege when setting up permissions, granting only the necessary access required for the operation.
Sources
Why Does S3 Return 403 Instead of 404 When the Object Doesn’t Exist? | AWS re:Post
How Amazon S3 authorizes a request for a bucket operation - Amazon Simple Storage Service
Unlocking AWS Console: Diagnosing Errors with Amazon Q Developer | AWS DevOps & Developer Productivity Blog