Hello, We are experiencing a connectivity issue between Good Data Cloud and our Redshift via AWS Private Link. I've already reached out to Good Data support (129706), but this is directly affecting our end users.

Hello, I'm sorry to hear about the connectivity issue between GoodData Cloud and your Redshift instance via AWS PrivateLink. Based on the knowledge sources, here are some key points and recommendations: 1. PrivateLink Setup Steps: Ensure that all steps for AWS PrivateLink integration have been followed, including creating a private network load balancer, setting up the VPC endpoint service, adding the correct GoodData account ID as an allowed principal, and permitting the required AWS subnets in your security groups. After this, GoodData support should provide you with a DNS to use as the host name for your data source connection in GoodData Cloud. If you are using a cross-region setup, additional configuration is required on both sides. Please double-check these steps as outlined in the documentation: [Use AWS PrivateLink](https://www.gooddata.com/docs/cloud/connect-data/use-aws-privatelink/) and confirm with support that all configurations are correct. 2. Common Issues: - Double-check for any typos or extra spaces in the endpoint URL or DNS name, as this has caused issues for other users in the past. - Ensure that the security groups and network ACLs allow traffic from the GoodData subnets for your region. - If you are using non-prod environments, make sure that the routing and endpoint services are set up for each environment as needed. Sometimes, a separate VPC endpoint or endpoint service may be required for each environment, especially if they reside in different VPCs or regions. 3. Troubleshooting: If you receive errors such as "Cannot reach the URL" or 400 status codes, check the trace ID in your logs and share it with GoodData support for further investigation. Also, verify that the Redshift instance is accessible from the PrivateLink endpoint and that all necessary permissions are in place. 4. Support Engagement: Since you have already reached out to GoodData support (ticket 129706), continue to monitor their updates. They may need additional information such as trace IDs, endpoint URLs, or screenshots to assist you further. If you haven't already, provide them with as much detail as possible to expedite troubleshooting. If you need more detailed, environment-specific guidance, please continue working with GoodData support, as they can access your account details and logs directly. If you have any specific error messages or trace IDs, sharing those here may help identify the root cause more quickly. For more details on the setup and troubleshooting, refer to the official documentation: [Use AWS PrivateLink](https://www.gooddata.com/docs/cloud/connect-data/use-aws-privatelink/) and related community discussions. Let me know if you have any specific error messages or need clarification on any of the steps above.