Storage Gateway Recovery Point Should Be Created
More Info:
This rule checksif a recovery point was created for Amazon Relational Database Service (Amazon RDS). The rule is NON_COMPLIANT if the Amazon RDS instance does not have a corresponding recovery pointRisk Level
HighAddress
ConfigurationCompliance Standards
CBP,SEBITriage and Remediation
Remediation
Using Console
Using Console
To remediate the misconfiguration of not having Storage Gateway Recovery Point created for AWS EC2 using the AWS console, follow these step-by-step instructions:
- Sign in to the AWS Management Console: Go to https://aws.amazon.com/ and sign in to your AWS account.
- Navigate to AWS Storage Gateway: Go to the AWS Management Console and search for “Storage Gateway” in the services search bar.
- Select your Storage Gateway: In the Storage Gateway console, select the Storage Gateway that is associated with your EC2 instance.
- Create a Recovery Point: Within the Storage Gateway console, navigate to the “Volumes” section and select the volume that is associated with your EC2 instance.
- Initiate a Snapshot: In the volume details page, locate the option to create a recovery point or snapshot. Click on the “Create Snapshot” or “Create Recovery Point” button.
- Configure Snapshot settings: Follow the on-screen instructions to configure the snapshot settings, such as the snapshot description, frequency, and retention period.
- Review and Confirm: Review the snapshot settings to ensure they meet your requirements, then click on the “Create Snapshot” or “Create Recovery Point” button to initiate the snapshot creation process.
- Monitor Snapshot Creation: Monitor the snapshot creation process in the Storage Gateway console. Once the snapshot is successfully created, you have now remediated the misconfiguration of not having a Storage Gateway Recovery Point created for your AWS EC2 instance.
Using CLI
Using CLI
To remediate the misconfiguration of not having Storage Gateway Recovery Point created for AWS EC2 using AWS CLI, you can follow these steps:
- Install and Configure AWS CLI: If you haven’t already, install and configure the AWS Command Line Interface (CLI) on your local machine. You can refer to the official AWS documentation for instructions on how to do this.
- Enable Storage Gateway for EC2 Instance: Ensure that the AWS Storage Gateway service is enabled for the specific EC2 instance that requires a Recovery Point. You can do this by navigating to the AWS Management Console, selecting the EC2 service, choosing the specific instance, and enabling the Storage Gateway service.
-
Create a Recovery Point using AWS CLI:
Use the AWS CLI to create a Recovery Point for the Storage Gateway associated with the EC2 instance. You can use the following command to create a Recovery Point:
Replace
<VOLUME_ARN>with the Amazon Resource Name (ARN) of the volume associated with the EC2 instance. -
Verify the Recovery Point:
After executing the command, verify that the Recovery Point has been successfully created by checking the AWS Storage Gateway console or by running the following command:
Replace
<GATEWAY_ARN>with the ARN of the Storage Gateway associated with the EC2 instance. - Set up Automated Recovery Point Creation (Optional): To ensure that Recovery Points are created regularly, you can set up a scheduled task or automation using AWS CloudWatch Events or AWS Lambda to trigger the creation of Recovery Points at specified intervals.
Using Python
Using Python
To remediate the misconfiguration of not having Storage Gateway recovery points created for AWS EC2 instances using Python, you can follow these steps:
-
Install the AWS SDK for Python (Boto3) by running the following command:
- Create a Python script to automate the process of creating recovery points for the AWS Storage Gateway. Below is a sample script that you can use:
-
Replace
'YOUR_GATEWAY_ARN'with the actual ARN of the Storage Gateway that is associated with the EC2 instance. - Run the Python script to create a recovery point for the specified Storage Gateway. This will ensure that recovery points are created for the EC2 instance.