The entrypoint can generate AWS CLI profiles that retrieve short-lived credentials from an independently managed host proxy. The sandbox does not start or own that service.
Set AWS_AI_PROXY_PROFILE_CONFIG to a comma-separated list of profile mappings.
For each entry, startup writes an AWS credential_process stanza under the
sandbox user's ~/.aws/config. AWS_AI_PROXY_URL selects the proxy endpoint and
defaults to http://host.docker.internal:9998.
The generated configuration exposes only what the external proxy authorizes. Refresh expired authentication on the host, and do not treat this integration as a substitute for least-privilege AWS policy.
The shared image includes AWS CLI so generated profiles can be used directly by tools inside the sandbox.
Compose forwards AWS_AI_PROXY_ENABLED, AWS_AI_PROXY_URL, and
AWS_AI_PROXY_PROFILE_CONFIG to the harness. Set the enabled flag only when the
host service is running and reachable from host.docker.internal; the default
URL uses port 9998.
On start or rebuild, the controller queries the enabled profile list and derives the container-side profile mappings. Expired SSO sessions must be refreshed on the host. The sandbox consumes the resulting short-lived, read-only credentials but never manages the host proxy.