- Newest
- Most votes
- Most comments
Hello.
Perhaps the following explanation is relevant.
The "ap-southeast-4" region was created after 2019, so unlike the "ap-southeast-2" region, I thought that an error would occur if the region was not specified at the time of the request.
It is unclear how the backup software sends requests to S3, but if you can set the region, it may be a good idea to set the region.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html
Virtual-hosted–style requests for other Regions
The legacy global endpoint is also used for virtual-hosted–style requests in other supported Regions. If you create a bucket in a Region that was launched before March 20, 2019, and use the legacy global endpoint, Amazon S3 updates the DNS record to reroute the request to the correct location, which might take time. In the meantime, the default rule applies, and your virtual-hosted–style request goes to the US East (N. Virginia) Region. Amazon S3 then redirects it with an HTTP 307 Temporary Redirect to the correct Region.For S3 buckets in Regions launched after March 20, 2019, the DNS server doesn't route your request directly to the AWS Region where your bucket resides. It returns an HTTP 400 Bad Request error instead. For more information, see Making requests.
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago