Hi there @AWS-User-8556114,
This could be a mishap in the configuration of the Redshift connector on the Canvas service side. Can you try to forcefully close the Canvas app by deleting the connector first, then logging out of Canvas and/or by deleting the app (by going into the AWS Management Console, SageMaker, your domain, your profile, and deleting the app with type
Canvas), then creating it again?
Alternatively, I'd have to ask you to reach out to Support so that they can help you troubleshoot this by looking into your configuration.
Redshift ML / SageMaker - Deploy an existing model artifact to a Redshift ClusterAccepted Answerasked 2 years ago
What's the best way to send real-time data to Amazon Redshift?Accepted Answerasked 2 years ago
Redshift Data API not recognized by Boto3Accepted Answerasked 2 years ago
SageMaker Canvas connect Redshift failedAccepted Answer
Glue ETL Job with external connection to Redshift - filter then extract?Accepted Answerasked 4 years ago
SageMaker Canvas failed to import the Redshift Data
Should SageMaker Canvas region and S3 region be the same?Accepted Answerasked 2 months ago
AWS Glue load data from S3 to Redshiftasked 4 months ago
Using redshift-data boto3 to make cross account redshift callsasked 8 months ago
Redshift Data Sharing - Play and PauseAccepted Answerasked 2 years ago