aws / aws/aws-cdk

(aws-rds): no way to specify CloudWatch log group retention

Open
#23,720 1 comment 5 reactions 0 assignees View on GitHub
@aws-cdk/aws-rds effort/medium feature-request p2
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

### Describe the feature

At present when creating RDS Proxies, there is no way to specify the retention period for the resulting log group. The log group does seem to have a predictable name (in our case it seems to default to `/aws/rds/proxy/proxy` - not sure if this is a universal or how that changes if you deploy multiple proxies in an account).

It seems that it would be relatively straightforward to allow the configuration of log group retention via a `logRetention` property similar to the one which exists for Lambda functions - this could then create a `LogRetention` resource rather than forcing the user to do it manually.

### Use Case

Most people don't want infinite log retention and the associated costs. The ability to easily set a retention period would be helpful.

### Proposed Solution

allow the configuration of log group retention via a `logRetention` property similar to the one which exists for Lambda functions - this could then automatically create a `LogRetention` resource under the hood rather than forcing the user to do it manually.

### 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.49.0

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

N/A

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the RDS Proxy implementation and the existing Lambda support for the `logRetention` property and `LogRetention` resource. Confirm how proxy log-group names behave when multiple proxies are deployed, then define the property behavior and verify that the generated retention resource is created correctly.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.