> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/integrations/sources/aws-s3-rehydration/aws-s3-rehydration-deprecated.md).

# AWS S3 Rehydration (Deprecated)

{% hint style="info" %}
**NOTE**

This source has been deprecated and replaced with a new [AWS S3 Rehydration](/integrations/sources/aws-s3-rehydration.md) source. While it will continue to function, it will no longer receive any enhancements and you should migrate to the new source.
{% endhint %}

### Object Format

Rehydrated data must be in [OTLP format JSON](https://github.com/open-telemetry/opentelemetry-proto) for correct processing. Ensure your data adheres to this format.

The [AWS S3 Destination](/integrations/destinations/aws-s3.md) supports `gzip` compression. This receiver will gracefully detect and handle if any data is gzipped or uncompressed.

### Supported Platforms

| Platform | Supported |
| -------- | --------- |
| Linux    | ✓         |
| Windows  | ✓         |
| macOS    | ✓         |

### Configuration Fields

<table><thead><tr><th width="168.96484375">Field</th><th>Description</th></tr></thead><tbody><tr><td>Region</td><td>The AWS recognized region string</td></tr><tr><td>Bucket</td><td>Name of the S3 Bucket to rehydration telemetry from.</td></tr><tr><td>Folder Prefix</td><td>Root directory of the bucket to rehydration telemetry from.</td></tr><tr><td>Poll Interval</td><td>The interval for checking new objects, e.g., '1m' for one minute.</td></tr><tr><td>Starting Time</td><td>UTC start time for rehydration in the format <code>YYYY-MM-DDTHH:MM</code>.</td></tr><tr><td>Ending Time</td><td>UTC end time for rehydration in the format <code>YYYY-MM-DDTHH:MM</code>.</td></tr><tr><td>Delete on Read</td><td>If true, objects are deleted after rehydration.</td></tr><tr><td>Enable Storage</td><td>Enable to specify a storage extension for tracking rehydration progress.</td></tr><tr><td>Storage Directory</td><td>Directory for storing rehydration state, useful for maintaining state and resuming operations. (Only relevant if <code>Enable Storage</code> is true)</td></tr></tbody></table>

### Example Configuration

#### Basic Configuration

This configuration sets up AWS S3 Rehydration with necessary details such as Region, Bucket, and time range for rehydration.

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2Fgit-blob-90f0dde4dc3cef8bd238246827c52997f2a1c3e4%2Fintegrations-sources-aws-s3-rehydration-readme-image-1.png?alt=media" alt="Bindplane docs - AWS S3 Rehydration (Deprecated) - image 1"><figcaption></figcaption></figure>

Adjust the Region, Bucket, Starting Time, and Ending Time to match your configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/integrations/sources/aws-s3-rehydration/aws-s3-rehydration-deprecated.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.