Skip to content

Commit 38515a7

Browse files
mergify[bot]benironsidegithub-actions[bot]
authored
[8.16] [ESS & Serverless] Adds OrganizationUnitIDs description to agentless section of AWS CSPM guide (backport #6155) (#6195)
* [ESS & Serverless] Adds OrganizationUnitIDs description to agentless section of AWS CSPM guide (#6155) * Adds OrganizationalUnitIDs field to the agentless CSPM AWS guide, edits language for the field in agent-based method * Apply suggestions from code review Co-authored-by: Nastasha Solomon <[email protected]> --------- Co-authored-by: Nastasha Solomon <[email protected]> (cherry picked from commit ed8b9bb) # Conflicts: # docs/serverless/cloud-native-security/cspm-get-started.asciidoc * Delete docs/serverless directory and its contents --------- Co-authored-by: Benjamin Ironside Goldstein <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 parent 1da4800 commit 38515a7

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/cloud-native-security/cspm-get-started-aws.asciidoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,9 @@ beta::[]
4343
. Click **Advanced options**, then select **Agentless (BETA)**.
4444
. Next, you'll need to authenticate to AWS. Two methods are available:
4545
.. Option 1: Direct access keys/CloudFormation (Recommended). Under **Preferred method**, select **Direct access keys**. Expand the **Steps to Generate AWS Account Credentials** section, then follow the displayed instructions to automatically create the necessary credentials using CloudFormation.
46+
+
47+
NOTE: If you don't want to monitor every account in your organization, specify which to monitor using the `OrganizationalUnitIDs` field that appears after you click **Launch CloudFormation**.
48+
+
4649
.. Option 2: Temporary keys. To authenticate using temporary keys, refer to the instructions for <<cspm-use-temp-credentials, temporary keys>>.
4750
. Once you've selected an authentication method and provided all necessary credentials, click **Save and continue** to finish deployment. Your data should start to appear within a few minutes.
4851

@@ -76,7 +79,7 @@ For most use cases, the simplest option is to use AWS CloudFormation to automati
7679
. Return to your {kib} tab. Click *Save and continue* at the bottom of the page.
7780
. Review the information, then click *Launch CloudFormation*.
7881
. A CloudFormation template appears in a new browser tab.
79-
. For organization-level deployments only, you must enter the ID of the organizational unit where you want to deploy into the `OrganizationalUnitIds` field in the CloudFormation template. You can find it in the AWS console under *AWS Organizations -> AWS Accounts* (it appears under the organization name).
82+
. For organization-level deployments only, you must enter the ID of the organizational units where you want to deploy into the CloudFormation template's `OrganizationalUnitIds` field. You can find organizational unit IDs in the AWS console under *AWS Organizations -> AWS Accounts* (under each organization's name). You can also use this field to specify which accounts in your organization to monitor, and which to skip.
8083
. (Optional) Switch to the AWS region where you want to deploy using the controls in the upper right corner.
8184
. Tick the checkbox under *Capabilities* to authorize the creation of necessary resources.
8285
+

0 commit comments

Comments
 (0)