Logo of Trend Micro
Use the Conformity Knowledge Base AI to help improve your Cloud Posture

Redshift Reserved Node Payment Pending

Trend Cloud One™ – Conformity is a continuous assurance tool that provides peace of mind for your cloud infrastructure, delivering over 1000 automated best practice checks.

Risk Level: High (not acceptable risk)
Rule ID: RS-013

Identify any pending Amazon Redshift Reserved Nodes (RNs) available within your account and follow Cloud Conformity guidelines for remediation/resolution in order to receive a significant discount (up to 75% depending on the commitment term) on the hourly charges. A payment-pending Redshift RN purchase is a reservation purchase that can`t be fully processed due to issues with the AWS account payment method, that maintains the "payment-pending" status long after the initial purchase attempt - not to be confused with the pending state temporarily installed during a successfully processed Redshift RN purchase (i.e. where the reservation status changes from "payment-pending" to "active" in a timely fashion).

This rule can help you work with the AWS Well-Architected Framework.

This rule resolution is part of the Conformity Security & Compliance tool for AWS.

Cost
optimisation

Using Reserved Nodes to cut down on computing costs is one of the most recommended cost optimization strategies when working with AWS Redshift. To fully receive the discount benefit you need to make sure that all your Redshift reservation purchases have been fully processed (i.e. the purchase has been approved and the payment has been confirmed).

Audit

To identify any pending Redshift RN purchases available within your AWS account, perform the following:

Using AWS Console

01 Sign in to the AWS Management Console.

02 Navigate to Redshift dashboard at https://console.aws.amazon.com/redshift/.

03 In the navigation panel, choose Reserved Nodes.

04 Open the dashboard Show/Hide Columns dialog box by clicking the configuration icon from the right menu:

Show/Hide Columns

05 Inside the Show/Hide Columns dialog box, select Status checkbox:

Show/Hide Columns Status

then click Save to apply the changes.

06 On the Redshift Reserved Nodes page, verify the status value listed for each RN within the Status column to determine the node reservation status. If one or more AWS Redshift RNs have the status set to payment-pending, the purchase payment processing for the listed Reserved Node(s) was not fully processed, therefore you need to retry your reservation(s) pending payment by contacting AWS Support Center.

07 Change the AWS region from the navigation bar and repeat the entire audit process for other regions.

Using AWS CLI

01 Run describe-reserved-nodes command (OSX/Linux/UNIX) using custom query filters to list the IDs of all existing Redshift RN purchases, available in the selected AWS region: 

aws redshift describe-reserved-nodes
    --region us-east-1
    --output table
    --query 'ReservedNodes[*].ReservedNodeId'

02 The command output should return a table with the requested Reserved Node(s) ID(s): 

----------------------------------------
|           ReservedNodeIds            |
+--------------------------------------+
| ca703e93-112a-b71d-ac5b-e1e2e30bd254 |
| e8698e2e-ac01-5d65-935d-a6a3e931e75f |
+--------------------------------------+

03 Run again describe-reserved-nodes command (OSX/Linux/UNIX) using the ID of your AWS Redshift RN returned at the previous step as identifier and custom query filters to describe the purchase status for the selected Reserved Node: 

aws redshift describe-reserved-nodes
    --region us-east-1
    --reserved-node-id ca703e93-112a-b71d-ac5b-e1e2e30bd254
    --query 'ReservedNodes[*].State'

04 The command output should return the requested RN purchase payment status: 

[
    "payment-pending"
]

If the status value returned by the command output is "payment-pending", the selected Redshift Reserved Node purchase payment was not fully processed, therefore you must retry your RN(s) pending payment by contacting AWS Support Center using the console available at https://console.aws.amazon.com/support/.

05 Change the AWS region by updating the --region command parameter value and repeat steps no. 1 – 4 to perform the audit process for other regions.

Remediation / Resolution

Because Partial Upfront and All Upfront Reserved Node types require an upfront payment, if the issuing bank of your payment method does not approve the AWS charges for some reason, your reservation purchases are not fully processed (and confirmed), hence Amazon set their status to "payment-pending". To resolve any incomplete AWS Redshift reservations, you need to retry these Reserved Node(s) payments by contacting Amazon Web Services. To create the required support case through the AWS Support Center, perform the following:

Note: Requesting Amazon to retry your pending Redshift Reserved Node(s) payments using AWS Billing and Cost Management console or AWS API via Command Line Interface (CLI) is not currently supported.

Using AWS Console

01 Sign in to the AWS Management Console.

02 Navigate to AWS Support Center page at https://console.aws.amazon.com/support/.

03 On Support Center page, click Create case to open the necessary support case.

04 On the Create Case page, perform the following:

  1. Under Regarding, select Account and Billing Support option.
  2. Choose Billing from the Service dropdown list to send your request to AWS Billing and Cost Management service.
  3. Select Reserved Instances from the Category dropdown list.
  4. Inside the Subject box, enter a subject for your request such as "Retry Redshift Reserved Node pending payment".
  5. Within Description textbox, enter a small description for your request so that AWS support can evaluate faster your request.
  6. Under Contact method, select a preferred contact method that AWS support team can use to respond to your request. If your need is urgent, choose Phone to request a direct phone call.
  7. Click Submit to send the payment retry request for your Redshift Reserved Node(s) to Amazon Web Services support team.

References

Publication date Mar 7, 2017

Related Redshift rules