Hi Daniel, I’m sorry to hear about that. We don’t differentiate between Serverless and regular Redshift clusters from our end; The connection to either of them is done in the same way, as described in
Create and Amazon Redshift Data Source.
It is unusual to see a connection fail like that, especially if nothing was changed on either end. Still, I would recommend double checking the configuration of your Redshift instance - e.g., ensure the access rights haven’t changed, that it doesn’t contain any features not supported by GoodData, that IP Whitelists are configured correctly, etc. The article I shared above is a good resource for ensuring all requirements are met.
Are you able to check your browser’s Developer Tools for the error message that is displayed on the Console when you try to connect to the serverless instance via the Data Source manager? If so, could you share the
traceId that accompanies the message?