User Story:

The ingress operator should create route53 and tagging clients in the eusc-de-east-1 region for EUSC. Otherwise, the request will fail due to credential region mismatch. Additionally, we need to support custom endpoint for ELB v2 (to create NLB in EUS Cloud).

As of now, due to AWS SDK v1 EOL, we can only support EUSC via custom service endpoints.

Acceptance Criteria:

Description of criteria:

• Route 53 and Tagging client should point to eusc-de-east-1.
• ELB v2 client should order custom endpoint. This means taking the same URL as ELB (v1) because the service ID is the same.

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• https://github.com/openshift/cluster-ingress-operator/blob/master/pkg/dns/aws/dns.go 

This requires/does not require a design proposal.
This requires/does not require a feature gate.