THE FIELD GUIDE / FLEET MANAGEMENT

Native cloud transports to the endpoint agent

Reach the existing Mr Patchy endpoint agent through supported AWS, Google Cloud and Azure APIs.

Mr Patchy documentation · 2 min read

Choose a route for the enrolled host

Direct SSH and Google Cloud IAP keep their existing trust model. The native cloud transport uses AWS Systems Manager, the supported Google Cloud execution route or Azure Managed Run Command to invoke typed operations through the existing agent. Check provider capability and host identity before switching routes.

Limit cloud and target permissions

Use scoped workload identities and provider permissions constrained to the intended instance and operation path. The controller validates cloud account or project, region and instance identity. The endpoint validates the Mr Patchy request and reports bounded, redacted output.

Diagnose before retrying

Separate cloud authentication, service readiness, API admission and endpoint receipt errors. A cloud timeout can leave execution uncertain. Reconcile the original request and target receipt before resubmitting a mutation. Read-only inventory and unsupported actions have explicit capability states.

Go deeper

Open the application reference for capability scope and technical details.

Open View scope in issue #359 ↗

Actual application interface with illustrative documentation data.