Skip to main content
Choose a deployment based on the number of services you need and how much provisioning you want the CLI to coordinate. Cloud Adapter uses the same adapter implementations across these choices. A broader deployment does not add API operations to a service mapping.

​
Identity and networking

Distinguish the application-facing endpoint from the backend connection. The application must reach the adapter; the adapter must reach its backend and any coordination store. Each connection needs its own network and authentication design. Do not equate private placement with authentication. Before exposing a listener beyond the local host, verify the release’s supported request-authentication mode, transport security and network policy. An AWS-shaped request is not proof that its signature has been verified. Use the least privilege needed for backend operations. Keep provisioning credentials separate from runtime credentials where the deployment supports that separation.

​
State and availability

Inventory application data, adapter state and coordination state separately. Give each an owner, backup policy and recovery procedure. Replicating a process does not replicate or back up every store on which it depends. Availability also depends on the backend and the network path to it. Exercise a backend failure and a process restart with test data before relying on either deployment shape for production traffic.

​
Setup and updates

The provisioned setup is designed to accept configuration from a file or generate it through guided questions. Later configuration changes are orchestrated by the local CLI, with compatibility checks and coordinated restarts. See operations.