-
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
(stepfunctions): SqsSendMessage is not adding policy sqs:sendMessage since v2.127.0 #29203
Comments
Furthermore, if I add this const { stateMachine } = buildStateMachine(this, { definitionBody });
console.log(JSON.stringify((stateMachine.node.children[0] as any).defaultPolicy.document.statements, null, 2)); I get [
{
"Action": "sqs:SendMessage",
"Effect": "Allow",
"Resource": "${Token[TOKEN.632]}"
},
{
"Action": [
"logs:CreateLogDelivery",
"logs:GetLogDelivery",
"logs:UpdateLogDelivery",
"logs:DeleteLogDelivery",
"logs:ListLogDeliveries",
"logs:PutResourcePolicy",
"logs:DescribeResourcePolicies",
"logs:DescribeLogGroups"
],
"Effect": "Allow",
"Resource": "*"
},
{
"Action": [
"logs:PutResourcePolicy",
"logs:DescribeResourcePolicies",
"logs:DescribeLogGroups"
],
"Effect": "Allow",
"Resource": "arn:${Token[AWS.Partition.4]}:logs:${Token[AWS.Region.5]}:${Token[AWS.AccountId.1]}:*"
}
] Which mean that at the moment of creation it exists, but it doesn't end up in the CloudFormation Template |
Sounds like this issue should go to aws-solutions-constructs ? |
I was thinking the same but, why does it happen with v2.127.0 or higher and not with v2.126.0 and lower? |
I have checked a bit further the v2.127.0 release As soon as I rollback this file and use as it was in v2.126.0, it starts working again. |
With the changes in v2.127.0 when we bind
|
By moving back the statement |
|
Yes, this is a Solutions Constructs issue and should be remedied when we address awslabs/aws-solutions-constructs#1077. While we hesitate to give an exact ETA, it is imminent. |
Describe the bug
Permission missing for step function to perform SQS's send message action when using SqsSendMessage construct together with
@aws-solutions-constructs/aws-s3-stepfunctions
.It happens to any @aws-solutions-constructs that uses
buildStateMachine
Expected Behavior
CloudFormation output for the State Machine should contain
Current Behavior
CloudFormation output for the State Machine doesn't contain
Difference
Reproduction Steps
Create a step function using
SqsSendMessage
frompackage.json
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.127.0
Framework Version
No response
Node.js Version
20.11.1
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: