Skip to content

Commit 2bd86cb

Browse files
benironsidebenironside
authored
Uses a snippet for the Agentless Integrations FAQ to resolve broken link (#1338)
Fixes a broken link to https://www.elastic.co/docs/troubleshoot/security/agentless-integrations.html by re-adding a page at that URL. Uses a snippet so the page can also exist in its [proper location](https://www.elastic.co/docs/solutions/security/get-started/agentless-integrations-faq). This is a temporary solution to make sure links from Google and other search engines work while the full redirect capabilities in V3 are pending. Previews: [/troubleshoot/agentless-integrations.html](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1338/troubleshoot/security/agentless-integrations) [/solutions/security/get-started/agentless-integrations-faq.html](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1338/solutions/security/get-started/agentless-integrations-faq)
1 parent 1a5aadf commit 2bd86cb

File tree

5 files changed

+65
-50
lines changed

5 files changed

+65
-50
lines changed

‎solutions/security/get-started/_snippets/agentless-integrations-faq.md‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
Frequently asked questions and troubleshooting steps for {{elastic-sec}}'s agentless CSPM integration.
2+
3+
4+
## When I make a new integration, when will I see the agent appear on the Integration Policies page? [_when_i_make_a_new_integration_when_will_i_see_the_agent_appear_on_the_integration_policies_page]
5+
6+
After you create a new agentless integration, the new integration policy may show a button that says **Add agent** instead of the associated agent for several minutes during agent enrollment. No action is needed other than refreshing the page once enrollment is complete.
7+
8+
9+
## How do I troubleshoot an `Offline` agent? [_how_do_i_troubleshoot_an_offline_agent]
10+
11+
For agentless integrations to successfully connect to {{elastic-sec}}, the {{fleet}} server host value must be the default. Otherwise, the agent status on the {{fleet}} page will be `Offline`, and logs will include the error `[elastic_agent][error] Cannot checkin in with fleet-server, retrying`.
12+
13+
To troubleshoot this issue:
14+
15+
1. Find **{{fleet}}** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab.
16+
2. Under **{{fleet}} server hosts**, click the **Actions** button for the policy named `Default`. This opens the Edit {{fleet}} Server flyout. The policy named `Default` should have the **Make this {{fleet}} server the default one** setting enabled. If not, enable it, then delete your integration and create it again.
17+
18+
::::{note}
19+
If the **Make this {{fleet}} server the default one** setting was already enabled but problems persist, it’s possible someone changed the default {{fleet}} server’s **URL** value. In this case, contact Elastic Support to find out what the original **URL** value was, update the settings to match this value, then delete your integration and create it again.
20+
::::
21+
22+
23+
24+
## How do I troubleshoot an `Unhealthy` agent? [_how_do_i_troubleshoot_an_unhealthy_agent]
25+
26+
On the **{{fleet}}** page, the agent associated with an agentless integration has a name that begins with `agentless`. To troubleshoot an `Unhealthy` agent:
27+
28+
* Confirm that you entered the correct credentials for the cloud provider you’re monitoring. The following is an example of an error log resulting from using incorrect AWS credentials:
29+
30+
```
31+
[elastic_agent.cloudbeat][error] Failed to update registry: failed to get AWS accounts: operation error Organizations: ListAccounts, get identity: get credentials: failed to refresh cached credentials, operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: XXX, api error AccessDenied: User: XXX is not authorized to perform: sts:AssumeRole on resource:XXX
32+
```
33+
34+
35+
For instructions on checking {{fleet}} logs, refer to [{{fleet}} troubleshooting](/troubleshoot/ingest/fleet/common-problems.md).
36+
37+
38+
## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]
39+
40+
::::{note}
41+
Deleting your integration will remove all associated resources and stop data ingestion.
42+
::::
43+
44+
45+
When you create a new agentless CSPM integration, a new agent policy appears within the **Agent policies** tab on the **{{fleet}}** page, but you can’t use the **Delete integration** button on this page. Instead, you must delete the integration from the CSPM Integration’s **Integration policies** tab.
46+
47+
1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then search for and select `CSPM`.
48+
2. Go to the CSPM Integration’s **Integration policies** tab.
49+
3. Find the integration policy for the integration you want to delete. Click **Actions**, then **Delete integration**.
50+
4. Confirm by clicking **Delete integration** again.

‎solutions/security/get-started/agentless-integrations-faq.md‎

Lines changed: 2 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -10,53 +10,5 @@ applies_to:
1010

1111
# Agentless integrations FAQ [agentless-integration-troubleshooting]
1212

13-
Frequently asked questions and troubleshooting steps for {{elastic-sec}}'s agentless CSPM integration.
14-
15-
16-
## When I make a new integration, when will I see the agent appear on the Integration Policies page? [_when_i_make_a_new_integration_when_will_i_see_the_agent_appear_on_the_integration_policies_page]
17-
18-
After you create a new agentless integration, the new integration policy may show a button that says **Add agent** instead of the associated agent for several minutes during agent enrollment. No action is needed other than refreshing the page once enrollment is complete.
19-
20-
21-
## How do I troubleshoot an `Offline` agent? [_how_do_i_troubleshoot_an_offline_agent]
22-
23-
For agentless integrations to successfully connect to {{elastic-sec}}, the {{fleet}} server host value must be the default. Otherwise, the agent status on the {{fleet}} page will be `Offline`, and logs will include the error `[elastic_agent][error] Cannot checkin in with fleet-server, retrying`.
24-
25-
To troubleshoot this issue:
26-
27-
1. Find **{{fleet}}** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab.
28-
2. Under **{{fleet}} server hosts**, click the **Actions** button for the policy named `Default`. This opens the Edit {{fleet}} Server flyout. The policy named `Default` should have the **Make this {{fleet}} server the default one** setting enabled. If not, enable it, then delete your integration and create it again.
29-
30-
::::{note}
31-
If the **Make this {{fleet}} server the default one** setting was already enabled but problems persist, it’s possible someone changed the default {{fleet}} server’s **URL** value. In this case, contact Elastic Support to find out what the original **URL** value was, update the settings to match this value, then delete your integration and create it again.
32-
::::
33-
34-
35-
36-
## How do I troubleshoot an `Unhealthy` agent? [_how_do_i_troubleshoot_an_unhealthy_agent]
37-
38-
On the **{{fleet}}** page, the agent associated with an agentless integration has a name that begins with `agentless`. To troubleshoot an `Unhealthy` agent:
39-
40-
* Confirm that you entered the correct credentials for the cloud provider you’re monitoring. The following is an example of an error log resulting from using incorrect AWS credentials:
41-
42-
```
43-
[elastic_agent.cloudbeat][error] Failed to update registry: failed to get AWS accounts: operation error Organizations: ListAccounts, get identity: get credentials: failed to refresh cached credentials, operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: XXX, api error AccessDenied: User: XXX is not authorized to perform: sts:AssumeRole on resource:XXX
44-
```
45-
46-
47-
For instructions on checking {{fleet}} logs, refer to [{{fleet}} troubleshooting](/troubleshoot/ingest/fleet/common-problems.md).
48-
49-
50-
## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]
51-
52-
::::{note}
53-
Deleting your integration will remove all associated resources and stop data ingestion.
54-
::::
55-
56-
57-
When you create a new agentless CSPM integration, a new agent policy appears within the **Agent policies** tab on the **{{fleet}}** page, but you can’t use the **Delete integration** button on this page. Instead, you must delete the integration from the CSPM Integration’s **Integration policies** tab.
58-
59-
1. Find **Integrations** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then search for and select `CSPM`.
60-
2. Go to the CSPM Integration’s **Integration policies** tab.
61-
3. Find the integration policy for the integration you want to delete. Click **Actions**, then **Delete integration**.
62-
4. Confirm by clicking **Delete integration** again.
13+
:::{include} _snippets/agentless-integrations-faq.md
14+
:::

‎troubleshoot/security.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,4 @@ This section covers common {{elastic-sec}} related issues and how to resolve the
1616
* [Troubleshoot detection rules](security/detection-rules.md)
1717
* [Troubleshoot {{elastic-defend}}](security/elastic-defend.md)
1818
* [Troubleshoot indicators of compromise](security/indicators-of-compromise.md)
19+
* [Agentless integrations FAQ](security/agentless-integrations.md)

‎troubleshoot/security/agentless-integrations.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
applies_to:
3+
stack: all
4+
serverless:
5+
security: all
6+
---
7+
8+
# Agentless integrations FAQ [agentless-integration-troubleshoot]
9+
10+
:::{include} /solutions/security/get-started/_snippets/agentless-integrations-faq.md
11+
:::

‎troubleshoot/toc.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,7 @@ toc:
137137
- file: security/detection-rules.md
138138
- file: security/elastic-defend.md
139139
- file: security/indicators-of-compromise.md
140+
- file: security/agentless-integrations.md
140141
- file: ingest.md
141142
children:
142143
# - file: ingest/enterprise-search/crawls.md

0 commit comments

Comments
 (0)