This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
AWS::Redshift::Cluster: Endpoint.Address not available during creation in cnf template with Fn::GetAtt #29353
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.
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 returnEndpoint.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
app.py
from this gist: Python CDK app to deploy: app.pycdk.json
: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.
The text was updated successfully, but these errors were encountered: