Can I restrict an AWS SSO session to specific resources and actions?

Yes. AWS session policies can further restrict the permissions of temporary credentials when you assume a role or obtain federated access. The effective permissions are the intersection of the role’s identity policies and the session policy, so a broad role can be narrowed for that specific session. Keep in mind that session policies can’t grant permissions the role doesn’t already have, and resource-level restrictions depend on whether the AWS action supports them.

Another approach is to use separate roles or permission sets for common workflows, such as read-only access, SSM access, backup administration, or deployment work. This is often easier to audit and less error-prone than creating a custom policy for every session. For AI-assisted work, giving the assistant a dedicated read-only or narrowly scoped role while keeping elevated operations human-approved is a sensible safeguard.

Session policies are probably the closest match to what you described. For example, you could assume a role that has broad EC2 and S3 permissions while passing a policy allowing only the required EC2 actions on one instance and read operations on one bucket. AWS then evaluates the role and session policy together and permits only the overlap.

For more dynamic setups, you can combine role chaining, session tags, and ABAC or resource-based policies to select the resources a session can access. Just be aware that ABAC coverage varies by AWS service, so some environments need a mixture of tags, explicit policies, permission boundaries, and purpose-built roles. The AI component doesn’t fundamentally change the IAM model—it mainly makes choosing and enforcing the right scope more important.