Skip to main content

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.

EnvironmentStart hereWhat to check
Linux hostsdeb/rpm packages and AnsibleService identity, queue storage and outbound connectivity.
Windows hostsMSI installer and Windows Event LogThe current source has a narrow channel/event allow-list. WEC-first rollout remains planned.
ContainersContainer images, console, Docker sidecarDurable volumes and explicit source opt-in.
AWS servers with the CloudWatch agentQuick start: CloudWatch agentEvents reach CloudWatch Logs before Bower redacts them; keep retention short.
Linux Azure VMs or Arc servers with Azure Monitor AgentQuick start: Azure Monitor AgentAny local account can write rows on this path; compare the three Azure paths. Rate limits and a free syslog facility.
AWSAWS security sourcesQueue permissions and least privilege.
Google CloudGCP security sourcesPub/Sub acknowledgement and forwarding configuration.
Azure FunctionsAzure Functions collectorThis path currently has no durable queue; durable ingest is tracked in issue #137.
Segmented networksRelay modeMutual 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.