just a heads-up about a bug I’ve run into twice: I made a change to some IAM permissions, and it said “Press ENTER to redeploy infrastructure”. I do that, and it just runs through the stacks saying no changes. 🤔 so I ^C the sst start proc, run it again, and then it errors out & quits:

Cannot delete ChangeSet in status CREATE_IN_PROGRESS

 ❌  dev-microservices-api-users failed: The dev-microservices-api-users stack failed to deploy.

seems like it’s doing a change in the background and the sst start proc is not aware of it. NOTE: I’m on 0.53.3, so it’s possible this was fixed in 0.53.4

it's about permissions, you need to add DeleteChangeSet permissions to your iam role

which IAM role?

your AWS user

hmm, I don’t think that’s the problem. I’m an admin user

oh if you are super admin then that's a separate problem, but for me that was an issue and we resolved it by adding DeleteChangeSet to my user but I agree that shouldn't be a problem if you are a super admin

and now that I think about it, my GitHub action for deploying probably shouldn’t be using an admin IAM user.. heh. but it needs so many different permissions, it’s hard to know what those should be

yeah it's hard to come up with minimal permissions, IAM is hard for good reasons, it takes a few trial and failure I guess starting from very minimum and adding up needed permissions

Why your project is called

microservies

? isn’t that redundant?

we have separate front & back end. the projects are called

v2-frontend

and

v2-microservices

Mmmm.

right. we have one product

Not saying is wrong… just been trying to avoid naming stacks in the technical way.

it’s so devs can immediately tell what is what. also reduces any chance of making mistakes.. all the names match up with the repository, etc

Makes sense.