Skip to main content

More Info:

Ensure that none of your AWS Redshift Reserved Node purchases have been failed.

Risk Level

Low

Address

Cost Optimisation

Compliance Standards

  • APRA CPS 234 (Australia)
  • BSI C5 (Germany)
  • Brazil LGPD
  • CCPA / CPRA (California)
  • CIS Critical Security Controls v8
  • CMMC 2.0
  • CSA Cloud Controls Matrix v4
  • Cloudanix Best Practice
  • DPDPA
  • Digital Operational Resilience Act (EU)
  • ISO/IEC 27017
  • KSA PDPL
  • MAS Technology Risk Management (Singapore)
  • NIS2 Directive
  • NIST SP 800-171
  • NYDFS 23 NYCRR 500
  • SWIFT Customer Security Controls Framework
  • Sarbanes-Oxley IT General Controls
  • UK NCSC Cyber Assessment Framework

Triage and Remediation

Remediation

Using Console

To remediate the issue of Redshift Reserved Nodes having a status of “Payment Failed” in AWS, you can follow these steps using the AWS Management Console:
  1. Navigate to the AWS Redshift Console:
    • Go to the AWS Management Console (https://aws.amazon.com/console/).
    • In the “Find Services” search bar, type “Redshift” and select “Amazon Redshift” from the options.
  2. Access the Reserved Nodes Dashboard:
    • In the Amazon Redshift console, navigate to the “Clusters” section from the left-hand menu.
    • Click on the “Reserved Nodes” tab to view the list of reserved nodes.
  3. Identify Reserved Nodes with Payment Failed Status:
    • Look for the reserved nodes that have a status of “Payment Failed” in the list of reserved nodes.
  4. Modify the Reserved Node:
    • Select the reserved node with the “Payment Failed” status by clicking on it.
    • Click on the “Modify” button to edit the reservation.
  5. Update Payment Information:
    • In the modification form, update the payment information associated with the reserved node.
    • Ensure that the payment method linked to the reserved node is valid and has sufficient funds to cover the reservation.
  6. Save Changes:
    • After updating the payment information, click on the “Save” or “Apply Changes” button to confirm the modifications.
  7. Verify Status:
    • Once the changes are saved, verify that the status of the reserved node has been updated to a valid state (e.g., “Active”).
  8. Monitor and Confirm:
    • Monitor the status of the reserved node over the next few minutes to ensure that the changes are successfully applied.
    • Confirm that the reserved node no longer shows a status of “Payment Failed.”
By following these steps, you should be able to remediate the issue of Redshift Reserved Nodes having a status of “Payment Failed” in AWS Redshift using the AWS Management Console.

To remediate the issue of Redshift Reserved Nodes having a status of “Payment Failed” in AWS, you can follow these steps using the AWS CLI:
  1. Identify the Reserved Node with Payment Failed status: Use the following AWS CLI command to list all the Redshift Reserved Nodes and their statuses:
    Look for the Reserved Node(s) with the “Payment Failed” status.
  2. Modify the Reserved Node: Use the following AWS CLI command to modify the Reserved Node with the Payment Failed status:
    Replace <ReservedNodeId> with the ID of the Reserved Node with Payment Failed status and <NewReservedNodeOfferingId> with the ID of a new Reserved Node offering that you want to apply.
  3. Confirm the modification: Use the following AWS CLI command to confirm the modification and apply the changes:
    Replace <NewReservedNodeOfferingId> with the ID of the new Reserved Node offering that you specified in step 2.
  4. Verify the status: Use the following AWS CLI command to verify that the Reserved Node status has been updated:
    Check if the Reserved Node status is now updated and no longer shows “Payment Failed”.
By following these steps using the AWS CLI, you should be able to remediate the issue of Redshift Reserved Nodes having a status of “Payment Failed” in AWS.
To remediate the misconfiguration of Redshift Reserved Nodes having a status of “Payment Failed” in AWS, you can use the AWS SDK for Python (Boto3) to automate the remediation process. Here are the step-by-step instructions to remediate this issue:
  1. Install Boto3: If you haven’t already installed Boto3, you can do so using pip:
  2. Configure AWS Credentials: Make sure you have your AWS credentials configured either through environment variables, shared credentials file, or AWS config file.
  3. Write Python Script: Create a Python script with the following code to identify and update the status of Redshift Reserved Nodes with “Payment Failed” status:
  4. Run the Script: Execute the Python script to identify Redshift Reserved Nodes with “Payment Failed” status and update their status to “ALL_UPFRONT” payment option.
By following these steps, you can automatically remediate the misconfiguration of Redshift Reserved Nodes with a status of “Payment Failed” in AWS Redshift using Python and Boto3.
Terraform cannot remediate this finding.Redshift reserved node purchases (and their payment status) are not managed resources in the hashicorp/aws provider—there is no aws_redshift_reserved_node (or similar) resource or argument to change status from payment-failed to active.To fix this, you must resolve the payment issue in AWS directly: in the AWS Console go to Redshift → Reserved nodes, identify nodes with payment-failed status, and follow AWS billing/payment instructions (or re-purchase the reservation once billing is corrected). After that, Terraform can continue to manage cluster resources, but not the reservation payment state.

Additional Reading: