---
title: "Amazon S3 Bucket Changes"
slug: "amazon-s3-bucket-changes"
updated: 2023-11-14T17:11:38Z
published: 2023-11-14T17:11:39Z
canonical: "docs.retrospect.com/amazon-s3-bucket-changes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.retrospect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon S3 Bucket Changes

## Summary

Retrospect 17.5 and later is fully compatible with Amazon S3, both with path-style and virtual-host style DNS naming. See the examples below. Note the bucket name is part of the path in the path-style and part of the domain in the virtual-host style.

Retrospect 17.0 and earlier are compatible with Amazon S3’s deprecated path-style DNS naming. Buckets created before September 30, 2020 will continue to work with these versions of Retrospect.

## Background

In May 2019, Amazon announced their [deprecation plans](https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/) for Amazon AWS S3 Path-Style Bucket URLs. As of September 30, 2020, new S3 buckets will not support the deprecated path-style bucket URL naming. See below for examples:

## Troubleshooting

If you see error "Host not found or network unavailable", the issue could be that you are using a Retrospect version below 17.5 with a path-style domain. See screenshot.

![](https://cdn.us.document360.io/6d1fe0c6-ccdb-4ee9-a621-0504cb91b4be/Images/Documentation/amazon-s3-bucket-changes-image-0rwmcf0w.png)

Please upgrade to Retrospect 17.5 to use virtual-host domains.

Last Update: September 22, 2020