Ensure all EBS volumes are included in a backup plan to maintain data integrity and availability.
Rule | EBS volumes should be in a backup plan |
Framework | GxP EU Annex 11 |
Severity | ✔ High |
Rule/Policy Description:
EBS volumes should be included in a backup plan to comply with GxP EU Annex 11 regulations. This ensures that critical data stored on Amazon Elastic Block Store (EBS) volumes, which are used for persistent storage in Amazon Web Services (AWS), are regularly backed up and recoverable in case of data loss or system failure.
Troubleshooting Steps:
If a backup plan for EBS volumes is not already in place, follow the steps below to troubleshoot and implement the necessary backup strategy:
Remediation Steps:
Step 1: Define Backup Requirements
Step 2: Choose Backup Methodology
Step 3: Implement Backup Solution
Step 4: Test and Validate Backups
Step 5: Monitor Backup Compliance
Necessary Codes (if applicable):
There are no specific codes required for this policy. However, you may use AWS CLI commands to perform actions related to EBS snapshot management.
CLI Commands for EBS Snapshot Management:
aws ec2 create-snapshot --volume-id <EBS_VOLUME_ID>
aws ec2 describe-snapshots
aws ec2 create-volume --snapshot-id <SNAPSHOT_ID>
Note: Replace
<EBS_VOLUME_ID>
with the actual EBS volume ID and <SNAPSHOT_ID>
with the actual snapshot ID.Ensure that the AWS CLI is properly configured with appropriate IAM credentials before executing these commands.
Following the above steps and necessary CLI commands, you can establish and maintain a backup plan for EBS volumes that complies with GxP EU Annex 11 regulations.