Running the command as amp would be counter to what I have been told in the linked issue.
But having now done that and creating a new instance afterwards results in the same exact issue.
Also: I can provide root-ssh-access and admin-amp access (for debugging by support).