Best Practice for multiple AWS Organizations, Cloud Insights, and MID Selection
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2023 09:10 PM
Suppose a customer has multiple AWS Organizations: not accounts rolling up to one billing organization, but multiple billing organizations. This is not going to change in the near future, and it is also growing from acquisitions. So, even if the problem were to be immediately solved, the next acquisition would then begin the problem all over again.
These organizations are isolated affairs. Largely operated as datacenter replacements for IT, they are not widely open to the Internet. Cloud APIs are protected by Service Control Policies in AWS (which is a good security practice). For Discovery, each of these independent service provider clouds has dedicated MID servers using "credential-less" discovery and "Assume Role" capabilities. When we set up a Discovery schedule, we can tie that schedule to a single MID or to a Cluster (or allow it to "auto select," but this fails for obvious reasons).
However, I don't see a similar function available for Cloud Insights. Perhaps I am missing it? Where can I help guide MID selection for billing downloads?