400 Bad Request when Exposing external HTTPS service

SRV answer is in the other thread: Direct traffic to AWS ECS services using SRV records

Lack of change is odd, is it still showing up as HTTP when you inspect the admin API, with no errors in the controller logs indicating that the sync failed?