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

AWS S3 Buckets with "s3-" prefix not showing up in IntelliJ AWS Explorer #2342

Closed
adammeyerspro opened this issue Jan 13, 2021 · 3 comments
Closed
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@adammeyerspro
Copy link

Describe the bug
I am able to connect to my AWS S3 bucket fine in IntelliJ, but when selecting a region, I see all the buckets EXCEPT any of them with a "s3-" prefix. Logging directly into s3.console.aws.amazon.com I can see the buckets I want, but they don't show in the IJ AWS Explorer.

To reproduce

  1. View buckets in s3.console.aws.amazon.com
  2. See all buckets
  3. Open S3 in AWS Explorer in IntelliJ
  4. SEE MISSING buckets with 's3-' prefix

Expected behavior
s3.console.aws.amazon.com and AWS Explorer in IJ should match

Screenshots
image

Your Environment

  • OS: Win10
  • JetBrains product: IntelliJ
  • JetBrains product version: 2020.3
  • AWS Toolkit version: 1.22 (2020-12-01)
  • SAM CLI version:
  • JVM/Python version:

Additional context
Is this a bug? Or is there a setting I need to set somewhere?

@adammeyerspro adammeyerspro added the bug We can reproduce the issue and confirmed it is a bug. label Jan 13, 2021
@abrooksv
Copy link
Contributor

abrooksv commented Jan 13, 2021

I was able to reproduce it, we are failing to grab the region for those buckets so they are being hidden:

Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <s3-<username>-foo.s3-<username.-foo.s3.us-west-2.amazonaws.com> doesn't match any of the subject alternative names: [s3-us-west-2.amazonaws.com, *.s3-us-west-2.amazonaws.com, s3.us-west-2.amazonaws.com, *.s3.us-west-2.amazonaws.com, s3.dualstack.us-west-2.amazonaws.com, *.s3.dualstack.us-west-2.amazonaws.com, *.s3.amazonaws.com, *.s3-control.us-west-2.amazonaws.com, s3-control.us-west-2.amazonaws.com, *.s3-control.dualstack.us-west-2.amazonaws.com, s3-control.dualstack.us-west-2.amazonaws.com, *.s3-accesspoint.us-west-2.amazonaws.com, *.s3-accesspoint.dualstack.us-west-2.amazonaws.com, *.s3.us-west-2.vpce.amazonaws.com]

Need to figure out why the hostname is messed up for the bucket

s3-<username>-foo.s3-<username.-foo.s3.us-west-2.amazonaws.com
vs
s3-<username.-foo.s3.us-west-2.amazonaws.com

@abrooksv
Copy link
Contributor

abrooksv commented Jan 14, 2021

This is actually fixed in master. I found it by accident when running some tests and forgot about it: bebee70

If you are blocked by this, our EAP builds have the fix. Here is a link to our latest 2020.3 EAP: https://plugins.jetbrains.com/plugin/11349-aws-toolkit/versions/eap/107488

@adammeyerspro
Copy link
Author

Great, thanks!

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

2 participants