Given a Tech document that addresses the risk of change, the rollback plan, the security implications etc, and a suite of metrics demonstrating load and failure conditions with appropriate alerting. And of course the PR with appropriate test suite, shown to work in a test environment in concert with the rest of the ecosystem, that stuff is just table sakes. convince a director to approve the change. Ideally a director that doesn't report to the same vp as your org.
You go through the normal change process like everybody else.
There is no such thing as a "safe" change.
The only exception to this is when stuff is on fire, and, practically by definition at that point, there is no such thing as a "safe" change.