The cost of running 9 separate registries in AWS is not sustainable. The original purpose of this architecture was to enable nodes to have "ownership" of their metadata, and to provide the easiest means for them to access and update their metadata freely, without having to worry about specific auth needs to ensure they were only touching their data.
We should now re-think this architecture and how we could significantly cut cost down by have 1-2 registries, and provide some sort of access/auth layer that ensures nodes are able to ingest and query data from "their" registry, but really it is just narrowing their access to the data their node registered.
💡 Description
The cost of running 9 separate registries in AWS is not sustainable. The original purpose of this architecture was to enable nodes to have "ownership" of their metadata, and to provide the easiest means for them to access and update their metadata freely, without having to worry about specific auth needs to ensure they were only touching their data.
We should now re-think this architecture and how we could significantly cut cost down by have 1-2 registries, and provide some sort of access/auth layer that ensures nodes are able to ingest and query data from "their" registry, but really it is just narrowing their access to the data their node registered.