.NET CDK 1.8 ClusterEndpoint does not return port number
See original GitHub issueLike with #2711, .NET CDK 1.8 DatabaseCluster.ClusterEndpoint.Port
is of type double
, precluding getting endpoint port back.
The workaround described in #2711 can be used to mitigate the issue.
Reproduction Steps
Use .NET CDK 1.8 to create RDS Aurora cluster.
Error Log
Environment
- CLI Version :1.8
- Framework Version: .NET Core 2.1
- OS :WIndows 10
- Language :.NET C#
Other
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
class DatabaseCluster (construct) · AWS CDK
You are not viewing the latest version. ... Create a clustered database with a given number of instances. ... port? number, What port...
Read more >aws-cdk.aws-ec2 - PyPI
The CDK Construct Library for AWS::EC2. ... PRIVATE_WITH_NAT ) - instances in private subnets are not directly routable from the Internet, and connect...
Read more >How to use the @aws-cdk/core.Output function in ... - Snyk
Use Snyk Code to scan source code in minutes - no build needed - and fix ... public export(): DatabaseClusterRefProps { return {...
Read more >How to upgrade CDK from CDKv1 to CDKv2 in an existing ...
txt is used. The data platform itself is created in a so-called restricted AWS environment, which means that there is no public internet...
Read more >Redshift Cluster Default Port | Trend Micro
To change your Redshift database cluster endpoint port follow the steps outlined in the Remediation/Resolution section. 06 Repeat step no. 4 and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In case anyone else ends up in this question, the mystery number comes form the numeric Token representation: https://docs.aws.amazon.com/cdk/latest/guide/tokens.html
To solve this in my case, I used the
cdk.Token
class to convert the numeric Token into a string Token:This synthesizes as
"Fn::ImportValue": "FoobarInfra:ExportsOutputFnGetAttDatabaseB269D8BBEndpointPort3ACB3F51"
, which ends with the correct value in the ECS Task Container.It’s a nice workaround, @marioizquierdo, thank you, but it also shows the problem is still there and the issue needs trip be reopened @RomainMuller.