You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IAM Identity Center bootstrap for a user with no profile yet (#65). aws_login_start takes ssoSession + startUrl + ssoRegion: it writes a managed [sso-session] block to the AWS config file and runs aws sso login --sso-session (AWS CLI 2.9.0+, with AWS_PROFILE stripped from the child so a stale one cannot fail it). aws_login_complete on such a login returns the token status instead of running an identity check there is no profile for. Two new tools follow it: aws_sso_list_assignments (read-only; every account and role the login can use, flagging which already have a profile) and aws_sso_generate_profiles (writes [profile ...] sections for all assignments, up to 200, or a selection; dryRun previews). Generated sections carry a managed-by: aws-mcp marker and are the only sections aws-mcp ever changes -- a hand-written section is never modified, and every other byte of the file is preserved. The SSO bearer token reaches the CLI only through a 0600 temp file and never appears in a tool result. aws_list_profiles gains ssoAccountId, ssoRoleName and managed.
Changed
The oam floor moves from 0.19.1 to 0.19.5, so the aws-mcp launcher no longer runs the server on oam 0.19.1-0.19.4. 0.19.5 is verified on the installed aarch64-pc-windows-msvc binary through the launcher with OAM_BIN pointing at it and AWS_MCP_RUNTIME=oam: a full MCP handshake listing all 30 tools, aws_list_profiles served, and the documented aws_script sandbox divergence re-measured on it (eval('1+1') returns 2 and Function('return 7')() returns 7 under oam; Function('return this')() yields a global with no process and no require; both raise the code-generation error under Node).
The locked atomic writer behind aws_assume_role's credentials file moved to src/ini-file.ts and is shared with the config-file writer. No behaviour change for aws_assume_role.
README: new section "Multi-user gateways: one process per user" (#65) -- run one aws-mcp process per user, each with its own HOME/USERPROFILE, AWS_CONFIG_FILE, AWS_SHARED_CREDENTIALS_FILE and TMPDIR, routed by the gateway's verified principal.
Fixed
AWS_CONFIG_FILE and AWS_SHARED_CREDENTIALS_FILE are honoured everywhere the server reads those files itself (#67). aws_list_profiles, the profile start-URL lookup that picks the cached SSO token for aws_whoami, aws_login_complete and aws_refresh_if_expiring_soon, and aws_assume_role read ~/.aws/config / ~/.aws/credentials directly, so with either variable set they disagreed with the aws CLI they spawn. Paths now resolve as botocore resolves them: $NAME / ${NAME} (and %NAME% on Windows) are expanded, then ~; an unset reference is left as written; the value is not trimmed; and a set-but-empty value means "no file", which aws_list_profiles reports as an error and aws_assume_role refuses, instead of falling back to the default path.
SSO device login recognizes the newer verification URLs (#66, thanks @SolomonHD). aws_login_start now accepts the IAM Identity Center portal (https://<id>.awsapps.com/start/#/device) and AWS sign-in (https://...signin.aws/.../device) forms. A signin.aws URL must end in /device, so an unrelated sign-in URL cannot suppress the PKCE fallback, and the URL is re-read from the full output when the login settles, so a stdout chunk split inside ?user_code=... no longer drops the code.
Security
Lockfile-only bumps, within existing ranges, clearing all open Dependabot alerts and npm audit findings (#70): undici 8.12.4 (3 high), fast-uri 3.1.9, hono 4.13.18, @hono/node-server 2.1.7, zod 4.6.7, body-parser 2.4.0, qs 6.17.1, ip-address 10.7.6.