Actually to add to this behavior, I updated all my dependencies to the latest (for reference, I am also using aws-classic). I reran the

up

command where i got a successful update, but the change was never applied (it ignored the error I guess?)

should this be filed as a bug, as it create a deadend in the IaC life cycle (requires manual intervention to unblock automatic deployment process). For now I have added some custom Boto3 check and action in the code, but would much rather have it embedded in resource management process