Best way of avoiding public i18n JSONs

Hi. We’re considering using i18n JSONs (https://<our-project> and would like to know what would be the recommended way of avoiding them being 100% publicly accessible. We intend to host the JSONs in an AWS S3 bucket. Would restricting access to this bucket to certain DatoCMS source IP addresses be a good way? If so, could we get a list of possible addresses?

Hello @rodrigo.weigert

The JSON is fetched by the users of the CMS, so if you only want to share that with people inside a network that you control I guess you can do that.

I see, thanks!