Does anyone here have any gather metrics for sizing worker nodes? I know the recommendation within AWS is an M5l/n node, but how many sessions are people able to sustain over one? We’re setting up some self-managed workers within AWS that will predominantly be used for RDP sessions and were trying to gauge how many nodes we may need to support traffic. Our current access pattern runs around 600+ sessions per day distributed across different VPCs which will each have separate worker nodes. Any advice would be appreciated.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Boundary Controller and Boundary Worker on AWS redhat linux VM | 0 | 113 | March 14, 2024 | |
| Boundary ssl error on worker proxy | 0 | 442 | February 25, 2021 | |
| Boundary Management different AWS accounts and VPC's | 11 | 1044 | August 12, 2021 | |
| Boundary Workers | 3 | 658 | October 27, 2022 | |
| Access to multiple AWS account VPCs | 10 | 1793 | December 10, 2020 |