Amazon Redshift will no longer support the creation of new Python UDFs starting Patch 198. Existing Python UDFs will continue to function until June 30, 2026. For more information, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/).
# Getting started with read-only data sharing in the console
With Amazon Redshift, you can manage data sharing with writes using the console to control access and govern data across Amazon Redshift clusters and AWS accounts. The following sections provide step-by-step instructions on configuring and managing data sharing with writes using the Amazon Redshift console.
Use the Amazon Redshift console to manage datashares created in your account or shared from other accounts.
You need permissions to create, edit, or delete datashares. For information, see [Managing permissions for a datashares in Amazon Redshift](writes-managing-permissions.md).
+ If you are a producer administrator, you can create datashares, add data consumers, add datashare objects, create databases from datashares, edit datashares, or delete datashares from the **CLUSTERS** tab.
From the navigation menu, navigate the **Clusters** tab, choose a cluster from the cluster list. Then do one of the following:
+ Choose the **Datashares** tab, choose a datashare from the **Datashares created in my namespace** section. Then do one of the following:
+ [Create a datashare](datashare-creation.md#create-datashare-console)
When a datashare is created, you can add datashare objects or data consumers. For more information, see [Add datashare objects to datashares](datashare-creation.md#add-datashare-object-console) and [Add data consumers to datashares](datashare-creation.md#add-data-consumer-console).
+ [Editing datashares created in your account](manage-datashare-existing-console.md#edit-datashare-console)
+ [Deleting a datashare created in your account](manage-datashare-existing-console.md#delete-datashare-console)
+ Choose **Datashares** and choose a datashare from the **Datashares from other clusters** section. Then do one of the following:
+ [Create a datashare](datashare-creation.md#create-datashare-console)
+ [Creating databases from datashares](query-datashare-console.md#create-database-from-datashare-console)
+ Choose **Databases** and choose a database from the **Databases** section. Then choose **Create datashare**. For more information, see [Creating databases from datashares](query-datashare-console.md#create-database-from-datashare-console).
**Note**
To view databases and objects within databases or to view datashares in the cluster, connect to a database. For more information, see [Connecting to a database](connect-database-console.md).
# Connecting to a database
With Amazon Redshift, you can establish a connection to your data warehouse cluster and execute SQL queries, load data, or perform administrative tasks. Connecting to a database refers to the process of creating a secure channel between a client application or tool and the Amazon Redshift cluster. The following sections will provide step-by-step instructions on how to connect to an Amazon Redshift database.
Connect to a database to view databases and objects within databases in this cluster or to view datashares.
The user credentials used to connect to a specified database must have the necessary permissions to view all datashares.
If there is no local connection, do one of the following:
+ In the cluster details page, from the **Databases** tab, in the **Databases** or **Datashare objects** section, choose **Connect to database** to view database objects in the cluster.
+ In the cluster details page, from the **Datashares** tab, do one of the following:
+ In the **Datashares from other clusters** section, choose **Connect to database** to view datashares from other clusters.
+ In the **Datashares created in my cluster** section, choose **Connect to database** to view datashares in your cluster.
+ On the **Connect to database** window, do one of the following:
+ If you choose **Create a new connection**, choose **AWS Secrets Manager** to use a stored secret to authenticate access for the connection.
Or, choose **Temporary credentials** to use database credentials to authenticate access for the connection. Specify values for **Database name** and **Database user**.
Choose **Connect**.
+ Choose **Use a recent connection** to connect to another database that you have the necessary permissions.
Amazon Redshift automatically makes the connection.
After a database connection is established, you can start creating datashares, querying datashares, or creating databases from datashares.
# Creating datashares
With Amazon Redshift, you can share live data across Amazon Redshift clusters or AWS accounts using datashares. A datashare is a consumer-producer object that allows you to share live data from your Amazon Redshift cluster with other clusters or AWS accounts. Creating datashares enables secure data sharing while maintaining control over access and ensuring data remains up-to-date. The following sections provide details on creating datashares and adding database objects such as schemas, tables, and views to share live data securely.
## Create a datashare
A datashare is a logical container of database objects, permissions, and consumers. Consumers are Amazon Redshift provisioned clusters or Amazon Redshift Serverless namespaces in your account and other AWS accounts. Each datashare is associated with the database it's created in and only objects from that database can be added. As a producer administrator, you can create datashares on the console and with SQL by following one of the below procedures.
------
#### [ Console ]
On the console, you can create datashares from the **Datashares** tabs in the cluster or namespace details page. After the datashare is created, you can create databases from the datashare on a consumer as a consumer administrator.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. In the cluster or namespace details page, from the **Datashares** tab, in the **Datashares** section, connect to a database if you don't have a database connection. In the **Datashares created in my account** section, choose **Create datashare**. The **Create datashare** page appears.
1. Choose **Create datashare**. You can only create a datashare from a local database. If you haven't connected to the database, the **Connect to database** page appears. Follow the steps in [Connecting to a database](connect-database-console.md) to connect to a database. If there is a recent connection, the **Create datashare** page appears.
1. In the **Datashare information** section, choose one of the following:
+ Choose **Datashare** to create datashares to share data for read or write purpose across different Amazon Redshift data warehouses (provisioned clusters or Serverless endpoints) or in the same AWS account or different AWS accounts.
+ Choose **AWS Data Exchange datashare** to create datashares to license your data through AWS Data Exchange.
1. Specify values for **Datashare name**, **Database name**, and **Publicly accessible**. When you change the database name, make a new database connection.
1. Add objects to your datashare either using the **Scoped permissions** or **Direct permissions** sections. To add objects to a datashare, see [Creating a datashare in Amazon Redshift](writes-creating-datashare.md).
1. In the **Data consumers** section, you can choose to publish to Amazon Redshift, or publish to the AWS Glue Data Catalog, which starts the process of sharing data with Lake Formation. Publishing your datashare to Amazon Redshift means sharing your data with another namespace or Amazon Redshift account that acts as the consumer.
**Note**
Once the datashare is created, you can't edit the configuration to publish to the other option.
1. Choose **Create datashare**.
------
#### [ SQL ]
The following command creates a datashare:
```
CREATE DATASHARE salesshare;
```
At the time of datashare creation, each datashare is associated with a database. Only objects from that database can be shared in that datashare. Multiple datashares can be created on the same database with the same or different granularity of objects. There is no limit on the number of datashares a cluster can create. You can also use the Amazon Redshift console to create datashares. For more information, see [CREATE DATASHARE](r_CREATE_DATASHARE.md).
You can also control security restrictions to the datashare during creation. The following example shows that the consumer with a public IP access is allowed to read the datashare.
```
CREATE DATASHARE my_datashare [PUBLICACCESSIBLE = TRUE];
```
Setting PUBLICACCESSIBLE = TRUE allows consumers to query your datashare from publicly accessible clusters and provisioned workgroups. Leave this out or explicitly set it to false if you do not want to allow it.
You can modify properties about the type of consumers after you create a datashare. For example, you can define that clusters that want to consume data from a given datashare can't be publicly accessible. Queries from consumer clusters that don't meet security restrictions specified in datashare are rejected at query runtime. For more information, see [ALTER DATASHARE](r_ALTER_DATASHARE.md).
------
## Add datashare objects to datashares
You can add database objects of various types on the console and with SQL by following one of the below procedures.
------
#### [ Console ]
You can add objects to your datashare either using **Scoped permissions** or **Direct permissions** sections. Select either **Grant scoped permissions** or **Grant direct permissions** to add objects. Select the **Add** button to add objects. A dialog appears. Perform the following steps:
1. If you select **Grant scoped permissions**, the **Grant scoped permissions** page appears where you can grant scoped permissions at either a database or a schema level. Datashares with scoped permissions have the specified permissions on all current and future objects within the database or schema. For more details see, [Scoped permissions](t_scoped-permissions.md).
1. Next, select **Database scoped permissions** to grant scoped permissions at the database level. When you grant scoped permissions, they apply to the current database while creating the datashare. These permissions can’t be granted to individual objects and are applicable to both existing and new objects (schemas, tables, views, UDFs).
1. Select the scoped permission(s) for the schemas, table or views or user-defined functions. This means all objects in the database have the selected permissions granted to consumers. Select **Grant** to complete granting database scoped permissions.
1. Then, select **Schema scoped permissions** to grant scoped permissions at the schema level. When you grant schema-scoped permissions, all objects added to the schema have the specified datashare permissions.
1. Select the schema you want to add to the datashare from the dropdown. You can select only a single schema at a time. Then, select direct permission(s) you want to grant on the selected schema.
1. Select scoped permission(s) for your schema objects such as tables, views and user-defined functions. Permissions are granted on all matching objects in the schema. These can be either existing objects or those added in the future. When it's applied, you can't remove a permission from an object without revoking the scoped permissions.
1. Select **Grant** to complete granting schema scoped permissions.
1. If you select **Grant direct permissions**, the **Grant direct permissions** page appears where you can grant direct permissions at each objects level such as schema, table, view or user-defined function. To grant direct permissions, you must first add the relevant schemas to the datashare.
1. Next, select **Grant direct permissions** to schemas to apply direct permissions on specific schema. Then, select schema permission(s) for your schema objects such as tables, views and user-defined functions and select the schema you want added to the datashare. Select **Grant** to complete adding schema to the datashare.
1. After you have a schema added to your datashare, you can proceed with adding direct permissions for your schema objects. Select **Grant direct permissions ** again. The **Grant direct permissions** page appears. Then, navigate to the direct permissions tabs for schema objects.
1. Select **Grant direct permissions to tables and views** to grant object level direct permissions on these objects. Select the required direct permission(s) and the required objects from the list. Use the search field to find datashare objects. Select Grant to complete adding tables and views to the datashare.
1. Select **Grant direct permissions to user-defined functions** to grant object level direct permissions on user-defined functions. Select the required direct permission(s) and the required objects from the list. Use the search field to find datashare objects. Select **Grant** to complete adding user-defined functions to the datashare.
1. You can also choose whether you want to **Add future objects**. When you choose to include datashare objects added to the schema, it means that objects added to the schema are added to the datashare automatically.
1. Choose **Add** to complete the section and add the objects. They're listed under the **Datashare objects**.
1. After you add objects, you can select individual objects and edit their permissions. If you select a schema, a dialog appears that asks if you would like to add **Scoped permissions**. This makes it so each existing or added object to the schema has a pre-selected set of permissions, appropriate for the object type. For instance, the administrator can set that all added tables have SELECT and UPDATE permissions, for instance.
1. All datashare objects are listed under the **Scoped permissions** or **Direct permissions** sections.
1. In the **Data consumers** section, you can add namespaces or add AWS accounts as consumers of the datashare.
1. Choose **Create datashare** to save your changes.
After you create the datashare, it appears in the list under **Datashares created in my namespace**. If you choose a datashare from the list, you can view its consumers, its objects, and other properties.
------
#### [ SQL ]
With SQL, the datashare owner must grant USAGE on the schemas they want to add to the datashare. The GRANT is used to grant various actions on the schema, including CREATE and USAGE. The schemas hold shared objects:
```
CREATE SCHEMA myshared_schema1;
CREATE SCHEMA myshared_schema2;
GRANT USAGE ON SCHEMA myshared_schema1 TO DATASHARE my_datashare;
GRANT CREATE, USAGE ON SCHEMA myshared_schema2 TO DATASHARE my_datashare;
```
Alternatively, the administrator can continue to run ALTER commands to add a schema to the datashare. Only USAGE permissions are granted when a schema is added this way.
```
ALTER DATASHARE my_datashare ADD SCHEMA myshared_schema1;
```
After the administrator adds schemas, they can grant datashare permissions on objects in the schema. These can be both read and write permissions. The GRANT ALL sample shows how to grant all permissions.
```
GRANT SELECT, INSERT ON TABLE myshared_schema1.table1, myshared_schema1.table2, myshared_schema2.table1
TO DATASHARE my_datashare;
GRANT ALL ON TABLE myshared_schema1.table4 TO DATASHARE my_datashare;
```
You can continue to run commands like ALTER DATASHARE to add tables. When you do, only SELECT permissions are granted on the objects added.
```
ALTER DATASHARE my_datashare ADD TABLE myshared_schema1.table1, myshared_schema1.table2, myshared_schema2.table1;
```
You can grant scoped permissions to a datashare on all objects of a type within a database or schema. Datashares with scoped permissions have the specified permissions on all current and future objects within the database or schema.
You can view the scope of database-level scoped permissions in [SVV\$1DATABASE\$1PRIVILEGES](r_SVV_DATABASE_PRIVILEGES.md). You can view the scope of schema-level scoped permissions in [SVV\$1SCHEMA\$1PRIVILEGES](r_SVV_SCHEMA_PRIVILEGES.md).
The following is the syntax for granting scoped permissions to datashares. For more information about scoped permissions, see [Scoped permissions](t_scoped-permissions.md).
```
GRANT { CREATE | USAGE | ALTER | DROP } [,...] | ALL [ PRIVILEGES ] }FOR SCHEMAS IN
DATABASE db_name
TO DATASHARE { datashare_name}
GRANT { { SELECT | INSERT | UPDATE | DELETE | DROP | ALTER | TRUNCATE | REFERENCES } [, ...] } | ALL [PRIVILEGES] } }FOR TABLES IN
{SCHEMA schema_name [DATABASE db_name ] | DATABASE db_name }
TO DATASHARE { datashare_name}
GRANT { EXECUTE | ALL [ PRIVILEGES ] }FOR FUNCTIONS IN
{SCHEMA schema_name [DATABASE db_name ] | DATABASE db_name }
TO DATASHARE { datashare_name}
```
------
## Add data consumers to datashares
You can add one or more data consumers to the datashares. Data consumers can be namespaces that uniquely identified Amazon Redshift clusters or AWS accounts.
You must explicitly choose to turn off or turn on sharing your datashare to clusters with public access.
+ Choose **Add namespaces to the datashare**. Namespaces are globally unique identifier (GUID) for Amazon Redshift cluster.
+ Choose **Add AWS accounts** to the datashare. The specified AWS accounts must have access permissions to the datashare.
# Authorizing or removing authorization from datashares
As a producer administrator, choose which data consumers to authorize to access datashares or to remove authorization from. Authorized data consumers receive notifications to take actions on datashares. If you are adding a namespace as a data consumer, you don't have to perform authorization.
Prerequisite: To authorize or remove authorization for the datashare, there must be at least one data consumer added to the datashare.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Datashares**. The datashare list page appears.
1. Choose **In my account**.
1. In the **Datashares in my account** section, do one of the following:
+ Choose one or more consumer clusters that you want to authorize. The Authorize data consumers page appears. Then choose **Authorize**.
If you chose **Publish to AWS Glue Data Catalog** when creating the datashare, you can only grant authorization of the datashare to a Lake Formation account.
For AWS Data Exchange datashare, you can only authorize one datashare at a time.
When you authorize an AWS Data Exchange datashare, you are sharing the datashare with the AWS Data Exchange service and allowing AWS Data Exchange to manage access to the datashare on your behalf. AWS Data Exchange allows access to consumers by adding consumer accounts as data consumers to the AWS Data Exchange datashare when they subscribe to the products. AWS Data Exchange doesn't have read access to the datashare.
+ Choose one or more consumer clusters that you want to remove authorization from. Then choose **Remove authorization**.
After data consumers are authorized, they can access datashare objects and create a consumer database to query the data.
After authorization is removed, data consumers lose access to the datashare immediately.
# Managing datashares from other accounts as a consumer
## Removing association of datashare from data consumers
As a consumer administrator, you can remove association of datashares from data consumers.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Datashares**. The datashare list page appears.
1. Choose **From other accounts**.
1. In the **Datashares from other accounts** section, choose the datashare to remove association from data consumers.
1. In the **Data consumers** section, choose one or more data consumers to remove association from. Then choose **Remove association**.
1. When the Remove association page appears, choose **Remove association**.
After association is removed, data consumers will lose access to the datashare. You can change the data consumer association at any time.
## Declining datashares
As a consumer administrator, you can reject any datashare whose state is [available or active](https://docs.aws.amazon.com/redshift/latest/dg/access-cross-account.html#manage-status). After you reject a datashare, consumer cluster users lose access to the datashare. Amazon Redshift doesn't return the rejected datashare if you call the `DescribeDataSharesForConsumer` API operation. If the producer administrator runs the `DescribeDataSharesForProducer` API operation, they will see that the datashare was rejected. Once a datashare is rejected, the producer administrator can authorize the datashare to a consumer cluster again, and the consumer administrator can choose to associate their AWS account with the datashare or reject it.
If your AWS account has an association to a datashare and a pending association to a datashare that's managed by Lake Formation, rejecting the datashare association that's managed by Lake Formation also rejects the original datashare. To reject a specific association, the producer administrator can remove authorization from a specified datashare. This action doesn't affect other datashares.
To reject a datashare, use the AWS console, the API operation `RejectDataShare`, or `reject-datashare` in the AWS CLI.
**To reject a datashare using the AWS console:**
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. In the navigation menu, choose **Datashares**.
1. Choose **From other accounts**.
1. In the **Datashares from other accounts** section, choose the datashare you want to decline. When the **Decline datashare** page appears, choose **Decline**.
After you decline the datashares, you can't revert the change. Amazon Redshift removes the datashares from the list. To see the datashare again, the producer administrator must authorize it again.
# Managing existing datashares
With Amazon Redshift, you can manage existing datashares to control access to your data in an Amazon Redshift cluster. The following sections provide step-by-step guidance on managing datashares in your Amazon Redshift environment.
## Viewing datashares
View datashares from the **DATASHARES** or **CLUSTERS** tab.
+ Use the **DATASHARES** tab to list datashares in your account or from other accounts.
+ To view datashares created in your account, choose **In my account**, then choose the datashare you want to view.
+ To view datashares that are shared from other accounts, choose **From other accounts**, then choose the datashare you want to view.
+ Use the **CLUSTERS** tab to list datashares in your cluster or from other clusters.
Connect to a database. For more information, see [Connecting to a database](connect-database-console.md).
Then choose a datashare either from the **Datashares from other clusters** or **Datashares created in my cluster** section to view its details.
## Removing datashare objects from datashares
You can remove one or more objects from a datashare by using the following procedure.
**To remove one or more objects from a datashare**
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. Choose **Datashares**.
1. In the **Datashares created in my account** section, choose **Connect to database**. For more information, see [Connecting to a database](connect-database-console.md).
1. Choose the datashare you want to edit, then choose **Edit**. The datashare details page appears.
1. To remove one or more datashare objects to the datashare, do one of the following:
+ To remove schemas from the datashare, choose one or more schemas. Then choose **Remove**. Amazon Redshift removes the specified schemas and all the objects of the specified schemas from the datashare.
+ To remove tables and views from the datashare, choose one or more tables and views. Then choose **Remove**. Alternatively, choose **Remove by schema** to remove all tables and views in the specified schemas.
+ To remove user-defined functions from the datashare, choose one or more user-defined functions. Then choose **Remove**. Alternatively, choose **Remove by schema** to remove all user-defined functions in the specified schemas.
## Removing data consumers from datashares
You can remove one or more data consumers from a datashare. Data consumers can be namespaces that uniquely identified Amazon Redshift clusters or AWS accounts.
Choose one or more data consumers either from the namespace IDs or AWS account, then choose **Remove**.
Amazon Redshift removes the specified data consumers from the datashare. They lose access to the datashare immediately.
## Editing datashares created in your account
Edit datashares created in your account using the console. Connect to a database first to see the list of datashares created in your account.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. Choose **Datashares**.
1. In the **Datashares created in my account** section, choose **Connect to database**. For more information, see [Connecting to a database](connect-database-console.md).
1. Choose the datashare you want to edit, then choose **Edit**. The datashare details page appears.
1. Make any changes in the **Datashare objects** or **Data consumers** section.
**Note**
If you chose to publish your datashare to the AWS Glue Data Catalog, you can't edit the configuration to publish the datashare to other Amazon Redshift accounts.
1. Choose **Save changes**.
Amazon Redshift updates your datashare with the changes.
## Deleting a datashare created in your account
Delete datashares created in your account using the console. Connect to a database first to see the list of datashares created in your account.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. Choose **Datashares**. The datashare list appears.
1. In the **Datashares created in my account** section, choose **Connect to database**. For more information, see [Connecting to a database](connect-database-console.md).
1. Choose one or more datashares you want to delete, then choose **Delete**. The Delete datashares page appears.
Deleting a datashare shared with Lake Formation doesn't automatically remove the associated permissions in Lake Formation. To remove them, go to the Lake Formation console.
1. Type **Delete** to confirm deleting the specified datashares.
1. Choose **Delete**.
After datashares are deleted, datashare consumers lose access to the datashares.
# Querying datashares
With Amazon Redshift, you can query data across datashares from producer clusters to securely access live data without copying or transferring it. The following sections cover the details of setting up and querying datashares in your Amazon Redshift environment.
## Creating databases from datashares
To start querying data in the datashare, create a database from a datashare. You can create only one database from a specified datashare.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. Choose **Datashares**. The datashare list appears.
1. In the **Datashares from other clusters** section, choose **Connect to database**. For more information, see [Connecting to a database](connect-database-console.md).
1. Choose a datashare that you want to create databases from, then choose **Create database from datashare**. The Create database from datashare page appears.
1. In the **Database name**, specify a database name. The database name must be 1–64 alphanumeric characters (lowercase only) and it can't be a reserved word.
1. Choose **Create**.
After the database is created, you can query data in the database.
# Managing AWS Data Exchange datashares
With Amazon Redshift, you can securely share and receive live data from AWS Data Exchange without having to create and manage data extracts or pipelines. Managing AWS Data Exchange datashares allows you to subscribe to third-party data products and integrate live data streams directly into your Amazon Redshift data warehouse. The following sections demonstrate managing AWS Data Exchange datashares within your Amazon Redshift clusters.
## Creating data sets on AWS Data Exchange
Create data sets on AWS Data Exchange.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. Choose **Datashares**.
1. In the **Datashares created in my account** section, choose an AWS Data Exchange datashare.
1. Choose **Create data set on AWS Data Exchange**. For more information, see [Publishing a new product](https://docs.aws.amazon.com/data-exchange/latest/userguide/publishing-products.html).
## Editing AWS Data Exchange datashares
Edit AWS Data Exchange datashares using the console. Connect to a database first to see the list of datashares created in your account.
For AWS Data Exchange datashares, you can't make changes to data consumers.
To edit the publicly accessible setting for AWS Data Exchange datashares, use the Query editor v2. Amazon Redshift generates a random one-time value to set the session variable to allow turning this setting off. For more information, see [ALTER DATASHARE usage notes](r_ALTER_DATASHARE.md#r_ALTER_DATASHARE_usage).
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. From the navigator menu, choose **Editor**, then **Query editor v2**.
1. If this is the first time you use the Query editor v2, configure your AWS account. By default, an AWS owned key is used to encrypt resources. For more information about configuring your AWS account, see [Configuring your AWS account](https://docs.aws.amazon.com/redshift/latest/mgmt/query-editor-v2-getting-started.html) in the *Amazon Redshift Management Guide*.
1. To connect to the cluster that your AWS Data Exchange datashare is in, choose **Database** and the cluster name in the tree-view panel. If prompted, enter the connection parameters.
1. Copy the following SQL statement. The following example changes the publicly accessible setting of the salesshare datashare.
```
ALTER DATASHARE salesshare SET PUBLICACCESSIBLE FALSE;
```
1. To run the copied SQL statement, choose **Queries** and paste the copied SQL statement in the query area. Then choose **Run**.
An error appears following:
```
ALTER DATASHARE salesshare SET PUBLICACCESSIBLE FALSE;
ERROR: Alter of ADX-managed datashare salesshare requires session variable datashare_break_glass_session_var to be set to value 'c670ba4db22f4b'
```
The value 'c670ba4db22f4b' is a random one-time value that Amazon Redshift generates when an unrecommended operation occurs.
1. Copy and paste the following sample statement into the query area. Then run the command. The `SET datashare_break_glass_session_var` command applies a permission to allow an unrecommended operation for an AWS Data Exchange datashare.
```
SET datashare_break_glass_session_var to 'c670ba4db22f4b';
```
1. Run the ALTER DATASHARE statement again.
```
ALTER DATASHARE salesshare;
```
Amazon Redshift updates your datashare with the changes.
## Deleting AWS Data Exchange datashares created in your account
Delete AWS Data Exchange datashares created in your account using the console. Connect to a database first to see the list of datashares created in your account.
1. Sign in to the AWS Management Console and open the Amazon Redshift console at [https://console.aws.amazon.com/redshiftv2/](https://console.aws.amazon.com/redshiftv2/).
1. On the navigation menu, choose **Clusters**, then choose your cluster. The cluster details page appears.
1. From the navigator menu, choose **Editor**, then **Query editor v2**.
1. If this is the first time you use the Query editor v2, configure your AWS account. By default, an AWS owned key is used to encrypt resources. For more information about configuring your AWS account, see [Configuring your AWS account](https://docs.aws.amazon.com/redshift/latest/mgmt/query-editor-v2-getting-started.html) in the *Amazon Redshift Management Guide*.
1. To connect to the cluster that your AWS Data Exchange datashare is in, choose **Database** and the cluster name in the tree-view panel. If prompted, enter the connection parameters.
1. Copy the following SQL statement. The following example drops the salesshare datashare.
```
DROP DATASHARE salesshare
```
1. To run the copied SQL statement, choose **Queries** and paste the copied SQL statement in the query area. Then choose **Run**.
An error appears following:
```
ERROR: Drop of ADX-managed datashare salesshare requires session variable datashare_break_glass_session_var to be set to value '620c871f890c49'
```
The value '620c871f890c49' is a random one-time value that Amazon Redshift generates when an unrecommended operation occurs.
1. Copy and paste the following sample statement into the query area. Then run the command. The `SET datashare_break_glass_session_var` command applies a permission to allow an unrecommended operation for an AWS Data Exchange datashare.
```
SET datashare_break_glass_session_var to '620c871f890c49';
```
1. Run the DROP DATASHARE statement again.
```
DROP DATASHARE salesshare;
```
After the datashare is deleted, datashare consumers lose access to the datashare.
Deleting a shared AWS Data Exchange datashare can breach data product terms in AWS Data Exchange.