aws-cdk-lib.aws_redshiftserverless module - Query History Empty in the AWS Console
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the bug
When creating an Amazon Redshift Serverless namespace and workgroup, the Query History in the AWS console is empty. This is the Query History in the AWS Console. However, when creating Amazon Serverless manually, the Query History in the AWS console is fully detailed information.
I think that when creating Redshift Serverelss by CDK or CloudFormation (L1 Construct), it does not enable monitoring query history from the AWS Console
### Expected Behavior
Query History should show historical queries
### Current Behavior
Query History is empty from the AWS Console
### Reproduction Steps
Just create a simple Amazon Redshift Serverless like below
```ts
export class RedshiftServerlessStack extends Stack {
constructor(scope: Construct, id: string, props: RedshiftServerlessProps) {
super(scope, id, props);
// security block this
const namespace = new aws_redshiftserverless.CfnNamespace(
this,
"RedshiftNameSpace",
{
namespaceName: "demo",
adminUsername: "admin",
adminUserPassword: "Admin2023",
dbName: "demo",
defaultIamRoleArn: props.defaultRole.roleArn,
iamRoles: props.roles.map((role) => role.roleArn),
logExports: ["userlog", "connectionlog", "useractivitylog"],
}
);
const workgroup = new aws_redshiftserverless.CfnWorkgroup(
this,
"RedshiftWorkGroup",
{
workgroupName: "demo",
baseCapacity: 32,
namespaceName: "demo",
subnetIds: props.vpc.publicSubnets.map((subnet) => subnet.subnetId),
publiclyAccessible: false,
securityGroupIds: [props.sg.securityGroupId],
}
);
workgroup.addDependency(namespace);
}
}
```
### Possible Solution
_No response_
### Additional Information/Context
I do not know
### CDK CLI Version
2.87.0
### Framework Version
typescript
### Node.js Version
v18.16.1
### OS
Amazon 2023
### Language
Typescript
### Language Version
TypeScript 5.1.3
### Other information
_No response_
Contributor guide
Research direction
Start by reproducing the TypeScript stack and comparing its generated CloudFormation with a manually created Redshift Serverless namespace and workgroup. Inspect the aws_redshiftserverless L1 construct schema and available resource properties to identify whether query history configuration is represented, then verify the console behavior and add focused coverage if a CDK change is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100