Maybe not a bottleneck, but for large data sets would it reduce the data transfer costs as the inter-s3 bucket transfer would use AWS’ internal links rather than route over external interfaces.
-Bruce > Has this been tested already ? Generally, wdyt ? No. I suggest to first test cross geo mongo deployment with single S3 bucket. There shouldn't be functional issue in using single S3 bucket. Few customers use single shared S3 bucket between non-clustered cross-geo jackrabbit2 repositories in production. Sure, adding more complexity only make sense if we can demonstrate this is a bottleneck. Regards, Timothee
