Closed priyanknarvekar closed 6 months ago
@priyanknarvekar Could you clarify if the Cross Region Endpoints table is incorrect or should not be in that topic?
@pdwatters this statement , Buckets that are created at a cross region endpoint distribute data across three regions. Any one of these regions can suffer an outage or even destruction without impacting availability. ...
when seen in context of the table users would/are interpreting, cross region bucket would spread data across US, EU and AP. and hence creates confusion, with users asking if their data would cross the geographical boundary. see the screenshot below.
this interpretation is not correct. Also the column header for the first column "Region" is incorrect, which also add to this confusion. that should be "Geo"
A data in US cross region bucket is distributed only across regions in US, i.e Dallas, WDC and SJC. A data in EU cross region bucket is distributed only across regions in EU, i.e Amsterdam, FRA and Milan. Finally data in AP cross region bucket is distributed only across regions in AP, i.e TOK, SYD and OSA.
so either the description needs to be improved, or some other hint needs to be added.
@priyanknarvekar Please review my updates: https://test.cloud.ibm.com/docs-draft/cloud-object-storage?topic=cloud-object-storage-endpoints#endpoints-geo
@pdwatters looks good !
The description of the cross region endpoints appears to be misleading(and incorrect), specially in context of the table below it. Users have misinterpreted that , cross region buckets are replicated across "three regions" us, eu and ap. to the best of my understanding cross region buckets are still within the same geo , but across multiple mzr(s) and single site
it would be good to update to reflect, Buckets that are created at a cross region endpoint distribute data across the mzr's within the geo
https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints#endpoints-geo