While it is somewhat pathological to rename a param, doing so will break the stack. What appears to happen:
- grants the custom resource permissions to manage the param on initial run
- rename the param
- try to run and custom resource tries to create the new param and
- boom:
...is not authorized to perform: ssm:PutParameter on resource...
I'm guessing because the grant hasn't changed yet. And even if it had, we'd have the problem where the grant won't let you remove the old param.
While it is somewhat pathological to rename a param, doing so will break the stack. What appears to happen:
...is not authorized to perform: ssm:PutParameter on resource...I'm guessing because the grant hasn't changed yet. And even if it had, we'd have the problem where the grant won't let you remove the old param.