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

Requested attribute Endpoint.Address does not exist in schema for AWS::Redshift::Cluster #14524

Closed
mydarpa opened this issue May 4, 2021 · 3 comments
Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. needs-reproduction This issue needs reproduction. p2

Comments

@mydarpa
Copy link

mydarpa commented May 4, 2021

❓ General Issue

The Question

I deployed a Redshift cluster and I would like to export the hostname of the endpoint like this:

cluster = redshift.Cluster(
            self, "redshift-cluster",
            vpc=vpc,
            cluster_name="mycluster",
            cluster_type=redshift.ClusterType.MULTI_NODE,
            number_of_nodes=4,
            logging_bucket=cluster_logging_bucket,
            security_groups=[cluster_security_group],
            master_user=redshift.Login(
                master_username="master",
            ),
            roles=[access_role],
            port=5439,
            node_type=redshift.NodeType.DC2_LARGE,
            publicly_accessible=True,
            subnet_group=redshift.ClusterSubnetGroup(
                self, 'subnet-group',
                vpc=vpc,
                vpc_subnets=ec2.SubnetSelection(subnet_type=ec2.SubnetType.PUBLIC),
                description="public subnet")
        )

core.CfnOutput(
            self, "cluster-hostname",
            value=cluster.cluster_endpoint.hostname,
            export_name="cluster-hostname"
        )

However I get the error:

Requested attribute Endpoint.Address does not exist in schema for AWS::Redshift::Cluster

The same stack was deployed some days ago in another account without problems. According to the documentation this property is valid for the class Endpoint [1] and the Endpoint.Address attribute still exists in CloudFormation [2].

[1] https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-redshift.Endpoint.html
[2] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-redshift-cluster.html#aws-resource-redshift-cluster-return-values

Environment

  • CDK CLI Version: 1.72.0
  • Module Version: aws-cdk.aws-redshift==1.72.0
  • Node.js Version:
  • OS:
  • Language: Python

Other information

This issue is only for Endpoint exports. I don't get any problems with other exports like:

core.CfnOutput(
            self, "password-arn",
            value=cluster.secret.secret_arn,
            export_name="password-arn"
        )
@github-actions github-actions bot added the @aws-cdk/aws-redshift Related to Amazon Redshift label May 4, 2021
@NGL321 NGL321 added bug This issue is a bug. needs-reproduction This issue needs reproduction. p2 labels Jul 24, 2021
@NGL321
Copy link
Contributor

NGL321 commented Jul 24, 2021

Hey @mydarpa,

Thanks for reporting this. I am unsure as to why it was not marked as a bug report, but I have adjusted it. Someone will take a look into this as soon as we are able.

@github-actions
Copy link

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jul 24, 2022
@kayzbui
Copy link

kayzbui commented Feb 29, 2024

I encountered a similar issue when attempting to create a Redshift Cluster and establish an SSM reference to Cluster.Endpoint.Address. To resolve this, I divided the deployment into two stages. Initially, I created the Redshift Cluster, followed by a separate deployment for setting up the SSM reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. needs-reproduction This issue needs reproduction. p2
Projects
None yet
Development

No branches or pull requests

4 participants