S3Fetcher

The S3 Fetcher log source now accepts access key IDs in formats beyond the standard AWS prefixes (AKIA, ASIA), enabling configuration for non-AWS S3-compatible storage solutions such as Open Telekom Cloud.

The log source configuration adds a new field, Fetch from Storage Classes, which lets you select S3 storage classes to collect logs from and exclude all others, including archived classes GLACIER and DEEP_ARCHIVE. This reduces resource use and prevents repeated failures on inaccessible objects.

The log source configuration adds a new toggle, Fetch From Last Object Key, which resumes listing objects from the last retrieved object key to avoid fetching redundant object metadata and speed up listing on large buckets.

S3 Log Fetcher now processes downloads in batches, keeping memory usage stable as the number of objects in your bucket grows. This improves performance and prevents memory spikes when fetching large volumes of logs.

S3 Fetcher now supports additional cloud regions , enabling users to collect logs from newly available geographic locations.

You can now reset the last fetch date, allowing you to update the initial date for fetching logs.

You can now configure S3 Fetcher from Log Sources , which provides a centralized user interface for all the configurations of log collection. Compatibility is available with Director v2.6.0, currently available as Priority Access. Contact Support for its access.