-
Notifications
You must be signed in to change notification settings - Fork 436
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
src/java/ice.properties has an s3- before prepend to FQDN #277
Comments
@Virtui leave empty |
I'd imagine a conditional could be added that if set to us-east-1, it works correctly. Anyways, thanks for the info @ltagliamonte. I actually figured it out on my own and then found the issue here later. Took about 2 hours to debug. |
s3-us-east-1.amazonaws.com is not a valid endpoint https://docs.aws.amazon.com/general/latest/gr/rande.html?shortFooter=true#s3_region |
Hi Jeff,
Thanks for the suggestion. You’re right that a condition could be added to
make this problem go away.
Are you familiar with Groovy/Java and how to make Pull Requests? If you’re
not, it’s not an issue. Just let us know and we’ll do it.
Nicolas
Le mer. 17 janv. 2018 à 22:05, Jeff Uberstine <[email protected]> a
écrit :
I'd imagine a conditional could be added that if set to us-east-1, it
works correctly. Anyways, thanks for the info @ltagliamonte
<https://github.com/ltagliamonte>. I actually figured it out on my own
and then found the issue here later. Took about 2 hours to debug.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#277 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACUpYlONTA44TxcEx8VL_tQlrWTJdkRks5tLmCwgaJpZM4Qi0kK>
.
--
--
Nicolas Fonrose | Teevity | Founder
+33.6.61.35.43.31
https://teevity.com - Cloud Costs Analytics built on NetflixOSS
twitter - @nfonrose / @Teevity
|
Causes host resolution fail when determining bucket location. Currently causes UnknownHostException: bucketname.s3-us-east-1.amazonaws.com instead of bucketname.s3.us-east-1.amazonaws.com
The text was updated successfully, but these errors were encountered: