Skip to main content

Redpanda Terraform Provider returned "tcp <private link endpoint IP>:443: i/o timeout" when enabled Private Link in Cloud

  • Updated

Problem Statement

After deploying a Redpanda cluster with a private network and setting up a Private Link, running the Redpanda Terraform provider may fail and receive "tcp IP_ADDRESS:443: i/o timeout " error message. That message indicates that the port 443 is not open.

Solution

To solve the issue, the "Connect Console" on the PrivateLink settings must be enabled to open the port 443, then set your VPC Security Group and/or ACL to open the port on your VPC side.
For the Redpanda side, you can set this either via the Cloud UI or API.

  • For the UI,  please log in to the UI, then click the "Redpanda Network" link from the Overview page. On the PrivateLink settings page, toggle and turn on the "Connect Console" switch, then press the "Enable" button.
    If you cannot find the PrivateLink settings page in the UI, please try the following URI directory. https://cloudv2.redpanda.com/clusters/<cluster_id>/settings/pl.
  • For the REST API, please refer to the doc to set connect_console: true on the REST API endpoint. Here is an example.
CLUSTER_PATCH_BODY=`cat << EOF
{
"aws_private_link": {
"connect_console": true
}
}
EOF`

curl -vv -X PATCH \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $AUTH_TOKEN" \
-d "$CLUSTER_PATCH_BODY" $PUBLIC_API_ENDPOINT/v1beta2/clusters/$CLUSTER_ID

Notes

Due to a UI bug, you may not see if "Connect Console" was enabled on the Settings page. In that case, please check the current settings using the API call.


If you still see this message, please reach out to Redpanda Support.