Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking: [aws-backup] Support for lockConfiguration in higher construct #21076

Closed
sachin911 opened this issue Jul 9, 2022 · 1 comment · Fixed by #21105
Closed

Tracking: [aws-backup] Support for lockConfiguration in higher construct #21076

sachin911 opened this issue Jul 9, 2022 · 1 comment · Fixed by #21105
Labels
management/tracking Issues that track a subject or multiple issues

Comments

@sachin911
Copy link

Overview

AWS Backup is a fully managed backup service that makes it easy to centralize and automate the backup of data across AWS services in the cloud and on premises. Using AWS Backup, you can configure backup policies and monitor backup activity for your AWS resources in one place. AWS Backup automates and consolidates backup tasks that were previously performed service-by-service, and removes the need to create custom scripts and manual processes. With just a few clicks on the AWS Backup console, you can create backup policies that automate backup schedules and retention management.

AWS Backup has introduced a new feature for immutable backups using a feature called lockConfiguration. This is currently not available as part of the standard backup construct.

AWS Docs

Link to the service’s CDK Construct Library API reference page.

https://docs.aws.amazon.com/cdk/api/v1/docs/@aws-cdk_aws-backup.BackupPlan.html

Maturity: CloudFormation Resources Only

CloudFormation Resources Only

Implementation

https://docs.aws.amazon.com/cdk/api/v1/docs/@aws-cdk_aws-backup.BackupPlan.html

Issue list

  • [ ]
@sachin911 sachin911 added the management/tracking Issues that track a subject or multiple issues label Jul 9, 2022
jogold added a commit to jogold/aws-cdk that referenced this issue Jul 12, 2022
AWS Backup Vault Lock enforces a write-once, read-many (WORM)
setting for all the backups you store and create in a backup
vault.

https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html

Closes aws#21076
@jogold jogold mentioned this issue Jul 12, 2022
4 tasks
@mergify mergify bot closed this as completed in #21105 Jul 12, 2022
mergify bot pushed a commit that referenced this issue Jul 12, 2022
AWS Backup Vault Lock enforces a write-once, read-many (WORM)
setting for all the backups you store and create in a backup
vault.

https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html

Closes #21076


----

### All Submissions:

* [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
management/tracking Issues that track a subject or multiple issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant