admin管理员组文章数量:1435090
Very recently, my deployment system started acting weird and I'm dead in the water until I find a fix.
Original error:
An error occurred while fetching the SSM parameter "/serverless-framework/state/s3-bucket":
User: arn:aws:iam::0123456789:user/insert-real-user-here is not authorized to perform:
ssm:GetParameter on resource:
arn:aws:ssm:us-east-1:025132599338:parameter/serverless-framework/state/s3-bucket
because no identity-based policy allows the ssm:GetParameter action
Thing is, my serverless.yml file didn't change, and it points to a different region. (I.e. we don't use us-east-1).
ChatGPT and the docs haven't helped me debug what changed, and the change was sudden.
I've been trying to edit serverless.yml to specify a custom Deployment Bucket. I can see the name of the usual bucket within the region that I actually use. I've tried making other buckets. No joy.
So the simple question is, what would folks do next in order to debug this?
I have tried adding a state: to the top level of my serverless.yml file, and added my own S3 bucket as a parameter there, but I'm not sure that I'm using that correctly.
Very recently, my deployment system started acting weird and I'm dead in the water until I find a fix.
Original error:
An error occurred while fetching the SSM parameter "/serverless-framework/state/s3-bucket":
User: arn:aws:iam::0123456789:user/insert-real-user-here is not authorized to perform:
ssm:GetParameter on resource:
arn:aws:ssm:us-east-1:025132599338:parameter/serverless-framework/state/s3-bucket
because no identity-based policy allows the ssm:GetParameter action
Thing is, my serverless.yml file didn't change, and it points to a different region. (I.e. we don't use us-east-1).
ChatGPT and the docs haven't helped me debug what changed, and the change was sudden.
I've been trying to edit serverless.yml to specify a custom Deployment Bucket. I can see the name of the usual bucket within the region that I actually use. I've tried making other buckets. No joy.
So the simple question is, what would folks do next in order to debug this?
I have tried adding a state: to the top level of my serverless.yml file, and added my own S3 bucket as a parameter there, but I'm not sure that I'm using that correctly.
Share Improve this question edited Nov 19, 2024 at 13:27 ahuemmer 2,05913 gold badges27 silver badges36 bronze badges asked Nov 16, 2024 at 19:10 Christian NallyChristian Nally 11 bronze badge 1- I ended up fixing this by adding a bunch of permissions to a user that didn't need to be there before. I also had to add the deployment bucket name to serverless.yml where it wasn't needed before. Comments are still invited, in case there's something obvious that was happening. – Christian Nally Commented Nov 17, 2024 at 8:34
1 Answer
Reset to default 0I do have the similar problem that occurs today. Mine situation is even simpler. I am deploying to the localstack by the serverless-localstack plugin. It works all good last week but it failed today. I didn't change anything at all.
本文标签：
版权声明：本文标题：serverless Region changed? An error occurred while fetching the SSM parameter "serverless-frameworkstates3-bucket&q 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1745646346a2668161.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。
发表评论