iac
/
docker-elk
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc(ext): Clarify purpose of exposed TCP ports

This commit is contained in:
Antoine Cotten 2022-11-22 14:48:12 +01:00
parent e202d6ba7c
commit 0ebda1156f
No known key found for this signature in database
GPG Key ID: 94637E68D4A79DD0
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
extensions/enterprise-search/README.md
View File

@ -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

4
extensions/fleet/README.md
View File

@ -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