1 result found
Thank you all for your feedback!
We hear you loud and clear and are working on exposing these details in the next quarter.
An error occurred while saving the commentMichael commented
This feature would be great because we have design patterns where one instance imports lots of data into Atlas and our VPC is peered with the Atlas VPC.
So by knowing the actual zoneId of the primary it would be possible to spawn an instance in the same az. By doing this, it would be possible to save a lot of money because there are no data transfer costs between vpc peerings communicating in the same az: https://aws.amazon.com/de/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/
Also it would be possible perhaps to configure instances to read against the atlas nodes in the same az first.Michael supported this idea ·