Sélectionner vos préférences de cookies

Nous utilisons des cookies essentiels et des outils similaires qui sont nécessaires au fonctionnement de notre site et à la fourniture de nos services. Nous utilisons des cookies de performance pour collecter des statistiques anonymes afin de comprendre comment les clients utilisent notre site et d’apporter des améliorations. Les cookies essentiels ne peuvent pas être désactivés, mais vous pouvez cliquer sur « Personnaliser » ou « Refuser » pour refuser les cookies de performance.

Si vous êtes d’accord, AWS et les tiers approuvés utiliseront également des cookies pour fournir des fonctionnalités utiles au site, mémoriser vos préférences et afficher du contenu pertinent, y compris des publicités pertinentes. Pour accepter ou refuser tous les cookies non essentiels, cliquez sur « Accepter » ou « Refuser ». Pour effectuer des choix plus détaillés, cliquez sur « Personnaliser ».

Identity-based IAM policies for HealthOmics

Mode de mise au point
Identity-based IAM policies for HealthOmics - AWS HealthOmics
Cette page n'a pas été traduite dans votre langue. Demande de traduction

To grant users in your account access to HealthOmics, you use identity-based policies in AWS Identity and Access Management (IAM). Identity-based policies can apply directly to IAM users, or to IAM groups and roles that are associated with a user. You can also grant users in another account permission to assume a role in your account and access your HealthOmics resources.

The following IAM policy allows a user to access all HealthOmics API actions, and to pass service roles to HealthOmics.

Example User policy
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "omics:*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "iam:PassRole" ], "Resource": "*", "Condition": { "StringEquals": { "iam:PassedToService": "omics.amazonaws.com" } } } ] }

When you use HealthOmics, you also interact with other AWS services. To access these services, use the managed policies provided by each service. To restrict access to a subset of resources, you can use the managed policies as a starting point to create your own more restrictive policies.

The preceding policies don't allow a user to create IAM roles. For a user with these permissions to run a job, an administrator must create the service role that grants HealthOmics permission to access data sources. For more information, see Service roles for AWS HealthOmics.

Define custom IAM permissions for runs

You can include any workflow, run, or run group referenced by the StartRun request in an authorization request. To do so, list the desired combination of workflows, runs, or run groups in the IAM policy. For example, you can limit the use of a workflow to a specific run or run group. You can also specify that a workflow only be used with a run group.

The following is an example IAM policy that allows a single workflow with a single run group.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "omics:StartRun" ], "Resource": [ "arn:aws:omics:us-west-2:123456789012:workflow/1234567", "arn:aws:omics:us-west-2:123456789012:runGroup/2345678" ] }, { # Optionally, allow user to rerun a failed run. "Effect": "Allow", "Action": [ "omics:StartRun" ], "Resource": [ "arn:aws:omics:us-west-2:123456789012:run/*", "arn:aws:omics:us-west-2:123456789012:runGroup/2345678" ] }, { "Effect": "Allow", "Action": [ "omics:GetRun", "omics:ListRunTasks", "omics:GetRunTask", "omics:CancelRun", "omics:DeleteRun" ], "Resource": [ "arn:aws:omics:us-west-2:123456789012:run/*" ] }, ] }

Rubrique suivante :

Service roles

Rubrique précédente :

Permissions

Sur cette page

ConfidentialitéConditions d'utilisation du sitePréférences de cookies
© 2025, Amazon Web Services, Inc. ou ses affiliés. Tous droits réservés.