7 pointsby 0hardik16 hours ago2 comments
  • thedougd2 hours ago
    If you use AWS Config with an organization wide aggregator, which Control Tower sets up by default these days, have your agent use it to find resources and related resources. You can build most of the graph from that alone without traversing accounts.
  • chaos_emergent3 hours ago
    What’s the value of having a ton of silo’d accounts, especially for the use case demonstrated by the readme where there are multiple staging and production accounts?
    • thedougd2 hours ago
      Blast radius. One example… What happens when you give an identity s3:* on resource: *? It can read/modify every bucket in the account that doesn’t have a resource policy with an explicit deny.
    • casper143 hours ago
      This is not super uncommon, especially when selling to enterprises who demand complete data isolation.
    • 0hardik13 hours ago
      [dead]