Choose a deployment
Choose where Bower runs before connecting a source. Start with the supported guide for your environment, then return to your first verified event.
| Environment | Start here | What to check |
|---|---|---|
| Linux hosts | deb/rpm packages and Ansible | Service identity, queue storage and outbound connectivity. |
| Windows hosts | MSI installer and Windows Event Log | The current source has a narrow channel/event allow-list. WEC-first rollout remains planned. |
| Containers | Container images, console, Docker sidecar | Durable volumes and explicit source opt-in. |
| AWS servers with the CloudWatch agent | Quick start: CloudWatch agent | Events reach CloudWatch Logs before Bower redacts them; keep retention short. |
| Linux Azure VMs or Arc servers with Azure Monitor Agent | Quick start: Azure Monitor Agent | Any local account can write rows on this path; compare the three Azure paths. Rate limits and a free syslog facility. |
| AWS | AWS security sources | Queue permissions and least privilege. |
| Google Cloud | GCP security sources | Pub/Sub acknowledgement and forwarding configuration. |
| Azure Functions | Azure Functions collector | This path currently has no durable queue; durable ingest is tracked in issue #137. |
| Segmented networks | Relay mode | Mutual TLS, allowed collectors and downstream connectivity. |
Planned deployment paths
Kubernetes container sources, full WEC/GPO rollout and signed air-gapped bundle workflows are still being developed. An offline installer does not mean the entire product supports disconnected operation. Track open work on GitHub and use the current deployment guides as the source of truth.
Infrastructure templates are plan-first. Review the plan, identities and cost before applying it. Cloud permission context explains what each credential is allowed to do.