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://amazonaws-china.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/). # What is Amazon Redshift Serverless? Amazon Redshift Serverless automatically provisions data warehouse capacity and intelligently scales the underlying resources. Amazon Redshift Serverless adjusts capacity in seconds to deliver consistently high performance and simplified operations for even the most demanding and volatile workloads. With Amazon Redshift Serverless, you can benefit from the following features: + Access and analyze data without the need to set up, tune, and manage Amazon Redshift provisioned clusters. + Use the superior Amazon Redshift SQL capabilities, industry-leading performance, and data-lake integration to seamlessly query across a data warehouse, a data lake, and operational data sources. + Deliver consistently high performance and simplified operations for the most demanding and volatile workloads with intelligent and automatic scaling. + Use workgroups and namespaces to organize compute resources and data with granular cost controls. + Pay only when the data warehouse is in use. With Amazon Redshift Serverless, you use a console interface to reach a serverless data warehouse or APIs to build applications. Through the data warehouse, you can access your Amazon Redshift managed storage and your Amazon S3 data lake. This video shows you how Amazon Redshift Serverless makes it easy to run and scale analytics without having to manage data warehouse infrastructure: [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/XcRJjXudIf8/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/XcRJjXudIf8) # Amazon Redshift Serverless console To learn how to get started with the Amazon Redshift Serverless console, watch the following video. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/eq4o26Hpuac/0.jpg)](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 Amazon 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 Amazon Web Services 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, Amazon KMS encryption values, and audit logging values. You can update only audit logging. + **Amazon KMS key** – The Amazon 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.amazonaws.cn/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 Amazon Web Services accounts. + **Datashares from other namespaces and Amazon Web Services accounts** – You can create a database from a datashare from other namespace and Amazon Web Services 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.amazonaws.cn/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). ## Amazon Glue Data Catalog In the **Amazon Glue Data Catalog** tab, you can view the registration status of your namespace to the Amazon Glue Data Catalog. This tab only appears after you’ve started the registering process. For more information about registering namespaces to the Amazon Glue Data Catalog, see [ Apache Iceberg compatibility for Amazon Redshift](https://docs.amazonaws.cn/redshift/latest/dg/iceberg-integration_overview.html) in the Amazon Redshift Database Developer Guide. # Considerations when using Amazon Redshift Serverless For a list of Amazon Web Services Regions where the Amazon Redshift Serverless is available, see the endpoints listed for [Redshift Serverless API](https://docs.amazonaws.cn/general/latest/gr/redshift-service.html) in the *Amazon Web Services General Reference*. Some resources used by Amazon Redshift Serverless are subject to quotas. For more information, see [Quotas for Amazon Redshift Serverless objects](amazon-redshift-limits.md#serverless-limits-account). When you DECLARE a cursor, the result-set size specifications for Amazon Redshift Serverless is specified in [DECLARE](https://docs.amazonaws.cn/redshift/latest/dg/declare.html). Amazon Redshift Serverless has a cursor maximum total result set size of 150,000 MB. *Online Patching* – Amazon Redshift Serverless offers automatic software updates without requiring traditional maintenance windows. When a new update is available, the system applies it within 14 days of release during idle periods. The update process typically takes up to 15 minutes. If no 15-minute idle period occurs within 14 days, your Serverless endpoint may experience brief unavailability. During this time, application connections to endpoints may fail. You can monitor Redshift patch releases in the "Cluster versions for Amazon Redshift" documentation. For information about Amazon Redshift Serverless SLAs, see [Amazon Redshift Service Level Agreement](https://aws.amazon.com/redshift/sla/). *Track* – When Amazon Redshift releases a new workgroup version, your workgroup is updated automatically. You can control whether your workgroup is updated to the most recent release or to the previous release. For information about tracks, see [Tracks for Amazon Redshift provisioned clusters and serverless workgroups](tracks.md). *Availability Zone IDs* – When you configure your Amazon Redshift Serverless instance, open **Additional considerations**, and make sure that the subnet IDs provided in **Subnet** contain at least two of the supported Availability Zone IDs. + For workgroups without Enhanced VPC Routing (EVR), you need two Availability Zones (AZs). + For workgroups with EVR, you need three AZs. To see the subnet to Availability Zone ID mapping, go to the VPC console and choose **Subnets** to see the list of subnet IDs with their Availability Zone IDs. Verify that your subnet is mapped to a supported Availability Zone ID. To create a subnet, see [Create a subnet in your VPC](https://docs.amazonaws.cn//vpc/latest/userguide/working-with-vpcs.html#AddaSubnet) in the *Amazon VPC User Guide*. *Two subnets (without EVR)* – You must have at least two subnets, and they must span across two Availability Zones. *Three subnets (with EVR ONLY)* – You must have at least three subnets when you use EVR, and they must span across three or more Availability Zones. *Free IP address requirements* – When using Redshift Serverless without enhanced VPC routing (EVR) enabled, you must have at least three free IP addresses available in each subnet. This is a requirement of the proper functioning of the service. When updating the RPUs for Redshift Serverless deployment, at least three free IP addresses must be available in each subnet to accommodate the service's operational requirements. For more information about allocating IP addresses and understanding IP addressing in Amazon VPC, see [ IP addressing for your VPCs and subnets](https://docs.amazonaws.cn/vpc/latest/userguide/vpc-ip-addressing.html) in the *Amazon VPC User Guide*. ------ #### [ Without EVR ] If you don't use enhanced VPC routing, you must have at least three free IP addresses for each subnet, regardless of the size of the base RPU (4 to 1024 RPUs), or the RPU usage of your workgroup or workgroups. The need for 3 IP address is also applicable to workgroups that have AI-driven scaling and optimization capabilities enabled. ------ #### [ With Enhanced VPC Routing (EVR) ] If you use enhanced VPC routing with Redshift Serverless, the minimum number of IP addresses required when creating a workgroup are as follows: | Redshift Processing Units (RPUs) | Free IP addresses required | Minimum CIDR size | | --- | --- | --- | | 4 | 9 | /27 | | 8 | 9 | /27 | | 16 | 13 | /27 | | 32 | 13 | /27 | | 64 | 21 | /27 | | 128 | 37 | /26 | | 256 | 69 | /25 | | 512 | 133 | /24 | | 1024 | 261 | /23 | With EVR, you also need free IP addresses when updating your workgroup to use more RPUs. The number of free IP addresses required when updating the subnets for a workgroup are as follows: | Redshift Processing Units (RPUs) | Updated Redshift Processing Units (RPUs) | Free IP addresses required | | --- | --- | --- | | 4 | 8 | 10 | | 8 | 16 | 10 | | 16 | 32 | 13 | | 32 | 64 | 16 | | 64 | 128 | 28 | | 128 | 256 | 52 | | 256 | 512 | 100 | | 512 | 1024 | 197 | **Note** The maximum base RPU capacity of 1024 is only available in the following Amazon Web Services Regions: US East (N. Virginia) US East (Ohio) US West (Oregon) Europe (Ireland) Europe (London) ------ For more information on allocating IP addresses, see [IP addressing](https://docs.amazonaws.cn//vpc/latest/userguide/how-it-works.html#vpc-ip-addressing) in the *Amazon VPC User Guide*. *Storage space after migration* – When migrating small Amazon Redshift provisioned clusters to Amazon Redshift Serverless, you might see an increase in storage-space allocation after migration. This is a result of optimized storage-space allocation, resulting in preallocated storage space. This space is used over a period of time as data grows in Amazon Redshift Serverless. *Datasharing between Amazon Redshift Serverless and Amazon Redshift provisioned clusters * – When datasharing where Amazon Redshift Serverless is the producer and a provisioned cluster is the consumer, the provisioned cluster must have a cluster version later than 1.0.38214. If you use a cluster version earlier than this, an error occurs when you run a query. You can view the cluster version on the Amazon Redshift console on the **Maintenance ** tab. You can also run `SELECT version();`. *Max query execution time * – Elapsed execution time for a query, in seconds. Execution time doesn't include time spent waiting in a queue. If a query exceeds the set execution time, Amazon Redshift Serverless stops the query. Valid values are 0–86,399. *Migrating for tables with interleaved sort keys * – When migrating Amazon Redshift provisioned clusters to Amazon Redshift Serverless, Redshift converts tables with interleaved sort keys and DISTSTYLE KEY to compound sort keys. The DISTSTYLE doesn't change. For more information on distribution styles, see [Working with data distribution styles](https://docs.amazonaws.cn//redshift/latest/dg/t_Distributing_data.html) in the Amazon Redshift Developer Guide. For more information on sort keys, see [Working with sort keys](https://docs.amazonaws.cn//redshift/latest/dg/t_Sorting_data.html). *VPC sharing* – You can create Amazon Redshift Serverless workgroups in a shared VPC. If you do so, we recommend that you don't delete the resource share as it can result in the workgroup becoming unavailable. **IPv6 Support:** Amazon Redshift Serverless supports configuring your Amazon Redshift workgroups with both IPv4 and IPv6 addresses (dual-stack) or IPv4-only configurations within your Amazon Virtual Private Clouds (VPCs). You can enable IPv6 support when creating new Amazon Redshift Serverless workgroups or modify existing workgroups to support IPv6 addressing. With this capability, you can deploy Amazon Redshift Serverless warehouses in IPv6-enabled VPC subnets and configure network settings to support the expanding address space requirements of your applications. Your applications can now communicate with Amazon Redshift Serverless warehouses using either IPv4 or IPv6 protocols, ensuring compatibility with both existing and future network architectures.