Redshift Reserved Node Lease Expiration In The Next 30 Days
More Info:
Amazon Redshift Reserved Nodes (RN) should be renewed before expiration.Risk Level
LowAddress
Cost OptimisationCompliance Standards
CBPTriage and Remediation
Remediation
Using Console
Using Console
To remediate the issue of Redshift Reserved Node Lease Expiration in the next 30 days in AWS Redshift, you can follow these steps using the AWS Management Console:
- Login to AWS Console: Go to the AWS Management Console (https://aws.amazon.com/console/) and login with your credentials.
- Navigate to Amazon Redshift Service: Click on the “Services” dropdown menu at the top left corner of the console, then select “Redshift” under the Analytics section.
- Check Reserved Nodes: In the Redshift dashboard, navigate to the “Clusters” section on the left side menu. Click on the Redshift cluster for which you want to check the Reserved Node Lease Expiration.
- View Reserved Nodes: In the cluster details page, scroll down to the “Properties” section and click on the “Reserved Nodes” tab. Here you will see a list of all the Reserved Nodes associated with this cluster.
- Check Lease Expiration Date: Check the “Expiration” column in the Reserved Nodes tab to identify any Reserved Nodes with an expiration date within the next 30 days.
-
Renew Reserved Nodes: To remediate the issue, you can renew the Reserved Nodes with expiring leases by following these steps:
- Select the Reserved Node that is expiring soon by clicking the checkbox next to it.
- Click on the “Actions” dropdown menu above the Reserved Nodes list.
- Choose the “Modify Reserved Node” option from the dropdown.
- In the Modify Reserved Node window, you can extend the lease duration by selecting a new lease term and clicking the “Modify” button.
- Verify Lease Extension: Once you have extended the lease duration for the Reserved Node, go back to the Reserved Nodes tab and verify that the expiration date has been updated to a later date.
Using CLI
Using CLI
To remediate the issue of Redshift Reserved Node Lease Expiration in the next 30 days for AWS Redshift using AWS CLI, follow these step-by-step instructions:
-
List Reserved Nodes: First, list all the reserved nodes in your AWS Redshift cluster using the following AWS CLI command:
- Identify Expiring Nodes: Identify the reserved nodes that are expiring in the next 30 days from the output of the above command.
-
Purchase New Reserved Nodes: Purchase new reserved nodes to replace the expiring ones. You can use the following AWS CLI command to purchase a new reserved node:
Replace
<offering-id>with the ID of the reserved node offering you want to purchase and<count>with the number of nodes you want to purchase. -
Modify Existing Reserved Nodes: If you want to modify the existing reserved nodes instead of purchasing new ones, you can use the following AWS CLI command to modify the reserved node:
Replace
<node-id>with the ID of the reserved node you want to modify and<offering-id>with the ID of the new reserved node offering. -
Verify Changes: After purchasing new reserved nodes or modifying existing ones, verify the changes by listing the reserved nodes again using the
describe-reserved-nodescommand.
Using Python
Using Python
To remediate the issue of Redshift Reserved Node Lease Expiration in the next 30 days using Python, you can automate the process by checking the expiration dates of the reserved nodes and renewing them if necessary. Below are the step-by-step instructions to remediate this issue:Step 1: Install Boto3
Ensure that you have the Boto3 library installed in your Python environment. You can install it using pip:Step 2: Write Python Script
Create a Python script that will retrieve the expiration dates of the Redshift reserved nodes and renew them if the expiration date is within the next 30 days. Below is a sample script to achieve this:Step 3: Run the Script
Save the Python script to a file (e.g., This script will automatically check the expiration dates of the Redshift reserved nodes and renew them if the expiration date is within the next 30 days.Note: Ensure that you have the necessary permissions to describe and modify reserved nodes in Redshift.
remediate_redshift_reserved_nodes.py) and run it using the Python interpreter. Make sure you have the necessary AWS credentials configured for the Boto3 client to authenticate with AWS.