As part of our ongoing efforts to improve consistency, clarity, and long-term maintainability of the EOData repository, we are preparing changes to the naming of S3 buckets currently used.
What is changing?
We have identified that the possibility to use multiple bucket names, such as:
- EODATA
- EOCLOUD
- eocloud
- DIAS
- dias
aside from the main eodata bucket, may lead to confusion as for their purpose and content.
To avoid confusion and to align with AWS S3 best practices — which require bucket names to be lowercase — we will be consolidating all EOData access into a single unified bucket:
→ eodata (lowercase)
All other bucket name variants listed above will be deprecated and removed.
Why are we doing this?
- To introduce order and consistency within the S3 Endpoint environment
- To eliminate duplicate or confusing bucket references
- To follow AWS naming conventions
- To simplify integration, documentation, and user workflows across projects
As part of our ongoing efforts to improve consistency, clarity, and long-term maintainability of the EOData repository, we are preparing changes to the naming of S3 buckets currently used.
What is changing?
We have identified that the possibility to use multiple bucket names, such as:
aside from the main eodata bucket, may lead to confusion as for their purpose and content.
To avoid confusion and to align with AWS S3 best practices — which require bucket names to be lowercase — we will be consolidating all EOData access into a single unified bucket:
→ eodata (lowercase)
All other bucket name variants listed above will be deprecated and removed.
Why are we doing this?