Skip to content
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

How do I specify ap-northeast-1 as the region to authenticate in CodeWhisperer reconnections? #3662

Closed
WhiteRaven777 opened this issue May 11, 2023 · 3 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@WhiteRaven777
Copy link

Your Environment

  • OS: Kubuntu 22.04 LTS (Linux 5.15.0-71-generic)
  • JetBrains product: GoLand 2023.1.1
  • JetBrains product version: Build #GO-231.8770.71, built on May 3, 2023
  • AWS Toolkit version: AWS Toolkit For JetBrains 1.67-231
  • SAM CLI version: SAM CLI, version 1.81.0
  • JVM/Python version: JRE 17.0.6+10-b829.9 amd64

Question

We have a fee-based contract for the use of Amazon CodeWhisperer on AWS.
We use AWS IAM Identify Center (formerly AWS SSO) for user authentication in AWS.
The AWS IAM Identify Center we use is located in the Tokyo@Japan (ap-northeast-1) region.

The above configuration is possible in AWS Toolkit For JetBrains 1.67-231 and works fine the first time.
We can actually see CodeWhisperer in action.

However, the situation is different if you need to reconnect, e.g. because your session is to expire.
Oh dear, when reconnecting from the Toolkit, it always tries to connect to the AWS IAM Identify Centre by specifying us-east-1.

Even if 'ap-northeast-1' is set for 'sso_region' in the ~/.aws/config file, AWS Toolkit will not follow it and only go to 'us-east-1' for connections.
Whenever the IDE opens a browser, it is forced to access 'https://device.sso.us-east-1.amazonaws.com/'.
In this case, it has to follow the 'sso_region' to access 'https://device.sso.ap-northeast-1.amazonaws.com/'.
(Only the first time you set up a connection from the AWS Toolkit, you can access any Region.)

Therefore, we have to delete all previous connection information each time we reconnect, open Add New Connection from scratch again, select (Connect using AWS IAM Identify Center) and reconfigure the 'Start URL' and 'Region'.

We are currently forced to do this task at least once a day.
This is too painful and we would like to know what to do about it.
If this can be resolved by changing the settings, could you please let us know how to do this?

@WhiteRaven777 WhiteRaven777 added the guidance General information and guidance, answers to FAQs, or recommended best practices/resources. label May 11, 2023
@jeroen-hulleman-sqills
Copy link

I have the same issue.

@rli rli added bug We can reproduce the issue and confirmed it is a bug. ready-to-work Fully defined and ready for work and removed guidance General information and guidance, answers to FAQs, or recommended best practices/resources. labels May 11, 2023
@rli rli added pending-release and removed ready-to-work Fully defined and ready for work labels May 18, 2023
@colemvnio
Copy link

Duplicate: #3690

@rli
Copy link
Contributor

rli commented May 31, 2023

Released in 1.68

@rli rli closed this as completed May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

4 participants