As an implementor, I would like to see new AWS S3 Browser tested.

[thareUSGS]

🧑‍🔬 User Persona(s)

Node Operator, Data Engineer

💪 Motivation

More of an FYI rather than an issue. Thus, close as you see fit.

Of course -- Amazon just introduced an S3 Browser (Dec. 2024) at the Re:Invent conference. Roadmap is promising with future support for thumbnails and other items:
https://aws.amazon.com/about-aws/whats-new/2024/12/storage-browser-amazon-s3/
blog: https://aws.amazon.com/blogs/aws/connect-users-to-data-through-your-apps-with-storage-browser-for-amazon-s3/

📖 Additional Details

more Re:Invent related notes:

1. As we add with rclone, there could be a new built-in method to tag all S3 data with checksums (promising better data integrity):
   https://aws.amazon.com/blogs/aws/introducing-default-data-integrity-protections-for-new-objects-in-amazon-s3/

2. For S3 there is also a new metadata type (and table type). Could make scraping file information much easier:
   https://aws.amazon.com/about-aws/whats-new/2024/12/amazon-s3-metadata-preview/

Acceptance Criteria

No response

⚙️ Engineering Details

No response

🎉 I&T

No response

[jordanpadams]

@thareUSGS very interesting. We will definitely poke at this some more.

@viviant100 @tloubrieu-jpl @eddiesarevalo @sjoshi-jpl @collinss-jpl FYI. each of the things mentioned above could impact (positively) S3 browser and DUM.

[jordanpadams]

Note: looks like an auth layer may be required for the browser: https://ui.docs.amplify.aws/react/connected-components/storage/storage-browser#setup-and-authentication