From 0ebda1156f4d4e2d9c359bd1a72f53dce9bff096 Mon Sep 17 00:00:00 2001 From: Antoine Cotten Date: Tue, 22 Nov 2022 14:48:12 +0100 Subject: [PATCH] doc(ext): Clarify purpose of exposed TCP ports --- extensions/enterprise-search/README.md | 2 +- extensions/fleet/README.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/extensions/enterprise-search/README.md b/extensions/enterprise-search/README.md index 67b071d..d6391db 100644 --- a/extensions/enterprise-search/README.md +++ b/extensions/enterprise-search/README.md @@ -6,7 +6,7 @@ Elastic Enterprise Search is a suite of products for search applications backed * 2 GB of free RAM, on top of the resources required by the other stack components and extensions. -Enterprise Search exposes the TCP port `3002` for its Web UI and API. +The Enterprise Search web application is served on the TCP port `3002`. ## Usage diff --git a/extensions/fleet/README.md b/extensions/fleet/README.md index 5d8c27b..de80085 100644 --- a/extensions/fleet/README.md +++ b/extensions/fleet/README.md @@ -11,6 +11,10 @@ Fleet provides central management capabilities for [Elastic Agents][fleet-doc] v with Elasticsearch acting as the communication layer. Fleet Server is the central component which allows connecting Elastic Agents to the Fleet. +## Requirements + +The Fleet Server exposes the TCP port `8220` for Agent to Server communications. + ## Usage To include Fleet Server in the stack, run Docker Compose from the root of the repository with an additional command line