CmdID / aws / aws redshift

aws redshift accept-reserved-node-exchange

Exchanges a DC1 Reserved Node for a DC2 Reserved Node with no changes to the configuration (term, payment type, or number of nodes) and no additional costs. AWS CLI reference

1 example 2 options Its page in the AWS CLI reference

Examples

from aws-cli, each command read by CmdID

To accept reserved node exchange

The following accept-reserved-node-exchange example accepts exchange of a DC1 reserved node for a DC2 reserved node.

aws redshift accept-reserved-node-exchange --reserved-node-id 12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE --target-reserved-node-offering-id 12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE

Identify

--reserved-node-idA string representing the node identifier of the DC1 Reserved Node to be exchanged.

--target-reserved-node-offering-idThe unique identifier of the DC2 Reserved Node offering to be used for the exchange.

Its output

{
    "ExchangedReservedNode": {
        "ReservedNodeId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
        "ReservedNodeOfferingId": "12345678-12ab-12a1-1a2a-12ab-12a12EXAMPLE",
        "NodeType": "dc2.large",
        "StartTime": "2019-12-06T21:17:26Z",
        "Duration": 31536000,
        "FixedPrice": 0.0,
        "UsagePrice": 0.0,
        "CurrencyCode": "USD",
        "NodeCount": 1,
        "State": "exchanging",
        "OfferingType": "All Upfront",
        "RecurringCharges": [
            {
                "RecurringChargeAmount": 0.0,
                "RecurringChargeFrequency": "Hourly"
            }
        ],
        "ReservedNodeOfferingType": "Regular"
    }
}

For more information, see Upgrading Reserved Nodes With the AWS CLI in the Amazon Redshift Cluster Management Guide.

Options

2 in the AWS CLI reference

--reserved-node-idA string representing the node identifier of the DC1 Reserved Node to be exchanged.

--target-reserved-node-offering-idThe unique identifier of the DC2 Reserved Node offering to be used for the exchange.