AWS region mentioned not considered and still use us-east-1

[Zeeshan Ali Shah]

juju version:
juju --version 2.9.26-ubuntu-amd64

juju add-credential was
This operation can be applied to both a copy on this client and to the one on a controller.
Do you want to add a credential to:
    1. client only (--client)
    2. controller "microk8s-localhost" only (--controller microk8s-localhost)
    3. both (--client --controller microk8s-localhost)
Enter your choice, or type Q|q to quit: 3
Enter credential name: k8s-aws2

Regions
  us-east-1
  us-east-2
  us-west-1
  us-west-2
  ca-central-1
  eu-west-1
  eu-west-2
  eu-west-3
  eu-central-1
  eu-north-1
  eu-south-1
  af-south-1
  ap-east-1
  ap-south-1
  ap-southeast-1
  ap-southeast-2
  ap-southeast-3
  ap-northeast-1
  ap-northeast-2
  ap-northeast-3
  me-south-1
  sa-east-1

Select region [any region, credential is not region specific]: eu-central-1 ## <— Selected EU-Central-1

Using auth-type "access-key".

Enter access-key: AKIAXZX2L7EAOLHWBABT

Enter secret-key: zxzxxzxzxzxxxxxzxzxzxzxzxzxx

Credential "k8s-aws2" added locally for cloud "aws".

ubuntu@ip-172-31-34-21:~$ juju clouds
Only clouds with registered credentials are shown.
There are more clouds, use --all to see them.

Clouds available on the controller:
Cloud Regions Default Type
microk8s 1 localhost k8s

Clouds available on the client:
Cloud Regions Default Type Credentials Source Description
aws 22 us-east-1 ec2 1 public Amazon Web Services ### <—— It selected us-east-1 and did not Consider previous mentioned EU-Central-1

[Heather Lanigan (hmlanigan)]

@Zeeshan Ali Shah, Does this behavior prevent use of AWS in your scenario?

Agreed that asking for a region then displaying a different one is bad UX which should be addressed.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.