We are missing the mentioning of artifacts.elastic.co in our overview…

… docs (#310) (#313)

* Update overview.asciidoc

* Update docs/en/ingest-management/overview.asciidoc

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>

---------

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
(cherry picked from commit a8a05a2)

Co-authored-by: Philipp Kahr <philipp.kahr@elastic.co>

docs/en/ingest-management/overview.asciidoc

@@ -75,6 +75,17 @@ in {es}. This process typically requires an internet connection because
 integrations are updated and released periodically. You can find more information about running the {package-registry} in air-gapped
 environments in the section about {fleet-guide}/air-gapped.html[Air-gapped environments].
 
+[discrete]
+[[artifact-registry-intro]]
+== Elastic Artifact Registry
+
+{fleet} and {agent} require access to the public Elastic Artifact Registry. The {agent} running on any of your internal hosts should have access to `artifacts.elastic.co` in order to perform self-upgrades and install of certain components which are needed for some of the data integrations.
+
+Additionally, access to `artifacts.security.elastic.co` is needed for {agent} updates and security artifacts when using {elastic-defend}.
+
+You can find more information about running the above mentioned resources in air-gapped
+environments in the section about {fleet-guide}/air-gapped.html[Air-gapped environments].
+
 [discrete]
 [[central-management]]
 == Central management in {fleet}
@@ -156,3 +167,4 @@ The data collected by {agent} is stored in indices that are more granular than
 you'd get by default with the {beats} shippers or APM Server. This gives you more visibility into the
 sources of data volume, and control over lifecycle management policies and index
 permissions. These indices are called <<data-streams,_data streams_>>.
+