aws / aws/aws-cdk

neptune: construct should allow restoration from a snapshot

Open
#24,972 12 comments 0 reactions 0 assignees View on GitHub
@aws-cdk/aws-neptune effort/small feature-request mixins p2
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

### Describe the feature

The snapshotIdentifier would work very similar to the underlying RDS feature (https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_rds.CfnDBCluster.html). This would take in an ARN or another identifier and restore the Neptune database from the snapshot that matches the identifier.

This change would work as a construct built here https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-neptune-alpha.DatabaseCluster.html

### Use Case

Users require the ability to save snapshots of their Neptune database and restore from that snapshot in the case of a critical failure. This field would allow restoration from a snapshot while deploying applications that utilize cloud formation.

### Proposed Solution

Inclusion of the snapshotIdenfier property built into RDS - https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_rds.CfnDBCluster.html

### Other Information

_No response_

### Acknowledgements

- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.73.0

### Environment details (OS name and version, etc.)

Mac OSX, Linux

Contributor guide

Open the contributing guide

Research direction

Start at the aws-neptune-alpha.DatabaseCluster construct and compare its supported configuration with the AWS RDS CfnDBCluster snapshotIdentifier documentation linked in the issue. Trace how DatabaseCluster properties are represented in the synthesized CloudFormation template, then verify that a snapshot identifier produces the expected Neptune restoration configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cloud, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.