The temporary-route approach is the smart part, and the revert to strict isolation is what makes it safe to reuse. I would snapshot the private route table before adding the bastion route, so rolling back is a restore rather than a reconstruction from memory.
Thanks, Albert. One check I would add after the revert is confirming no outbound route to the bastion remains, since that is easy to miss once access works again.
Rishabh Mishra
Cloud FullStack Developer & Design Engineer.
The temporary-route approach is the smart part, and the revert to strict isolation is what makes it safe to reuse. I would snapshot the private route table before adding the bastion route, so rolling back is a restore rather than a reconstruction from memory.