hi guys

has anyone ever experienced an SSL issue using the aws-api please ?

when trying to create an AMI group on AWS, here is my stacktrace

EC2 API @kaffein ?

IAM api @ghadi

Which jdk and platform and can you provide any code snippets?

i'm on jdk 10 with clj 1.10 on mac os x

yes I can provide a snippet, just give me a second so that I can find it please 😉

I forgot to push my code so the only thing I'm not sure of is the syntax for the api call on the last line ... but it kinda looks like this @ghadi

Hmmm I can't reproduce that @kaffein Are you in osx or on a container?

i'm not on a container

that's weird

I should check one more time on my side perhaps

maybe I made a mistake somewhere

any custom thing you're hitting, or a corporate proxy or something? (IAM is global service, so it's probably not something region specific)

no corporate or specific settings I think since I'm using it from home

I may have missed something then : I will check it one more time this evening

thanks a lot for your help @ghadiappreciate it

no problem

@kaffein https://github.com/aws/aws-sdk-java/issues/1778 it looks like others have had a similar issue with Java 10 and macOS, where it seems the Amazon certificates didn't get shipped with the JDK. are you able to try Java 11?

that was my next thought!

I know they restored some certificates from JDK9->JDK10... didn't realize there was a secondary problem!

Thanks a lot @gws and @ghadi I can try to upgrade to java 11 to see if that solves the problem

Will let you guys know

cool brew cask install adoptopenjdk11

@ghadi oh, hello. looks like some new stuff has been added for credential refresh?

was getting an expired token exception, just bumped libs to see if the recent auto-refreshing-credentials stuff fixes my wagon

Yeah we fixed a nasty bug

It wasn't refreshing properly before @devn

@ghadi sweet, thanks!

yep, that did the trick.

I've upgraded my java install to use jdk 11 and it indeed solved the SSL issue!!again thanks a lot @ghadi 👍

thank you for following up @kaffein

really appreciated! (grumble....I wish AWS services used a common trust chain)