-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[cloudfront] High level support for AWS::CloudFront::RealtimeLogConfig resource type #10202
Comments
I just noticed a low-level CFN Resource constructs support will be added through automation in #10201, although I'd still be interested to have a high-level support of it. |
Hi @laurrentt, as you've discovered, CFN Resources are periodically generated from the AWS CloudFormation Resource Specification automatically and are usually up within a few days to a week. I'll update this issue to be a high-level feature request. |
Hi, |
@mrvini also trying to do this in serverless-nextjs/serverless-next.js#2284 and hitting the same roadblock. Would love not to have to update logs here. Did you ever find a workaround for this? Does AWS expose any ability to set the distribution id yet? Edit: |
Same here, any news on this? |
Are there any plans of implementing this feature? |
Any updated on this? There still seems to be no way for us to access the RealtimeLogConfig of the distro via CDK. |
+1 - any update on this? |
Any update? |
Any updates on this issue? There is not way to access each behavior's real time log configuration from the L2 construct. |
I believe this #26808 closes this issue. Will reopen if needed. |
|
Add support for the
AWS::CloudFront::RealtimeLogConfig
resource type2 days ago, CloudFormation added a new resource type for configuring realtime logging on CloudFront cache behaviours. Obviously being such a recent addition to CloudFormation, I understand this is not yet implemented in CDK. However I thought creating an issue would signify interest and also serve as a way to track the implementation progress.
The text was updated successfully, but these errors were encountered: