Open herson opened 2 years ago
Thanks for reporting! This appears to be caused by changes to the permissions attached to the role that the Amplify console creates. Those permissions have been scoped down compared to how they used to be. You can remedy this by updating your fork to the latest version in this repo, as well as adding the following permissions to the IAM role amplify created in your account:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ssm:PutParameter",
"ssm:DeleteParameter",
"ssm:GetParametersByPath",
"ssm:GetParameters",
"ssm:GetParameter",
"ssm:DeleteParameters"
],
"Resource": [
"arn:aws:ssm:*:*:parameter/serverless-shopping-cart-demo/*"
]
},
{
"Effect": "Allow",
"Action": "cloudformation:CreateChangeSet",
"Resource": "arn:aws:cloudformation:*:aws:transform/Serverless-2016-10-31"
},
{
"Effect": "Allow",
"Action": [
"lambda:ListVersionsByFunction",
"lambda:CreateAlias",
"lambda:DeleteAlias",
"lambda:PutFunctionConcurrency"
],
"Resource": "arn:aws:lambda:*:*:function:amplify*"
}
]
}
Hi, I just tried to test this with the instructions provided and build fails on:
Checked permissions and that
CreateChangeSet
is set on the newly created role: