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/).
# Amazon Redshift Serverless console
To learn how to get started with the Amazon Redshift Serverless console, watch the following video.
[](http://www.youtube.com/watch?v=https://www.youtube.com/embed/eq4o26Hpuac)
## Serverless dashboard
On the **Serverless dashboard** page, you can view a summary of your resources and graphs of your usage.
+ **Namespace overview** – This section shows the amount of snapshots and datashares within your namespace.
+ **Workgroups** – This section shows all of the workgroups within Amazon Redshift Serverless.
+ **Queries metrics** – This section shows query activity for the last one hour.
+ **RPU capacity used** – This section shows capacity used for the last one hour.
+ **Free trial** – This section shows the free trial credits remaining in your AWS account. This covers all usage of Amazon Redshift Serverless resources and operations, including snapshots, storage, workgroup, and so on, under the same account.
+ **Alarms** – This section shows the alarms you configured in Amazon Redshift Serverless.
## Data backup
On the **Data backup** tab you can work with the following:
+ **Snapshots** – You can create, delete, and manage snapshots of your Amazon Redshift Serverless data. The default retention period is `indefinitely`, but you can configure the retention period to be any value between 1 and 3653 days. You can authorize AWS accounts to restore namespaces from a snapshot.
+ **Recovery points** – Displays the recovery points that are automatically created so you can recover from an accidental write or delete within the last 24 hours. To recover data, you can restore a recovery point to any available namespace. You can create a snapshot from a recovery point if you want to keep a point of recovery for a longer time period. The default retention period is `indefinitely`, but you can configure the retention period to be any value between 1 and 3653 days.
## Data access
On the **Data access** tab you can work with the following:
+ **Network and security** settings – You can view VPC-related values, AWS KMS encryption values, and audit logging values. You can update only audit logging.
+ **AWS KMS key** – The AWS KMS key used to encrypt resources in Amazon Redshift Serverless.
+ **Permissions** – You can manage the IAM roles that Amazon Redshift Serverless can assume to use resources on your behalf. For more information, see [Identity and access management in Amazon Redshift Serverless](serverless-iam.md).
+ **Redshift-managed VPC endpoints** – You can access your Amazon Redshift Serverless instance from another VPC or subnet. For more information, see [Connecting to Amazon Redshift Serverless from other VPC endpoints](serverless-connecting.md#serverless-vpc-connect).
## Limits
On the **Limits** tab, you can work with the following:
+ **Base capacity in Redshift processing units (RPUs)** settings – You can set the base capacity used to process your workload. To improve query performance, increase your RPU value.
+ **Usage limits** – The maximum compute resources that your Amazon Redshift Serverless instance can use in a time period before an action is initiated. You limit the amount of resource Amazon Redshift Serverless uses to run your workload. Usage is measured in Redshift Processing Unit (RPU) hours. An RPU hour is the number of RPUs used in an hour. You determine an action to occur when you reach a limit that you set, as follows:
+ Send an alert.
+ Log an entry to a system table.
+ Turn off user queries.
You can set up to four limits.
+ **Query limits** – You can add a limit to monitor performance and limits. For more information about query monitoring limits, see [WLM query monitoring rules](https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html).
For more information, see [Compute capacity for Amazon Redshift Serverless](serverless-capacity.md).
## Datashares
On the **Datashares** tab you can work with the following:
+ **Datashares created in my namespace** settings – You can create a datashare and share it with other namespaces and AWS accounts.
+ **Datashares from other namespaces and AWS accounts** – You can create a database from a datashare from other namespace and AWS accounts.
For more information about data sharing, see [Data sharing in Amazon Redshift Serverless](serverless-datasharing.md).
## Query and database monitoring
On the **Query and database monitoring** page, you can view graphs of your **Query history** and **Database performance**.
On the **Query history** tab, you see the following graphs (you can choose between **Query list** and **Resource metrics**):
+ **Query runtime** – This graph shows which queries are running in the same timeframe. Choose a bar in the graph to view more query execution details.
+ **Queries and loads** – This section lists queries and loads by **Query ID**.
+ **RPU capacity used** – This graph shows overall capacity in Redshift Processing Units (RPUs).
+ **Database connections** – This graph shows the number of active database connections.
## Database performance
On the **Database performance** tab, you see the following graphs:
+ **Queries completed per second** – This graph shows the average number of queries completed per second.
+ **Queries duration** – This graph shows the average amount of time to complete a query.
+ **Database connections** – This graph shows the number of active database connections.
+ **Running queries** – This graph shows the total number of running queries at a given time.
+ **Queued queries** – This graph shows the total number of queries queued at a given time.
+ **Query run time breakdown** – This graph shows the total time queries spent running by query type.
## Resource monitoring
On the **Resource monitoring** page, you can view graphs of your consumed resources. You can filter the data based on several facets.
+ **Metric filter** – You can use metric filters to select filters for a specific workgroup, as well as choose the time range and time interval.
+ **RPU capacity used** – This graph shows the overall capacity in Redshift processing units (RPUs).
+ **Compute usage** – This graph shows the usage of RPU hours by period for the selected time range. For time ranges of less than 6 hours, RPU hours are shown in exact time. For time ranges of 6 hours or more, RPU hours are shown as averages.
+ **Extra compute for automatic optimizations charged seconds** – This graph shows the number of RPU-seconds charged for automatic database optimizations for the selected time range. You're charged for automatic optimizations when you Amazon Redshift uses extra compute resources to run them. For more information, see [ Allocating extra compute resources for automatic database optimization ](https://docs.aws.amazon.com/redshift/latest/dg/t_extra-compute-autonomics.html).
## Datashares
On the **Datashares** page, you can manage datashares **In my account** and **From other accounts**. For more information about data sharing, see [Data sharing in Amazon Redshift Serverless](serverless-datasharing.md).
## AWS Glue Data Catalog
In the **AWS Glue Data Catalog** tab, you can view the registration status of your namespace to the AWS Glue Data Catalog. This tab only appears after you’ve started the registering process. For more information about registering namespaces to the AWS Glue Data Catalog, see [ Apache Iceberg compatibility for Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/dg/iceberg-integration_overview.html) in the Amazon Redshift Database Developer Guide.