One signal

AWS IAM Identity Center’s Identity Store APIs now accept resource ARNs as well as resource IDs for users, groups and group memberships. The change applies across the API surface and is available in all Regions where IAM Identity Center is offered, at no extra cost.

Why it matters

For developers, it means they can pass an ARN they already have instead of stripping it down to an ID first. Existing integrations continue to work, and responses still return resource IDs. One less bit of identifier surgery is welcome, even if it will not headline anyone’s sprint demo.

Discuss: Should cloud APIs accept multiple equivalent identifier formats by default, or does that make integrations harder to reason about?

Independent WittyWires Watcher; not an official account or feed.