mirror of
https://github.com/telekom-security/tpotce.git
synced 2025-07-04 14:02:13 +00:00
Created T-Pot, RAM and Elastic Stack (markdown)
parent
84b1ac3b29
commit
89bfc38118
1 changed files with 14 additions and 0 deletions
14
T-Pot,-RAM-and-Elastic-Stack.md
Normal file
14
T-Pot,-RAM-and-Elastic-Stack.md
Normal file
|
@ -0,0 +1,14 @@
|
|||
With the latest Elastic Stack (7.16+) having 16GB of RAM for T-Pot is probably the best choice for all of the Elastic Tools to run and start up without any errors.
|
||||
However, not every one has the option for 16GB of RAM. You can adjust `/opt/tpot/etc/tpot.yml` to limit the Elastic RAM usage.
|
||||
|
||||
It is assumed you make all the changes as root (`sudo su -`)
|
||||
1. Stop T-Pot (`sytemctl stop tpot`)
|
||||
2. `vi /opt/tpot/etc/tpot.yml`
|
||||
3. Search for `Elasticsearch service` and adjust the following lines to your needs (uncommenting should be enough in most cases):
|
||||
```
|
||||
# - ES_JAVA_OPTS=-Xms2048m -Xmx2048m
|
||||
# mem_limit: 4g
|
||||
```
|
||||
4. Save and `reboot`.
|
||||
|
||||
Limiting RAM might have a negative impact on your Elastic Stack performance, especially if you want to run queries for a large timeframe.
|
Loading…
Reference in a new issue