Deregistering Amazon Redshift clusters and namespaces from the Amazon Glue Data Catalog - Amazon Redshift
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon Redshift will no longer support the creation of new Python UDFs starting November 1, 2025. If you would like to use Python UDFs, create the UDFs prior to that date. Existing Python UDFs will continue to function as normal. For more information, see the blog post .

Deregistering Amazon Redshift clusters and namespaces from the Amazon Glue Data Catalog

You can deregister a provisioned cluster or serverless namespace from the Amazon Glue Data Catalog using the Amazon Redshift console or the Amazon CLI. Data warehouses that you deregister from the Amazon Glue Data Catalog are only removed from the Amazon Glue Data Catalog itself. The warehouses remain part of your Amazon Redshift account. Additionally, the catalog remains in Amazon Glue and must be manually removed. When you remove the catalog from Amazon Glue, the managed workgroup associated with it is also removed.

Deregistering using the Amazon Redshift console

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshiftv2/.

  2. Navigate to the serverless namespace or provisioned cluster that you want to deregister and select it.

  3. From the namespace or cluster’s details page, select Deregister from Amazon Glue Data Catalog from the Actions drop-down menu. This option only appears if you’ve chosen a data warehouse that’s already been registered to the Amazon Glue Data Catalog.

  4. Enter the account ID that owns the catalog holding your cluster or namespace and choose Deregister.

Deregistering using the Amazon CLI

To deregister a cluster or namespace from the Amazon Glue Data Catalog using the Amazon CLI, use the deregister-namespace command with the following options:

  • namespace-identifier: An object with the unique identifier of the cluster or namespace you’re deregistering. This object is different depending on whether you’re deregistering a provisioned cluster or a serverless namespace. Consider the following:

    • For provisioned clusters, you provide a ProvisionedIdentifier object, which contains a ClusterIdentifier object with the unique identifier of the cluster you’re deregistering.

    • or serverless namespaces, you provide a ServerlessIdentifier object, which contains a NamespaceIdentifier object with the unique identifier of the namespace you’re deregistering, as well as a WorkgroupIdentifier object with the unique identifier of the workgroup associated with that namespace.

  • consumer-identifiers: An array with a single element, containing the unique identifier of the account you’re deregistering the cluster or namespace from.

The following example deregisters the mySampleNamespace serverless namespace from the account ID 012345678910. 

aws redshift deregister-namespace /
--namespace-identifier {ServerlessIdentifier: {NamespaceIdentifer: mySampleNamespace, WorkgroupIdentifier: mySampleWorkgroup}} /
--consumer-identifiers [012345678910]