Summary: 

To allow Redpanda to fully and completely manage your AWS cluster Private Link enabled, or to enable Private Link on an existing AWS cluster in the future, including cross-region Private Link that allows consumer endpoints to access a Redpanda cluster from a different AWS region, you will need to review and take the actions described below.

Severity: 

Low

Redpanda Products Affected:

• Redpanda Cloud - AWS BYOC
• Redpanda Cloud - AWS BYOVPC

Release Affected:

All releases

Identification:

This applies to any Redpanda BYOC or BYOVPC Cluster on AWS with Private Link enabled. To confirm if Private Link is enabled, refer to the Cluster Settings Page within the Cloud UI for each cluster.

Impact: 

Failure to grant the necessary new permissions (vpce:AllowMultiRegion, elasticloadbalancing:DescribeListenerAttributes) will prevent Redpanda from upgrading affected AWS clusters with new releases and will also block the enablement of cross-region Private Link. However, Private Link connectivity itself will remain unaffected.

Action required: 

The action required to address this depends on your cluster type:

• AWS BYOC Clusters: Run the cluster creation command again, replacing with your cluster's ID:

rpk cloud byoc aws apply --redpanda-id=''

• AWS BYOVPC Clusters: You must update your customer-managed resources. Refer to one of the following:
  • The latest Redpanda Terraform BYOVPC module
  • Redpanda cloud examples
  • The Redpanda documentation

Questions? If you have any questions on this TSB, or need further guidance, please contact Redpanda Support