Skip to content

Commit

Permalink
Update: Merge pull request #42 from reflexivesecurity/add_multiaccoun…
Browse files Browse the repository at this point in the history
…t_docs

Multi Account Documentation
  • Loading branch information
rjulian committed Dec 14, 2020
2 parents 12893da + b4d46a0 commit 53a9ce3
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions about.rst
Original file line number Diff line number Diff line change
Expand Up @@ -68,3 +68,20 @@ This infrastructure is created similarly to the output of `reflex build` in that
forwarding_regions:
- us-east-2
- eu-west-1
Multi-account Support
----------------------------

In a default implementation of reflex, a single account is monitored for events. If your organization leverages many accounts and wishes to monitor them all through a single reflex deploy, we allow for the configuration of a multi-account forwarder to a central account. In this setup, there is an account deployed with normal reflex infrastructure, called a "parent" account and then many "child" accounts that forward their rule findings to the central account for processing. In the "child" accounts, you will find just event rules, SNS topics, and IAM roles for cross account describe/remediation.

Similarly to the multi-region build output, we can create multi-account output with a configuration block update like below. This will create separate output directories needed to be deployed separately with terraform in each account. *Note*: If specifying child accounts, it is required to specify parent accounts in the configuration below. Specifying neither child or parent accounts will create a single account build.

.. code-block:: yaml
providers:
- aws:
region: us-east-1
parent_account: "123456789012"
child_accounts:
- "234567890123"
- "345678901234"

0 comments on commit 53a9ce3

Please sign in to comment.