MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Will Not Implement
Categories Atlas
Created by Guest
Created on Aug 10, 2021

RELATED FEEDBACK

Standardize case for region values

Depending on the resource, the case for the region value changes from uppercase with underscores (US_ EAST _1) to lowercase with dashes (us-east-1). This presents an unnecessary challenge when working with the provider. It would be much cleaner, easier to work with, and prone to fewer errors if all resources accepted us-east-1.
  • Attach files
  • Guest
    Jun 16, 2023
    hi Andrew there a lot of benefits to keeping cases standardized as we have. For example, each of the 3 main cloud vendors use different formats and this approach is easier / more intuitive for MongoDB Atlas multi-cloud users. can you please share more details on use cases or is this mapping of atlas regions to cloud regions names just for convivence? thank you.
    Reply
  • Guest
    Jun 1, 2022
    Hey Melissa, I agree with your comment. However, some API can be introduced to correlate the atlas region code and the cloud provider region code.
    Reply
  • Guest
    Aug 10, 2021
    Thank you Andrew. This is actually not a case situation per se but the provider expressing the reality of the platform's structure. These are distinctive types of regions - one being the region name in AWS, for example us-east-1, and the other the region within Atlas, e.g. US_EAST_1. See https://docs.atlas.mongodb.com/reference/amazon-aws/#std-label-amazon-aws. GCP and Azure have a similar situations: https://docs.atlas.mongodb.com/reference/google-gcp/ and https://docs.atlas.mongodb.com/reference/microsoft-azure/
    Reply