Closed pahud closed 1 hour ago
internal tracking: V1241367978
Can't reproduce this issue. Looking at the internal tracking ticket, this happens when encryptionKey: dummyKey
creates the policy with same action/condition as crossAccountAccessPolicy
which will cause conflicts.
When I run the synth, condition created by encryptionKey: dummyKey
is
Condition:
StringEquals:
kms:ViaService:
Fn::Join:
- ""
- - secretsmanager.
- Ref: AWS::Region
- .amazonaws.com
while the condition in crossAccountAccessPolicy
is
{
'StringEquals': { 'kms:ViaService': 'secretsmanager.us-east-1.amazonaws.com'}
}
The region is not resolved in the output template hence not causing conflicts. I'm going to close the issue for now. If this issue still exists, feel free to re-open it.
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.
Describe the bug
CDK synth is having
Resolution error: All principals in a PolicyStatement must have the same Conditions
by adding a cross-account plicy.Expected Behavior
synthesize with no error
Current Behavior
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.126.0 (build fb74c41)
Framework Version
No response
Node.js Version
v20.6.1
OS
linux
Language
TypeScript
Language Version
No response
Other information
No response