explain target_region field in configuration (#161)

tilfinltd · Sep 22, 2020 · c753e5f · c753e5f
1 parent 4bbb657
commit c753e5f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -62,6 +62,7 @@ More complex configurations involve multiple AWS accounts and/or organizations.
 - As above, **target roles** can be expressed with a `role_arn` or with both `aws_account_id` and `role_name` and can optionally pass the optional parameters.
 
 - If `target_role_name` is set in **base account**, the value is provided as the default role name for each **target roles**.
+- If `target_region` is set in **base account**, the value is provided as the default region for each **target roles**.
 
 ```
 [organization1]

diff --git a/options.html b/options.html
@@ -161,6 +161,7 @@ <h3>Complex Configuration</h3>
    <li>A <b>target role</b> is associated with a <b>base account</b> by the <b>target role</b> specifying a <code>source_profile</code>.</li>
    <li>As above, <b>target roles</b> can be expressed with a <code>role_arn</code> or with both <code>aws_account_id</code> and <code>role_name</code> and can pass the optional parameters.</li>
    <li>If <code>target_role_name</code> is set in <b>base account</b>, the value is provided as the default role name for each <b>target roles</b>.</li>
+   <li>If <code>target_region</code> is set in <b>base account</b>, the value is provided as the default region for each <b>target roles</b>.</li>
   </ul>
   <pre>
 [organization1]