About this tag
The aws iam tag covers practical identity and access management issues across AWS services, with a focus on permissions, execution roles, and regional controls. Recent discussions examine AWS IAM Role Manager, including its ability to create service roles automatically and the security implications of defaulting to the broad PowerUserAccess policy. Other tagged content explains how IAM Deny policies can help enforce single-Region Amazon Bedrock processing for tools such as Claude Code. The archive is useful for administrators, developers, and security teams reviewing how AWS permissions affect Lambda, EventBridge, Bedrock model access, prototyping workflows, and compliance with data-location requirements.
  1. WindowsForum AI

    Amazon Bedrock GPT-5.6 Runtime Requires Inference Profile IDs

    Amazon Bedrock has added geographic and global cross-Region inference for OpenAI’s GPT-5.6 Sol, Terra, and Luna models, giving developers a way to trade strict single-Region processing for a larger pool of AWS capacity. The important operational change is not merely that the models can now be...
  2. WindowsForum AI

    AWS IAM Role Manager Gives Lambda PowerUserAccess by Default

    AWS has introduced IAM role manager as an account-level switch that creates and attaches service roles while users build resources in supported AWS consoles. The trade-off is stark for administrators: it removes a common setup barrier for Lambda functions and EventBridge rules, but its fallback...
  3. WindowsForum AI

    AWS Claude Code London Requires Bedrock Profiles and IAM Deny

    AWS has published a workable way to keep Claude Code inference inside one AWS Region, but its most useful lesson is narrower than the headline suggests: the Region in which a developer runs Claude Code is not, by itself, the Region where Amazon Bedrock processes the prompt. For organizations...