(DOCS-10466) Move Remote Config

config/_default/menus/main.en.yaml

@@ -484,11 +484,6 @@ menu:
       url: agent/configuration/secrets-management/
       parent: agent_configuration
       weight: 609
-    - name: Remote Configuration
-      identifier: agent_remote_configuration
-      url: agent/remote_config
-      parent: agent
-      weight: 7
     - name: Fleet Automation
       identifier: agent_fleet_automation
       url: agent/fleet_automation
@@ -498,7 +493,7 @@ menu:
       identifier: remote_agent_management
       url: agent/fleet_automation/remote_management
       parent: agent_fleet_automation
-      weight: 801
+      weight: 802
     - name: Troubleshooting
       url: agent/troubleshooting/
       parent: agent
@@ -1155,6 +1150,12 @@ menu:
       identifier: coterm_rules
       parent: coterm
       weight: 3
+    - name: Remote Configuration
+      pre: config-2
+      url: remote_configuration
+      identifier: remote_configuration
+      parent: essentials_heading
+      weight: 130000
     - name: Cloudcraft (Standalone)
       url: cloudcraft/
       pre: cloudcraft

content/en/account_management/org_settings.md

@@ -169,7 +169,7 @@ The session duration can be configured within the following limits:
 [7]: /account_management/saml/mapping
 [8]: /account_management/api-app-keys/
 [9]: /account_management/rbac/
-[10]: /agent/remote_config/?tab=configurationyamlfile#how-it-works
+[10]: /remote_configuration#how-it-works
 [11]: /account_management/api-app-keys/#client-tokens
 [12]: /service_management/events/guides/email/
 [13]: /synthetics/settings/?tab=specifyvalue#overview

content/en/actions/private_actions/_index.md

@@ -24,7 +24,7 @@ further_reading:
 
 Private actions allow your Datadog workflows and apps to interact with services hosted on your private network without exposing them to the public internet. To use private actions, you must install a private action runner on a host in your network using Docker or [Kubernetes][1] and pair the runner with a [connection][2].
 
-<div class="alert alert-warning">To install a private action runner, your organization must have <a href="/agent/remote_config/?tab=configurationyamlfile#enabling-remote-configuration">Remote Configuration</a> enabled.</div>
+<div class="alert alert-warning">To install a private action runner, your organization must have <a href="/remote_configuration">Remote Configuration</a> enabled.</div>
 
 When you first start the runner, it generates a private key for authentication with Datadog's servers. This private key is never accessible by Datadog and ensures you exclusive access. Datadog uses a public key derived from the private key as the means to authenticate specific runners.
 

content/en/administrators_guide/plan.md

@@ -348,8 +348,8 @@ Create a detailed roll-out methodology in the [build][41] phase by focusing on t
 [32]: /error_tracking/
 [33]: /software_catalog/endpoints/
 [34]: /agent/fleet_automation/
-[35]: /agent/remote_config/
-[36]: /agent/remote_config/?tab=configurationyamlfile\#supported-products-and-feature-capabilities
+[35]: /remote_configuration
+[36]: /remote_configuration#supported-products-and-features
 [37]: /notebooks/
 [38]: /getting_started/containers/autodiscovery/?tab=adannotationsv2agent736
 [39]: /account_management/billing/aws/#aws-resource-exclusion

content/en/agent/configuration/_index.md

@@ -27,6 +27,6 @@ This section covers information on configuring your Datadog Agents. For informat
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /agent/remote_config/
+[1]: /remote_configuration
 [2]: /containers/
 [3]: /integrations/

content/en/agent/configuration/network.md

@@ -88,7 +88,7 @@ API test results for the Synthetics Worker < v0.1.5: `api.`{{< region-param key=
 : `dbm-metrics-intake.`{{< region-param key="dd_site" code="true" >}}<br>
 `dbquery-intake.`{{< region-param key="dd_site" code="true" >}}
 
-[101]: /agent/remote_config
+[101]: /remote_configuration
 [102]: /database_monitoring/
 
 {{% /site-region %}}

content/en/agent/fleet_automation/_index.md

@@ -2,7 +2,7 @@
 title: Fleet Automation
 disable_toc: false
 further_reading:
-- link: "/agent/remote_config"
+- link: "/remote_configuration"
   tag: "Documentation"
   text: "Find out more about Remote Configuration"
 - link: "/infrastructure/list/#agent-configuration"
@@ -31,17 +31,6 @@ With the Fleet Automation platform, you can:
 - Ensure your fleet of Agents is using the latest feature enhancements by identifying outdated Agent versions.
 - Help rotate API keys and ensure old keys can be disabled with no impact by identifying which Agents, and how many Agents, are using a particular key.
 
-## Configure Fleet Automation
-
-Fleet Automation incorporates several Datadog features, which are all enabled automatically in Agent version 7.49/6.49 or later. To ensure you have access to all of the features, upgrade your Agents to version 7.49/6.49 or later.
-
-If you're using an older Agent, you might still be able to enable the following Datadog features individually:
-- **Remote Configuration**: For information on supported Agent versions and configuration steps, see [Enabling Remote Configuration][3].
-- **Agent configuration**: Agent version 7.39/6.39 or later is required to enable the Agent configuration tab. It is enabled by default in Agent versions 7.47.0/6.47.0 or later. To enable Agent configuration manually, set `inventories_configuration_enabled` in your [Agent configuration file][2] to `true`. Alternatively, use the `DD_INVENTORIES_CONFIGURATION_ENABLED` environment variable.
-- **Agent integration configuration**: Agent integration configuration is enabled by default on Agent versions 7.49/6.49 or later. To enable Agent integration configuration manually, set `inventories_checks_configuration_enabled` in your [Agent configuration file][2] to `true`. Alternatively, use the environment variable `DD_INVENTORIES_CHECKS_CONFIGURATION_ENABLED`.
-
-Datadog recommends upgrading your Agents regularly to make sure you have access to the latest features.
-
 ## Observe your fleet
 
 Use the [**Fleet Automation**][1] page to gain insight into unmonitored hosts, Agents that need to be updated, or Agents that have integration issues. For each Agent, you can see:
@@ -67,7 +56,6 @@ When contacting Datadog Support with Remote Configuration enabled for an Agent,
 
 Remote Agent Management simplifies the process of upgrading your Agent fleet by reducing the need to coordinate with multiple deployment or configuration management tools. For more information, see [Remote Agent Management][6].
 
-
 ## Control access to Fleet Automation
 
 Fleet Automation is available to all users in a Datadog organization. You can control access to specific functionality:
@@ -87,7 +75,7 @@ For information on setting up roles and permissions, see [Access Control][5].
 
 [1]: https://app.datadoghq.com/fleet
 [2]: /agent/configuration/agent-configuration-files/
-[3]: /agent/remote_config#enabling-remote-configuration
+[3]: /remote_configuration#enabling-remote-configuration
 [4]: /infrastructure/list/#agent-configuration
 [5]: https://docs.datadoghq.com/account_management/rbac/
 [6]: /agent/fleet_automation/remote_management/

content/en/agent/fleet_automation/remote_management.md

@@ -5,7 +5,7 @@ further_reading:
 - link: "/agent/fleet_automation/"
   tag: "Documentation"
   text: "Fleet Automation"
-- link: "/agent/remote_config/"
+- link: "/remote_configuration"
   tag: "Documentation"
   text: "Remote Configuration"
 ---
@@ -24,15 +24,19 @@ Remote Agent Management simplifies the process of upgrading your Agent fleet by
 ## Setup
 
 To enable Remote Agent Management:
-1. If you haven't enabled Remote Configuration on the Agent, follow the [configuration instructions][1] to enable it.
+1. Ensure that [Remote Configuration is enabled for your organization][1].
 1. Go to the [Datadog Agent install page][3] for your platform or configuration management tool.
 1. Enable **Remote Agent Management**. Enabling Remote Agent Management adds the `DD_REMOTE_UPDATES` environment variable to the generated Agent installation command.
 
    {{< img src="/agent/fleet_automation/remote-agent-management-toggle.png" alt="Enable the Remote Agent Management toggle." style="width:100%;" >}}
 
 1. Use the generated Agent installation command to upgrade your Agent.
 
-   **Note**: You must run the generated installation command with `DD_REMOTE_UPDATES` set to `true` to gain access to Remote Agent Management. Enabling Remote Agent Management without running the install command does not grant access to the feature.
+   **Note**: You must run the generated installation command with `DD_REMOTE_UPDATES` set to `true` to gain access to Remote Agent Management. Enabling Remote Agent Management without running the installation command does not grant access to the feature.
+1. Select an existing API key or create a new API key, and enable the Remote Configuration capability on the key if it is not already enabled.
+
+   {{<img src="agent/remote_config/RC_Key_updated.png" alt="API Key properties with Remote Configuration capability Enable button." width="90%" style="center">}}
+1. Restart your Agent.
 
 ## Remotely upgrade your Agents
 ### Supported platforms
@@ -82,7 +86,7 @@ The Agent ensures that the appropriate permissions are set for these files. No c
 
 ### Upgrade precedence
 
-For the most consistent upgrade experience, Datadog recommends managing upgrades from one source at a time. Use either Fleet Automation or a configuration management tool. If you run a configuration management tool on an Agent that has already been upgraded using Fleet Automation, the upgrade reverts the Agent to the [`DD_AGENT_MINOR_VERSION`][9]  specified in your configuration. If no `DD_AGENT_MINOR_VERSION` is set, the Agent is upgraded to the latest available version .
+For the most consistent upgrade experience, Datadog recommends managing upgrades from one source at a time. Use either Fleet Automation or a configuration management tool. If you run a configuration management tool on an Agent that has already been upgraded using Fleet Automation, the upgrade reverts the Agent to the [`DD_AGENT_MINOR_VERSION`][9]  specified in your configuration. If no `DD_AGENT_MINOR_VERSION` is set, the Agent is upgraded to the latest available version.
 
 ### Mirrors and proxies
 
@@ -102,7 +106,7 @@ If you need to downgrade an Agent, follow the steps in [Upgrade your Agents](#do
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /agent/remote_config/#enabling-remote-configuration
+[1]: https://app.datadoghq.com/organization-settings/remote-config
 [2]: /account_management/rbac/permissions#fleet-automation
 [3]: https://app.datadoghq.com/account/settings/agent/latest
 [4]: https://app.datadoghq.com/fleet/agent-upgrades

content/en/agent/guide/_index.md

@@ -9,53 +9,54 @@ cascade:
         subcategory: Agent Guides
 ---
 
-{{< whatsnext desc="Configuration guides:" >}}
+{{< header-list header="Configuration guides" >}}
     {{< nextlink href="agent/guide/environment-variables" >}}Agent Environment Variables{{< /nextlink >}}
     {{< nextlink href="agent/guide/installing-the-agent-on-a-server-with-limited-internet-connectivity" >}}Installing the Agent on a server with limited internet connectivity{{< /nextlink >}}
     {{< nextlink href="agent/guide/ansible_standalone_role/" >}}Set up Ansible Using a Standalone Datadog Role{{< /nextlink >}}
     {{< nextlink href="agent/guide/how-do-i-uninstall-the-agent" >}}How do I uninstall the Agent?{{< /nextlink >}}
     {{< nextlink href="agent/guide/linux-key-rotation-2024" >}}Linux key rotation 2024{{< /nextlink >}}
     {{< nextlink href="agent/guide/fips-agent" >}}Install and configure the FIPS Agent{{< /nextlink >}}
+    {{< nextlink href="agent/guide/setup_remote_config" >}}Set up Remote Configuration for Fleet Automation{{< /nextlink >}}
 
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Windows guides:" >}}
+{{< header-list header="Windows guides" >}}
     {{< nextlink href="agent/guide/datadog-agent-manager-windows" >}}Datadog Agent Manager for Windows{{< /nextlink >}}
     {{< nextlink href="agent/guide/windows-agent-ddagent-user" >}}Datadog Windows Agent user{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Cloud infrastructure guides:" >}}
+{{< header-list header="Cloud infrastructure guides" >}}
     {{< nextlink href="agent/guide/can-i-set-up-the-dd-agent-mysql-check-on-my-google-cloudsql/" >}}Can I set up the dd-agent mysql check on my Google CloudSQL?{{< /nextlink >}}
     {{< nextlink href="/agent/guide/heroku-ruby" >}}Instrumenting a Ruby on Rails application on Heroku with Datadog{{< /nextlink >}}
     {{< nextlink href="agent/guide/heroku-troubleshooting/" >}}Datadog-Heroku Buildpack troubleshooting{{< /nextlink >}}
     {{< nextlink href="agent/guide/private-link" >}}Forward your telemetry securely to Datadog over AWS PrivateLink{{< /nextlink >}}
     {{< nextlink href="agent/guide/azure-private-link" >}}Connect to Datadog over Azure Private Link{{< /nextlink >}}
     {{< nextlink href="agent/guide/why-should-i-install-the-agent-on-my-cloud-instances" >}}Why should I install the Datadog Agent on my cloud instances?{{< /nextlink >}}
     {{< nextlink href="agent/guide/gcp-private-service-connect" >}}Connect to Datadog over GCP Private Service Connect{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Integration guides:" >}}
+{{< header-list header="Integration guides" >}}
     {{< nextlink href="agent/guide/use-community-integrations" >}}Use Community Integrations{{< /nextlink >}}
     {{< nextlink href="agent/guide/integration-management" >}}Integration Management{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Agent versioning guides:" >}}
+{{< header-list header="Agent versioning guides" >}}
     {{< nextlink href="agent/guide/upgrade" >}}Upgrade to Agent 7{{< /nextlink >}}
     {{< nextlink href="agent/guide/version_differences" >}}Agent Version differences{{< /nextlink >}}
     {{< nextlink href="agent/guide/upgrade_between_minor_versions" >}}Upgrade Between Minor Versions of the Datadog Agent{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-v6-python-3" >}}Python version management: Use Python 3 with Datadog Agent v6{{< /nextlink >}}
     {{< nextlink href="agent/guide/python-3" >}}Python 2 to 3 Custom Check Migration{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Agent 6 guides:" >}}
+{{< header-list header="Agent 6 guides" >}}
     {{< nextlink href="agent/guide/install-agent-6" >}}Install Agent 6{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-6-commands" >}}Agent 6 commands{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-6-configuration-files" >}}Agent 6 configuration files{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-6-log-files" >}}Agent 6 log files{{< /nextlink >}}
     {{< nextlink href="agent/guide/upgrade_to_agent_6" >}}Upgrade to Agent 6{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}
 
-{{< whatsnext desc="Agent 5 guides:" >}}
+{{< header-list header="Agent 5 guides" >}}
     {{< nextlink href="agent/guide/agent-5-architecture" >}}Agent 5 architecture{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-5-commands" >}}Agent 5 commands{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-5-configuration-files" >}}Agent 5 configuration files{{< /nextlink >}}
@@ -70,4 +71,4 @@ cascade:
     {{< nextlink href="agent/guide/agent-5-permissions-issues" >}}Agent 5 permission issues{{< /nextlink >}}
     {{< nextlink href="agent/guide/agent-5-debug-mode" >}}Agent 5 debug mode{{< /nextlink >}}
     {{< nextlink href="agent/guide/dogstream" >}}Dogstream{{< /nextlink >}}
-{{< /whatsnext >}}
+{{< /header-list >}}