Skip to content

Commit e54401a

Browse files
committed
Incorporates Oleg's review
1 parent 415a169 commit e54401a

File tree

3 files changed

+17
-5
lines changed

3 files changed

+17
-5
lines changed

solutions/security/cloud/asset-disc-aws.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,10 @@ Two deployment technologies are available: agentless and agent-based.
4242
* To use a pre-existing Cloud Connector for this deployment, select it under **Existing connection**.
4343
* To use a new Cloud Connector: under **New connection**, expand the **Steps to assume role** section. Complete the instructions to generate a `Role ARN` and `External ID`; enter them in Kibana.
4444

45+
::::{important}
46+
in order to use cloud connector for an AWS integration, your {{kib}} instance must be hosted on AWS. In other words, you must have chosen AWS hosting during {{kibana}} setup.
47+
::::
48+
4549
* Option 2: Direct access keys/CloudFormation. For **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.
4650

4751
::::{note}

solutions/security/cloud/get-started-with-cspm-for-aws.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,10 @@ Two deployment technologies are available: agentless and agent-based.
5353
* To use a pre-existing Cloud Connector for this deployment, select it under **Existing connection**.
5454
* To use a new Cloud Connector: under **New connection**, expand the **Steps to assume role** section. Complete the instructions to generate a `Role ARN` and `External ID`; enter them in Kibana.
5555

56+
::::{important}
57+
in order to use cloud connector for an AWS integration, your {{kib}} instance must be hosted on AWS. In other words, you must have chosen AWS hosting during {{kibana}} setup.
58+
::::
59+
5660
* Option 2: Direct access keys/CloudFormation. For **Preferred method**, select **Direct access keys**. Expand the **Steps to Generate AWS Account Credentials** section, then follow the instructions to automatically create the necessary credentials using CloudFormation.
5761

5862
::::{note}

solutions/security/get-started/cloud-connector-deployment.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,19 @@ applies_to:
66
security: preview
77
---
88

9-
# Quickly authenticate agentless integrations using cloud connector
9+
# Quickly authenticate agentless integrations using cloud connectors
1010

11-
Cloud connector authentication for agentless integrations allows you to quickly provide Elastic with access to your third-party cloud service provider accounts. This authentication method reduces administrative burden by eliminating the need to keep track of credentials such as API keys or passwords. Cloud connectors provide a simple, reusable means of authentication, making it easier to manage deployments with many integrations collecting data from multiple cloud security providers.
11+
Cloud connector authentication for agentless integrations allows you to quickly provide Elastic with access to your third-party cloud service provider accounts. Cloud connectors provide a simple, reusable means of authentication, making it easier to manage deployments with many integrations collecting data from multiple cloud security providers. This reduces your administrative burden by eliminating the need to keep track of credentials such as API keys or passwords.
1212

13-
## Where is cloud connector deployment supported?
13+
## Where is cloud connector authentication supported?
1414

1515
At the current stage of this technical preview, a limited selection of cloud providers and integrations are supported.
1616

1717
You can use cloud connector deployment to authenticate with AWS and Azure while deploying either Elastic's Cloud Security Posture Management (CSPM) or Asset Discovery integration. For deployment instructions, refer to:
1818

19-
- Asset Discovery: Asset Discovery on Azure; Asset Discovery on AWS
20-
- CSPM: CSPM on Azure; CSPM on AWS
19+
- Asset Discovery: [Asset Discovery on Azure](/solutions/security/cloud/asset-disc-azure.md); [Asset Discovery on AWS](/solutions/security/cloud/asset-disc-aws.md)
20+
- CSPM: [CSPM on Azure](/solutions/security/cloud/get-started-with-cspm-for-azure.md); [CSPM on AWS](/solutions/security/cloud/get-started-with-cspm-for-aws.md)
21+
22+
::::{important}
23+
in order to use cloud connector for an AWS integration, your {{kib}} instance must be hosted on AWS. In other words, you must have chosen AWS hosting during {{kibana}} setup.
24+
::::

0 commit comments

Comments
 (0)