Skip to content

Commit dd8dfbb

Browse files
authored
Replaces duplicate Fleet upgrade instructions with cross-link (#2644)
Fixes #2314 by replacing a duplicate set of instructions with a link to the main source of truth for those instructions.
1 parent fe64369 commit dd8dfbb

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

solutions/security/get-started/spaces-defend-faq.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,7 @@ This page introduces {{elastic-sec}} space awareness and answers frequently aske
1919
::::
2020

2121
::::{note}
22-
{{elastic-sec}}'s space awareness works in conjunction with {{fleet}}'s space awareness. Space awareness is enabled by default in both applications, but for {{stack}} deployments that existed prior to version 9.1, {{fleet}} requires you to manually “opt-in” so that existing data can become space aware:
23-
24-
1. Navigate to **Fleet** using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
25-
2. Go to the **Settings** tab.
26-
3. Scroll to **Advanced settings**.
27-
4. Under **Migrate to space-aware agent policies**, click **Start migration**.
28-
5. Confirm the migration.
22+
{{elastic-sec}}'s space awareness works in conjunction with {{fleet}}'s space awareness. Space awareness is enabled by default in both applications, but for {{stack}} deployments that existed prior to version 9.1, {{fleet}} requires you to manually “opt-in” so that existing data can become space aware. For instructions, refer to [Enable space awareness in {{fleet}}](/deploy-manage/manage-spaces-fleet.md#spaces-fleet-enable).
2923

3024
This is a one-time migration that copies your existing {{fleet}} data into a new, space-aware model. Previous data will be preserved in snapshots in case rollback is needed.
3125
::::

0 commit comments

Comments
 (0)