Describe the bug
When running ACK's IAM controller in the AWS European Sovereign Cloud (region eusc-de-east-1), it does not work out-of-the-box.
One has to explicitly configure the endpoints in the Helm values first:
aws:
endpoint_url: https://iam.eusc-de-east-1.amazonaws.eu
identity_endpoint_url: https://sts.eusc-de-east-1.amazonaws.eu
Contrary to that other controllers (e.g. the EKS controller) work without any additional configuration. I assume those controllers have newer AWS SDKs.
Steps to reproduce
Deploy the IAM controller to an EKS cluster in the region eusc-de-east-1. Before configuring the Identity Endpoint URL, you will see that the identity can not be assumed. Once the identity is assumed and before configuring the Endpoint URL, you will see that the controller is trying to use the wrong IAM API.
Expected outcome
The controller should work out-of-the-box.
Environment
- Kubernetes version: v1.36
- Using EKS (yes/no), if so version? yes, auto-mode, platform eks.9
- AWS service targeted (S3, RDS, etc.): IAM
Describe the bug
When running ACK's IAM controller in the AWS European Sovereign Cloud (region
eusc-de-east-1), it does not work out-of-the-box.One has to explicitly configure the endpoints in the Helm values first:
Contrary to that other controllers (e.g. the EKS controller) work without any additional configuration. I assume those controllers have newer AWS SDKs.
Steps to reproduce
Deploy the IAM controller to an EKS cluster in the region
eusc-de-east-1. Before configuring the Identity Endpoint URL, you will see that the identity can not be assumed. Once the identity is assumed and before configuring the Endpoint URL, you will see that the controller is trying to use the wrong IAM API.Expected outcome
The controller should work out-of-the-box.
Environment