I noticed that Tigris defaults to virtual hosts for new buckets, but nothing is mentioned about the migration for existing buckets. I tried to interact with one of our existing buckets using a virtual host, but the request fails, so I’d appreciate any pointers to adopt the new convention.
Thanks in advance.
from Tigris is moving to virtual host style URLs for new buckets
Path name style URLs will still work for buckets created before today, but all new buckets will require a virtual host style URL.
So I guess you keep using the old path name, no migration for existing buckets
Hey, sorry for the confusion. Can you give some more detail about how it fails and how you’ve configured your S3 client? I’m more than happy to help make sure things are working right with this change.