AccessBot has different Infrastructures depending on the Platform you want to use.
When using Slack, AccessBot uses Slack Socket Mode to communicate with Slack, as you can see in the diagram below:
Because of that, AccessBot doesn't support Load Balancing. Our recommendation is to use a Container Orchestrator and use it with a single replica and a liveness probe (e.g. k8s-descriptor.yaml).
In this scenario, for basic operations you don't need to configure any ingress rule.
When using MS Teams, AccessBot needs to expose an endpoint on port 3141 that Azure is going to hit whenever there is a user request. After that, AccessBot uses the Teams API (BotFramework API) to send messages. This communication you can see in the diagram below:
Putting aside the platform you want to use, there are some points you need to pay attention to:
- AccessBot has an endpoint on port 3141 that you can use for checking the health status:
http://localhost:3141/health-check - AccessBot needs an ingress port on 3142 for monitoring metrics