Skip to content
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.

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

aws-cdk-lib.aws_redshiftserverless module - Query History Empty in the AWS Console #26773

Open
entest-hai opened this issue Aug 16, 2023 · 1 comment
Labels
@aws-cdk/aws-redshiftserverless Related to AWS Redshift Serverless bug This issue is a bug. effort/medium Medium work item – several days of effort p2

Comments

@entest-hai
Copy link

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

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

@entest-hai entest-hai added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Aug 16, 2023
@github-actions github-actions bot added the aws-cdk-lib Related to the aws-cdk-lib package label Aug 16, 2023
@entest-hai entest-hai changed the title aws-cdk-lib.aws_redshiftserverless module aws-cdk-lib.aws_redshiftserverless module - Query History Empty in the AWS Console Aug 16, 2023
@pahud
Copy link
Contributor

pahud commented Aug 16, 2023

I checked the CFN doc for AWS::RedshiftServerless::Namespace and AWS::RedshiftServerless::Workgroup but I can't find any relevant property for this configuration.

We probably need to make sure cloudformation does support that before we are allowed to use CDK L1 construct to enable that.

I assume this feature is probably not supported by CFN yet.

@pahud pahud added p2 effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Aug 16, 2023
@moelasmar moelasmar added @aws-cdk/aws-redshiftserverless Related to AWS Redshift Serverless and removed aws-cdk-lib Related to the aws-cdk-lib package labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-redshiftserverless Related to AWS Redshift Serverless bug This issue is a bug. effort/medium Medium work item – several days of effort p2
Projects
None yet
Development

No branches or pull requests

3 participants