# Ensure Neptune Clusters Backup Retention Period

- Source: https://support.icompaas.com/support/solutions/articles/62000235136-ensure-neptune-clusters-backup-retention-period
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

### Profile Applicability:

-   Level 1
    

## Description:

Amazon Neptune provides automatic backups that can be retained for a configurable number of days. It is recommended that Neptune DB clusters have a Backup Retention Period of at least 7 days to ensure that data can be restored in case of accidental deletion, corruption, or other data loss events.

## Rationale:

-   Disaster Recovery: Having a sufficient backup retention period ensures that data can be restored if accidental deletions or failures occur.
    
-   Data Integrity: Longer backup retention allows for recovery from data corruption issues that might not be detected immediately.
    
-   Compliance: Many industry standards and regulations require a minimum backup retention period (e.g., SOC 2, ISO 27001).
    
-   Operational Resilience: Maintaining backups over several days enhances the ability to roll back to a known-good state.
    

## Impact:

Pros:

-   Ensures data availability for longer periods.
    
-   Supports disaster recovery and business continuity plans.
    
-   Helps in adhering to compliance and regulatory requirements.
    

Cons:

-   Increased Storage Costs: Longer retention periods may lead to higher backup storage costs.
    
-   Resource Management: Managing a larger set of backups might require additional operational oversight.
    

## Default Value:

-   The default Backup Retention Period for Neptune DB clusters is 1 day.
    

## Pre-Requisites:

-   AWS IAM permissions:
    
    -   neptune:DescribeDBClusters
        
    -   neptune:ModifyDBCluster
        
-   AWS CLI installed and configured.
    
-   Access to the AWS Management Console.
    

## Remediation:

## Test Plan:

### Using AWS Console:

1.  Sign in to the [AWS Management Console](https://console.aws.amazon.com/).
    
2.  Navigate to Amazon Neptune service.
    

  ![](https://support.icompaas.com/assets/kb/bf03ab8be5b457df.png)

3.  In the left navigation pane, click on Databases → DB Clusters.
    

         ![](https://support.icompaas.com/assets/kb/aaa7a3a1aabc3b2b.png)

4.  Select the Neptune DB cluster you want to check.
    

      ![](https://support.icompaas.com/assets/kb/8307c63fb9672e41.png)

5.  Under the Configuration tab, find Backup Retention Period.
    
    -   Pass: If the retention period is 7 days or more.
        
    -   Fail: If the retention period is less than 7 days.
        

       ![](https://support.icompaas.com/assets/kb/6bd9e1d2dd9bd4f6.png)

### Using AWS CLI:

List Neptune DB Clusters:

```generic
aws neptune describe-db-clusters --region <region> --query 'DBClusters[*].{DBClusterIdentifier:DBClusterIdentifier,BackupRetentionPeriod:BackupRetentionPeriod}'
```

Generic

Example output:

```generic
[   {     "DBClusterIdentifier": "my-neptune-cluster",     "BackupRetentionPeriod": 1   } 
]
```

Generic

-   Pass: If "BackupRetentionPeriod" is 7 or higher.
    
-   Fail: If "BackupRetentionPeriod" is less than 7.
    

## Implementation Steps:

### Using AWS Console:

1.  Sign in to the [AWS Management Console](https://console.aws.amazon.com/).
    
2.  Navigate to Amazon Neptune.
    

  ![](https://support.icompaas.com/assets/kb/5084860443a40838.png)

3.  Go to DB Clusters and select the cluster to modify.
    

    ![](https://support.icompaas.com/assets/kb/f022cc03336034b3.png)

4.  Click on Modify Cluster.
    

      ![](https://support.icompaas.com/assets/kb/327433d438e2cc3c.png)

5.  In the Backup section, set Backup Retention Period to 7 or more days.
    

       ![](https://support.icompaas.com/assets/kb/fa5d360bafd5dad9.png)

6.  Review your changes and click Continue.
    

  ![](https://support.icompaas.com/assets/kb/c0c9c0d78e3653e5.png)

7.  Select Apply Immediately or schedule the changes during the next maintenance window.
    

  ![](https://support.icompaas.com/assets/kb/0257f11b39169df2.png)

8.  Click Modify Cluster.
    

### Using AWS CLI:

Set Backup Retention Period to 7 Days

```generic
aws neptune modify-db-cluster \ --db-cluster-identifier <db-cluster-identifier> \ --backup-retention-period 7 \ --apply-immediately \ --region <region>
```

Generic

Verify the Changes:

```generic
aws neptune describe-db-clusters --region <region> \ 
--query 'DBClusters[*].{DBClusterIdentifier:DBClusterIdentifier,BackupRetentionPeriod:BackupRetentionPeriod}'
```

Generic

Expected output:

```generic
[  {    "DBClusterIdentifier": "my-neptune-cluster",     "BackupRetentionPeriod": 7  } ]
```

Generic

  

## Backout Plan:

If the change causes unintended issues or if a different backup retention period is needed:

1.  Go to Amazon Neptune → DB Clusters.
    
2.  Select the cluster and choose Modify Cluster.
    
3.  Set Backup Retention Period back to the previous value.
    
4.  Apply the changes immediately or during the next maintenance window.
    

## References:

1.  [Amazon Neptune Documentation](https://docs.aws.amazon.com/neptune/latest/userguide/what-is-amazon-neptune.html)
    
2.  [AWS CLI Neptune Documentation](https://docs.aws.amazon.com/cli/latest/reference/neptune/index.html)[](https://docs.aws.amazon.com/neptune/latest/userguide/backups.html)
    
3.  [Managing Amazon Neptune Backups](https://docs.aws.amazon.com/neptune/latest/userguide/backups.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
