Repository navigation
Google Cloud from AWS, with no key (lm15-contract f67699c, AUTH-1 gcp-chain; 4,271 of 4,271 checks, the same in every lm15 language; the amendment waits for ratification).
- New: a Google
external_accountcredential with an AWS source, whatgcloud iam workload-identity-pools create-cred-config … --awswrites. Vertex (vertex,vertex-anthropic) can now be reached from AWS through workload identity federation, for organizations that forbid API keys. Every lm15 language used to refuse it as a stated gap. lm15 signs an AWS STSGetCallerIdentityrequest with the AWS identity, Google's STS exchanges it, then the configuration's service account is impersonated. The subject token is google-auth's, byte for byte: two new contract vectors were computed by google-auth itself. - Where the AWS identity comes from:
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY(Lambda), then the container endpoint (ECS and EKS Pod Identity: the task's role), then EC2 metadata at the file'surl. IMDSv2 is used when the file names its token URL, with one session token per acquisition. The container endpoint is an lm15 addition: Google's own libraries skip it, so on ECS they sign as the host's role or find nothing. The region comes fromAWS_REGION, thenAWS_DEFAULT_REGION, else the file'sregion_url. - A source that is not
aws1, or that lacksregional_cred_verification_url, is refused before any request. When no AWS identity is found, the error says what was looked for. - Checked live (2026-11-12): Gemini on Vertex answered through a federated AWS identity, from the environment's keys and from a container endpoint. A service account with only
aiplatform.endpoints.predictis enough for Gemini.
Use it: point GOOGLE_APPLICATION_CREDENTIALS at the file and name the credential workload (Vertex, below), or leave the chain to find it.
In Rust: RouterConfig::new().credential("vertex", "workload"), then "vertex:gemini-2.5-flash" as the model. New public function lm15::cloud::chains::gcp_aws_subject_token.