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
.
Purchasing a reserved
node
You can use the Amazon Web Services Management Console or the Amazon CLI to purchase reserved node offerings, and to
view current and past reservations.
- Amazon Web Services Management Console
-
To purchase a reserved node
-
Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at
https://console.amazonaws.cn/redshiftv2/.
-
On the navigation menu, choose Clusters, then
choose Reserved nodes to display the list of
reserved nodes.
-
Choose Purchase reserved nodes to display the
page to choose the properties of the node that you want to
purchase.
-
Enter the properties of the node, then choose Purchase
reserved nodes.
After you purchase an offering, the Reserved Node
list displays your reservations and the details of each one, such as the
node type, number of nodes, and status of the reservation. For more
information about the reservation details, see How reserved nodes work.
To upgrade a reserved node, use the Amazon CLI.
You can't convert all node types to reserved nodes, and it's also possible
that an existing reserved node isn't available for renewal. This might be
because the node type is discontinued. Contact customer support to renew a
discontinued node type.
- Amazon CLI
-
To upgrade a reserved node
reservation with the Amazon CLI
-
Obtain a list of ReservedNodeOfferingID's for offerings that meet
your requirements for payment type, term, and charges. The following
example illustrates this step.
aws redshift get-reserved-node-exchange-offerings --reserved-node-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
{
"ReservedNodeOfferings": [
{
"Duration": 31536000,
"ReservedNodeOfferingId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy",
"UsagePrice": 0.0,
"NodeType": "dc2.large",
"RecurringCharges": [
{
"RecurringChargeFrequency": "Hourly",
"RecurringChargeAmount": 0.2
}
],
"CurrencyCode": "USD",
"OfferingType": "No Upfront",
"ReservedNodeOfferingType": "Regular",
"FixedPrice": 0.0
}
]
}
-
Call accept-reserved-node-exchange
and provide the ID
for the DC1 reserved node that you want to exchange along with the
ReservedNodeOfferingID you obtained in the previous step.
The following example illustrates this step.
aws redshift accept-reserved-node-exchange --reserved-node-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx --target-reserved-node-offering-id yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyyy
{
"ExchangedReservedNode": {
"UsagePrice": 0.0,
"OfferingType": "No Upfront",
"State": "exchanging",
"FixedPrice": 0.0,
"CurrencyCode": "USD",
"ReservedNodeId": "zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz",
"NodeType": "dc2.large",
"NodeCount": 1,
"RecurringCharges": [
{
"RecurringChargeFrequency": "Hourly",
"RecurringChargeAmount": 0.2
}
],
"ReservedNodeOfferingType": "Regular",
"StartTime": "2018-06-27T18:02:58Z",
"ReservedNodeOfferingId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyyy",
"Duration": 31536000
}
}
You can confirm that the exchange is complete by calling describe-reserved-nodes and checking the value for Node
type
.