3 ms·

The old REST-style S3 URLs are specifically excluded from being able to redirect: https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html htt

The old REST-style S3 URLs are specifically excluded from being able to redirect: https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-... You can create a new bucket or switch your existing one to "Static Website Hosting" mode to enable the ability to 301 your content going forward. But the URL for the "website" version isn't the same as the REST URL. And again, there's no way to redirect from the old naming scheme to the new one. If you have content that you've ever linked with one of those URLs, it's stuck there forever.

codetrotter 7y ago
> And again, there's no way to redirect from the old naming scheme to the new one. For customers, no. For Amazon itself, yes. And I think that is what parent commenter meant. That Amazon should 301 all requests that are using old paths.
- deleted 7y ago
  [deleted]
- xchaotic 7y ago
  It's not that simple, unfortunately - it won't work for the old dotted addresses and S3 is not HTTP
inopinatus 7y ago
This isn't a restriction if you're AWS and looking to give more customers a soft landing over an extended deprecation timeframe. The certificate concern some are raising is also a furphy.