1 Answer
- Newest
- Most votes
- Most comments
0
D'oh. This definitely falls into the category of user error. I'd completely forgot that the constant VPC_S3_ENDPOINT was one of my own creation, part of my original project from several months ago. It was set to
com.amazonaws.us-east-1.s3
and that of course is why I was getting the region error.
I'll change my constant definition to
VPC_S3_ENDPOINT = "com.amazonaws.{}.s3"
and inject the region into this constant before making the api call.
Edited by: pwsteele on Jan 4, 2019 1:13 PM
answered 5 years ago
Relevant content
- Accepted Answerasked a year ago
- asked 7 months ago
- asked 9 days ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago