I’ve just updated one of my repositories from serverless 4.4.7 to 4.4.9.
I was getting permissions errors during the first deployment as it was trying to do things in us-east-1, which is an AWS region we don’t use, and therefore restrict access to. Digging into it, I found these errors were related to the State feature introduced in 4.4.8.
I saw in the documentation that there’s a (reasonably complicated) way of working around this, but I wondered if this is actually deliberate or a bug?
If the former, why would serverless insist on using us-east-1 for a state bucket rather than the AWS region specified in serverless.yml?