01 Run describe-db-clusters command (OSX/Linux/UNIX) using the name of the Neptune cluster that you want to re-create as identifier to describe the configuration metadata for the selected database cluster:
aws neptune describe-db-clusters
--region us-east-1
--db-cluster-identifier cc-neptune-database-v3
02 The command output should return the requested configuration information:
{
"DBClusters": [
{
"PubliclyAccessible": false,
"LicenseModel": "amazon-license",
"ClusterCreateTime": "2018-10-31T15:42:54.084Z",
"CopyTagsToSnapshot": false,
"Engine": "neptune",
"MultiAZ": false,
"DBParameterGroups": [
{
"DBParameterGroupName": "default.neptune1",
"ParameterApplyStatus": "in-sync"
}
],
"PerformanceInsightsEnabled": false,
"AutoMinorVersionUpgrade": true,
"PreferredBackupWindow": "04:15-04:45",
"PromotionTier": 1,
...
"ReadReplicaDBClusterIdentifiers": [],
"AllocatedStorage": 1,
"DBClusterArn": "arn:aws:rds:us-east-1:123456789012:db:cc-neptune-database-v3",
"BackupRetentionPeriod": 7,
"PreferredMaintenanceWindow": "fri:05:23-fri:05:53",
"DBClusterStatus": "available",
"IAMDatabaseAuthenticationEnabled": true,
"EngineVersion": "1.0.1.0",
"AvailabilityZone": "us-east-1b",
"DomainMemberships": [],
"DBClusterIdentifier": "cc-neptune-db-cluster",
"DbiResourceId": "db-AAAABBBBCCCCDDDDAAAABBBBCD",
"CACertificateIdentifier": "rds-ca-2015",
"StorageEncrypted": false,
"DBClusterClass": "db.r4.large",
"DBClusterIdentifier": "cc-neptune-database-v3"
}
]
}
03 Run create-db-cluster command (OSX/Linux/UNIX) to create a new Amazon Neptune database cluster and deploy it to a Multi-AZ environment using the metadata returned at the previous step for configuration and the --multi-az command parameter for enabling the feature:
aws neptune create-db-cluster
--region us-east-1
--db-cluster-identifier cc-neptune-database-v4
--db-cluster-class db.r4.large
--engine neptune
--engine-version 1.0.1.0
--db-cluster-identifier cc-neptune-db-cluster
--availability-zone us-east-1b
--db-subnet-group-name default
--option-group-name default:neptune-1-0
--db-parameter-group-name default.neptune1
--auto-minor-version-upgrade
--no-publicly-accessible
--promotion-tier 1
--multi-az
04 The command output should return the metadata for the new Neptune database cluster:
{
"DBCluster": {
"PubliclyAccessible": false,
"LicenseModel": "amazon-license",
"CopyTagsToSnapshot": false,
"OptionGroupMemberships": [
{
"Status": "in-sync",
"OptionGroupName": "default:neptune-1-0"
}
],
"PendingModifiedValues": {},
"Engine": "neptune",
"MultiAZ": true,
"DBParameterGroups": [
{
"DBParameterGroupName": "default.neptune1",
"ParameterApplyStatus": "in-sync"
}
],
"AutoMinorVersionUpgrade": true,
"PreferredBackupWindow": "04:32-05:02",
...
"AllocatedStorage": 1,
"BackupRetentionPeriod": 7,
"PreferredMaintenanceWindow": "fri:10:23-fri:10:53",
"DBClusterStatus": "creating",
"IAMDatabaseAuthenticationEnabled": false,
"EngineVersion": "1.0.1.0",
"AvailabilityZone": "us-east-1b",
"DomainMemberships": [],
"DBClusterIdentifier": "cc-neptune-db-cluster",
"StorageType": "aurora",
"DbiResourceId": "db-AAAABBBBCCCCDDDDAAAABBBBAA",
"CACertificateIdentifier": "rds-ca-2015",
"StorageEncrypted": false,
"DBClusterClass": "db.r4.large",
"DbClusterPort": 0,
"DBClusterIdentifier": "cc-neptune-database-v4"
}
}
05 Once the new Neptune cluster is created, replace the source cluster endpoint with the new database cluster endpoint within your application configuration.
06 Now it is safe to remove the source Neptune cluster from your AWS account to avoid further charges. To delete the required database cluster, execute describe-db-clusters command (OSX/Linux/UNIX) using the name of the Neptune resource that you want to remove as identifier:
aws neptune delete-db-cluster
--region us-east-1
--db-cluster-identifier cc-neptune-database-v3
07 The command output should return the command request metadata:
{
"DBCluster": {
"PubliclyAccessible": false,
"MonitoringInterval": 0,
"LicenseModel": "amazon-license",
"DBClusterStatus": "deleting",
"IAMDatabaseAuthenticationEnabled": false,
"EngineVersion": "1.0.1.0",
"AvailabilityZone": "us-east-1b",
...
"DBClusterIdentifier": "cc-neptune-db-cluster",
"StorageType": "aurora",
"DbiResourceId": "db-AAAABBBBCCCCDDDDAAAABBBBAA",
"CACertificateIdentifier": "rds-ca-2015",
"StorageEncrypted": false,
"DBClusterClass": "db.r4.large",
"DbClusterPort": 0,
"DBClusterIdentifier": "cc-neptune-database-v3"
}
}
08 If required, repeat steps no. 1 – 7 to relaunch other Amazon Neptune database clusters within a Multi-AZ environment, available in the current region.
09 Change the AWS region by updating the --region command parameter value and repeat steps no. 1 – 8 to perform the remediation process for other regions.
Reliability 