Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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::Redshift::Cluster: Endpoint.Address not available during creation in cnf template with Fn::GetAtt #29353

Closed
maxhoheiser opened this issue Mar 4, 2024 · 4 comments
Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@maxhoheiser
Copy link

maxhoheiser commented Mar 4, 2024

Describe the bug

When deploying a new redshift cluster, and referencing the Cluster.Endpoint.Address via "Fn::GetAtt": ["Endpoint.Address"] the deployment fails with the error: Requested attribute Endpoint.Address does not exist.

Expected Behavior

Cloudformation handles waiting for cluster status created to return Endpoint.Address

Current Behavior

Deployment fails due to: FirehoseDeliveryStream Attribute 'Endpoint.Address' does not exist
deployment.log

Reproduction Steps

stack to deploy cnf template:
TestKinesisFirehoseScenarioNew.template.json

  1. create app.py from this gist: Python CDK app to deploy: app.py
  2. create cdk.json:
    {
      "app": "python3 app.py"
    }
  3. synth and deploy the app:
    cdk synth && cdk bootstrap && cdk deploy

Possible Solution

If I split the stack and first deploy the redshift cluster, the Endpoint.Address is available for the second stack.
No response

Additional Information/Context

No response

CDK CLI Version

2.130.0

Framework Version

No response

Node.js Version

v18.14.2

OS

MacOs 14

Language

Python

Language Version

Python 3.11

Other information

there is already an unresolved closed bug report for this: #14524
this is my attempt to bring attention to this.

@maxhoheiser maxhoheiser added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Mar 4, 2024
@github-actions github-actions bot added the @aws-cdk/aws-redshift Related to Amazon Redshift label Mar 4, 2024
@maxhoheiser maxhoheiser changed the title (module name): (short issue description) AWS::Redshift::Cluster: Endpoint.Address not available during creation in cnf template with Fn::GetAtt Mar 4, 2024
@pahud
Copy link
Contributor

pahud commented Mar 4, 2024

How did you create the cluster? Can you share your CDK code snippet? If you use aws-redshift-alpha, it does come with clusterEndpoint as type Endpoint where you can reference its address and port.

@pahud pahud added p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed needs-triage This issue or PR still needs to be triaged. labels Mar 4, 2024
@maxhoheiser
Copy link
Author

@pahud thanks for the quick reply!

Here is the CDK app: https://gist.github.com/maxhoheiser/e81bb62563b15700c0bc3a185817cc2c that I use to deploy the stack (if I split it into two separate stacks, and first deploy the redshift cluster and then the firehose stream it works, but I would very much like to deploy it as a single stack)

I will check out the alpha L2 construct, but due to dependencies in our current code base, I won't be able to use it in production.

@pahud
Copy link
Contributor

pahud commented Mar 4, 2024

OK now I can see you are provisioning it with CfnCluster

https://gist.github.com/maxhoheiser/e81bb62563b15700c0bc3a185817cc2c#file-firehose_redshift_cdk_app-py-L126

If you look at the cdk python reference, you should be able to access its endpoint attribute.

https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_redshift/CfnCluster.html#aws_cdk.aws_redshift.CfnCluster.endpoint

@pahud
Copy link
Contributor

pahud commented Mar 4, 2024

Converting to discussion as this doesn't seem to be a bug.

@aws aws locked and limited conversation to collaborators Mar 4, 2024
@pahud pahud converted this issue into discussion #29355 Mar 4, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
@aws-cdk/aws-redshift Related to Amazon Redshift bug This issue is a bug. p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants