[Info] on 22th  of July 8:00-9:00 CEST - Timestamp behavior alignment for Exos ListObjects requests 

Dear Customers,

We would like to inform you about an upcoming improvement to Exos - EOData access layer via S3 API.

As part of our ongoing efforts to improve compatibility with the AWS S3 standard, Exos will align the LastModified timestamps returned by ListObjects requests with the AWS S3 behavior.

The change will be deployed on 22 July 2026, between 8:00 - 9:00 CEST.

As a result, LastModified timestamps will be rounded to whole-second precision. During the rollout of this change, you may temporarily observe some timestamps appearing earlier than previously reported.

Timestamp example before the change:
<Key>Sentinel-2/MSI/L1C/2026/07/01/S2C_MSIL1C_20260701T230901_N0512_R101_T59LLJ_20260702T003337.SAFE/INSPIRE.xml</Key><LastModified>2026-07-02T01:33:02.450Z</LastModified>

Timestamp example after the change:
<Key>Sentinel-2/MSI/L1C/2026/07/01/S2C_MSIL1C_20260701T230901_N0512_R101_T59LLJ_20260702T003337.SAFE/INSPIRE.xml</Key><LastModified>2026-07-02T01:33:02.000Z</LastModified>

This change is not expected to affect the majority of users. However, if your applications or workflows rely on the exact LastModified timestamp values returned by ListObjects requests, we recommend monitoring them after the update and verifying that they continue to operate as expected.

No action is required for customers who do not rely on these timestamp values.

If you have any questions or concerns, please feel free to contact our support team.

Kind regards,
CREODIAS Support Team