Region is always us-east-2 when using console link through Okta

[mikeparker]

I'm using

console --link --skip-prompt --username=x --password-x --mfa-token=x with env vars

SAML2AWS_IDP_PROVIDER=Okta
SAML2AWS_URL=https://<url>
SAML2AWS_ROLE=<role>

Which works, it logs me on to AWS but its always us-east-2. I've tried setting the region by: arg: --region=us-east-1 Env: SAML2AWS_REGION=us-east-1

And neither logs me on to us-east-1. Is this working as expected? Is there any way to set the region to log on to with the console?

[duckfez]

So outside of saml2aws this is often part of the "relay state" in SAML. In our Okta defintion for the app we have a relay state defined like so:

https://console.aws.amazon.com/console/home?region=us-west-2

I'm not sure if you can pass a relay state through saml2aws or not.