aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Redshift Amazon Q Query Editor - Custom Context -

Open
#2,328 0 comments 0 reactions 0 assignees View on GitHub
Coverage
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::Redshift::Cluster

### Resource name

_No response_

### Description

As of 2025-05-29, custom context json files can only be submitted through QueryEditor v2 console and using a QueryEdtior admin allowed IAM role.

No current support for CLI or cloudformation (or boto3 but that makes sense)
I dont feel comfortable giving a human 'admin access' to QueryEditorv2.

Ideally if there was CLI or cfn support, we could of used an assigned repo and cfn-assigned IAM role to run these Custom Context json files. Since there is not , we are kinda outta luck.
basically an admin user would have to manually upload these json files from within the console.

Can also only upload one json file. Would expect ability to upload multiple individual files pertaining to different objects.
Could work around by packaging up a files, but since no programmatic support to upload. Cant.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the AWS::Redshift::Cluster coverage and the Query Editor v2 custom context requirements described here. Define what CloudFormation or CLI support should accept, including multiple JSON files, and consider the work complete when custom context can be uploaded without a console admin role.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.