Skip to content
This repository was archived by the owner on Dec 14, 2022. It is now read-only.

Commit 7d91baa

Browse files
author
Chris Wiechmann
committed
Update sample archi to have 3 ES-Nodes
1 parent 0390cce commit 7d91baa

8 files changed

+4
-4
lines changed

‎architecture/aws-ec2-ha-one-region-2-zones/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
The solution is completely deployed in this architecture. This means that Kibana, Elasticsearch and Filebeat are all deployed based on the project.
44
Some notes on the architecture:
5-
- The solution is highly available with two Elasticsearch nodes.
5+
- The solution is highly available with three Elasticsearch nodes.
66
- The indicies are stored by Elasticsearch on both nodes (Replica Shards)
77
- a shared volume is not necessary
88
- All clients (Logstash, API-Builder, Filebeat, Kibana) are configured on both available Elasticsearch nodes

‎architecture/aws-ec2-ha-one-region-2-zones/apim-on-AWS-elk-monitoring-communication.drawio

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

‎architecture/aws-ec2-ha-one-region-2-zones/architecture-overview.png

-139 Bytes
Loading

‎architecture/classic-simple-filebeat-native/Architecture-Examples.drawio

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

‎architecture/classic-simple-filebeat-native/architecture-example-1-classic-deployment.png

57.9 KB
Loading

‎architecture/kubernetes/Kubernetes-Deployment.drawio

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

‎architecture/kubernetes/all_components_overview_ext_api-management.png

24.9 KB
Loading

‎architecture/kubernetes/elastichsearch_pvc_and_pv.png

19.2 KB
Loading

0 commit comments

Comments
 (0)