You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's from this fix introduced in CDK 2.57.0. To avoid it in the short term, you can probably pin to CDK 2.56.0.
But according to the docs, it probably means S3 access logs are probably not being written somewhere in the app. We got the same error when we upgraded and dug into the CDK code. It doesn't look like the fix catches the KMS encryption when logging to a different bucket, so there's probably a bucket with KMS encryption attempting to write it's logs to itself. Look for a bucket with serverAccessLogsPrefix set, no log bucket assigned and (the encryption type set explicitly to KMS or KMS_MANGED) OR (an encryption key set).
I got an error that only SSE-S3 is supported for access log bucket.
SSE-S3 is the only supported default bucket encryption for Server Access Logging target buckets --The text was updated successfully, but these errors were encountered: