User Story:

The installer should support EU Sovereign Cloud regions as valid install regions. As of now, there is only 1 available region eusc-de-east-1.

Due to the AWS SDK v1 EOL, the default endpoint resolution support for this new region is only available in AWS SDK v2. Even though the installer soon runs on AWS SDK v2, various cluster operators are still on AWS SDK v1. Thus, we can only support this EUSC via custom service endpoint until all operators migrates to AWS SDK v2.

Acceptance Criteria:

Description of criteria:

• The installer accepts eusc-de-east-1 as a valid install region.
• The installer makes request to the eusc-de-east-1 endpoints to interact with AWS API.
• The installer can provision necessary cloud resouces for the cluster. This does not count resources managed by cluster operators such ingress.
• The installer can destroy the resources in eusc-de-east-1 region.

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• IAM service principal EC2 domain may need updating.
• Custom endpoint has a signing region property. The SDK may return the incorrect one so we need to make sure it points to eusc-de-east-1 ** as expected.
• The destroy code creates a tagging client in us-east-1, which needs skipping in EUS Cloud.

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