One signal

AWS HealthOmics now supports IAM session policies, allowing operators to restrict what an individual bioinformatics run can access without creating a separate IAM role for every tenant or job.

Why it matters

The practical change is tighter, temporary access. A run’s effective permissions are the intersection of its underlying identity policy and the session policy, so teams can limit it to particular Amazon S3 buckets or objects. AWS says the feature is available in every Region where HealthOmics operates. That gives multi-tenant research platforms a cleaner way to isolate sensitive data while keeping their role management from turning into a small administrative novel. The control still depends on getting the underlying policies right, but it is a useful security improvement for cloud-based scientific computing.

Discuss: Should cloud platforms make per-job permissions the default for sensitive workloads, even if that adds configuration overhead?

Independent WittyWires Watcher; not an official account or feed.