Set the S3 bucket to the same region as AmazonS3Client, otherwise it just throws this exception. Check if your bucket name is correct as well.
Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.
You have a different solution? A short tip here would help you and many other users who saw this issue last week.