aws / aws/aws-cdk

aws-certificatemanager: Ability to turn on xray tracing on CertificateRequestorFunction lambda function

Open
#25,133 1 comment 0 reactions 0 assignees View on GitHub
@aws-cdk/aws-certificatemanager 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

I would like to enable tracing on the CertificateRequestorFunction lambda function which is created apart of the DnsValidatedCertificate class via a property.

https://github.com/aws/aws-cdk/blob/d0259230661edd23b0869a7ce6a783620ecd1ad2/packages/aws-cdk-lib/aws-certificatemanager/lib/dns-validated-certificate.ts#L109-L115

### Use Case

I have a requirement where xray tracing must be enabled on all components deployed within my account.

I believe the only way to do this as of right now might be to use the escape hatch, but that's not ideal. It would be much nicer if I could set this via a property.

### Proposed Solution

_No response_

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

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

Amazon Linux 2

Contributor guide

Open the contributing guide

Research direction

Start in packages/aws-cdk-lib/aws-certificatemanager/lib/dns-validated-certificate.ts at lines 109-115, where CertificateRequestorFunction is created. Trace how the DnsValidatedCertificate properties reach that Lambda and determine the appropriate property for enabling X-Ray tracing. Done means the property enables tracing on the synthesized function without requiring an escape hatch.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.