-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supplying region should be optional #305
Comments
We plan to deploy our application on multiple regions too. One of the obstacle we have right now is this issue. |
I would like to work on this. Would it be possible to assign this to me? |
Please also enable to choose global endpoint. |
I don't think this is supported in js v3 yet, which will prevent our adoption of this aws/aws-sdk-js-v3#4568 |
are there any updates on this? |
I'm using this action to assume a role for CFN deployments. In the case where I might want to use the tool to deploy to multiple regions, I would need to update my action for each region I wish to deploy into. I'd rather embed this in my deployment tool config than the github action.
An explicit Region is not required when assuming a role, correct? Would it be reasonable to request making this optional? It seems like it is mostly used to get a Regional STS endpoint?
The text was updated successfully, but these errors were encountered: