# Identity and Access Management for AWS HealthImaging Identity and Access Management AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use HealthImaging resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [ ## Audience ](#security_iam_audience) + [ ## Authenticating with identities ](#security_iam_authentication) + [ ## Managing access using policies ](#security_iam_access-manage) + [ # How AWS HealthImaging works with IAM ](security_iam_service-with-iam.md) + [ # Identity-based policy examples for AWS HealthImaging ](security_iam_id-based-policy-examples.md) + [ # AWS managed policies for AWS HealthImaging ](security-iam-awsmanpol.md) + [ # Cross-service confused deputy prevention in HealthImaging ](cross-service-confused-deputy-prevention.md) + [ # Using service-linked roles for HealthImaging ](security-iam-service-linked-roles.md) + [ # Troubleshooting AWS HealthImaging identity and access ](security_iam_troubleshoot.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS HealthImaging identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How AWS HealthImaging works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [Identity-based policy examples for AWS HealthImaging](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### Federated identity As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials. A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials. For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # How AWS HealthImaging works with IAM Before you use IAM to manage access to HealthImaging, learn what IAM features are available to use with HealthImaging. **IAM features you can use with AWS HealthImaging** | IAM feature | HealthImaging support | | --- | --- | | [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes | | [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No | | [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes | | [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes | | [Policy condition keys (service-specific)](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes | | [ACLs](#security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Partial | | [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes | | [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#security_iam_service-with-iam-roles-service) | Yes | | [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes | To get a high-level view of how HealthImaging and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Identity-based policies for HealthImaging Identity-based policies **Supports identity-based policies:** Yes HealthImaging supports condition statements that specify DICOM Study and Series UIDs, enabling access control scoped to one or more DICOM Study or Series. Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. ### Identity-based policy examples for HealthImaging To view examples of HealthImaging identity-based policies, see [Identity-based policy examples for AWS HealthImaging](security_iam_id-based-policy-examples.md). ## Resource-based policies within HealthImaging Resource-based policies **Supports resource-based policies:** No Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Policy actions for HealthImaging Policy actions **Supports policy actions:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. To see a list of HealthImaging actions, see [ Actions defined by AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html#awshealthimaging-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in HealthImaging use the following prefix before the action: ``` medical-imaging ``` To specify multiple actions in a single statement, separate them with commas. ``` "Action": [ "medical-imaging:action1", "medical-imaging:action2" ] ``` To view examples of HealthImaging identity-based policies, see [Identity-based policy examples for AWS HealthImaging](security_iam_id-based-policy-examples.md). ## Policy resources for HealthImaging Policy resources **Supports policy resources:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` To see a list of HealthImaging resource types and their ARNs, see [ Resource types defined by AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html#awshealthimaging-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions and resources you can use an ARN, see [ Actions defined by AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html#awshealthimaging-actions-as-permissions). To view examples of HealthImaging identity-based policies, see [Identity-based policy examples for AWS HealthImaging](security_iam_id-based-policy-examples.md). ## Policy condition keys for HealthImaging Policy condition keys **Supports service-specific policy condition keys:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. To see a list of HealthImaging condition keys, see [ Condition keys for AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html#awshealthimaging-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [ Actions defined by AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html#awshealthimaging-actions-as-permissions). To view examples of HealthImaging identity-based policies, see [Identity-based policy examples for AWS HealthImaging](security_iam_id-based-policy-examples.md). ## ACLs in HealthImaging ACLs **Supports ACLs:** No Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. ## RBAC with HealthImaging RBAC | | | | --- |--- | | Supports RBAC | Yes | The traditional authorization model used in IAM is called role-based access control (RBAC). RBAC defines permissions based on a person's job function, known outside of AWS as a *role*. For more information, see [Comparing ABAC to the traditional RBAC model](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html#introduction_attribute-based-access-control_compare-rbac) in the *IAM User Guide*. ## ABAC with HealthImaging ABAC **Supports ABAC (tags in policies):** Partial **Warning** ABAC is not enforced via the `SearchImageSets` API action. Anyone who has access to the `SearchImageSets` action can access all metadata for image sets in a data store. **Note** Image sets are a child resource of data stores. To use ABAC, an image set must have the same tag as a data store. For more information, refer to [Tagging resources with AWS HealthImaging](tagging.md). Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys. If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**. For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*. ## Using temporary credentials with HealthImaging Temporary credentials **Supports temporary credentials:** Yes Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Cross-service principal permissions for HealthImaging Principal permissions **Supports forward access sessions (FAS):** Yes When you use an IAM user or role to perform actions in AWS, you are considered a principal. Policies grant permissions to a principal. When you use some services, you might perform an action that then triggers another action in a different service. In this case, you must have permissions to perform both actions. To see whether an action requires additional dependent actions in a policy, see [ Actions, resources, and condition keys for AWS HealthImaging](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awshealthimaging.html) in the *Service Authorization Reference*. ## Service roles for HealthImaging Service roles **Supports service roles:** Yes A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. **Warning** Changing the permissions for a service role might break HealthImaging functionality. Edit service roles only when HealthImaging provides guidance to do so. ## Service-linked roles for HealthImaging Service-linked roles **Supports service-linked roles:** Yes A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. HealthImaging uses service-linked roles to [publish CloudWatch metrics to your account](https://docs.aws.amazon.com/healthimaging/latest/devguide/monitoring-cloudwatch.html#setup-metrics). For details about creating or managing service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). # Identity-based policy examples for AWS HealthImaging Identity-based policy examples By default, users and roles don't have permission to create or modify HealthImaging resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*. For details about actions and resource types defined by Awesome, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for AWS Awesome ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html) in the *Service Authorization Reference*. **Topics** + [ ## Policy best practices ](#security_iam_service-with-iam-policy-best-practices) + [ ## Using the HealthImaging console ](#security_iam_id-based-policy-examples-console) + [ ## Allow users to view their own permissions ](#security_iam_id-based-policy-examples-view-own-permissions) + [ ## Granting permissions based on Study Instance UID and Series Instance UID ](#security_iam_id-based-policy-examples-study-series-uid) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete HealthImaging resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: + **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## Using the HealthImaging console Using the console To access the AWS HealthImaging console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the HealthImaging resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform. To ensure that users and roles can still use the HealthImaging console, also attach the HealthImaging `ConsoleAccess` or `ReadOnly` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*. ## Allow users to view their own permissions This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] } ``` ## Granting permissions based on Study Instance UID and Series Instance UID HealthImaging DICOMWeb APIs support granting access to image sets based on the Study Instance UID and Series Instance UID. You can define IAM policies that limit access by adding condition statements with the `StudyInstanceUID` and `SeriesInstanceUID` condition context keys. HealthImaging DICOMWeb APIs that use `StudyInstanceUID` as a required parameter support IAM policies that limit access based on the `StudyInstanceUID` key. Similarly, HealthImaging DICOMWeb APIs that use `SeriesInstanceUID` as a required parameter support policies with the `SeriesInstanceUID` key. **HealthImaging APIs that support IAM policies using `StudyInstanceUID` and `SeriesInstanceUID` context keys** | Name | Support for `StudyInstanceUID` condition | Support for `SeriesInstanceUID` condition | | --- | --- | --- | | GetDICOMInstance | Yes | Yes | | GetDICOMInstanceFrames | Yes | Yes | | GetDICOMInstanceMetadata | Yes | Yes | | GetDICOMSeriesMetadata | Yes | Yes | | GetDICOMBulkdata | Yes | Yes | | SearchDICOMSeries | Yes | No | | SearchDICOMInstances | Yes | Yes | | StoreDICOMStudy | Yes | No | **Note** A HealthImaging API that does not support this context key will function as if no context key was specified when invoked with a policy that contains a `StudyInstanceUID` or `SeriesInstanceUID` context key. ### Example 1: Granting access based on a StudyInstanceUID To grant access only to specific DICOM studies, attach a policy to the role that specifies a condition on the `StudyInstanceUID`. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "medical-imaging:SearchDICOMSeries" ], "Resource": [ "arn:aws:medical-imaging:us-west-2:account-id:datastore/your-datastore-id" ], "Condition": { "StringEquals": { "medical-imaging:StudyInstanceUID": "your study instance UID" } } } ] } ``` When this role is assumed via `sts assume-role`, the caller will only be authorized to access image sets that match the condition specified in the role policy, otherwise the calls will be rejected throwing an `AccessDenied` error. In this case, the caller will be granted access to all image sets having the specified `StudyInstanceUID`. You can use all IAM string condition operators in your policies, including wildcard matching and multiple matches. An example policy for wildcard matching: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "medical-imaging:SearchDICOMSeries" ], "Resource": [ "arn:aws:medical-imaging:us-west-2:account-id:datastore/your-datastore-id" ], "Condition": { "StringLike": { "medical-imaging:StudyInstanceUID": "123.456.789*" } } } ] } ``` An example policy for multiple matches: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "medical-imaging:SearchDICOMSeries" ], "Resource": [ "arn:aws:medical-imaging:us-west-2:account-id:datastore/your-datastore-id" ], "Condition": { "StringEquals": { "medical-imaging:StudyInstanceUID": [ "123.456.789", "1.2.3.4.5.6" ] } } } ] } ``` ### Example 2: Granting access based on a SeriesInstanceUID To grant access only to specific image sets corresponding to a DICOM Series, attach a policy to the role that specifies a condition on the `SeriesInstanceUID`. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "medical-imaging:SearchDICOMInstances" ], "Resource": [ "arn:aws:medical-imaging:us-west-2:account-id:datastore/your-datastore-id" ], "Condition": { "StringEquals": { "medical-imaging:SeriesInstanceUID": [ "123.456.789", "1.2.3.4.5.6" ] } } } ] } ``` ### Example 3: Granting access based on StudyInstanceUIDs and SeriesInstanceUIDs To grant access only to image sets of a particular DICOM Study and Series, attach a policy to the role that specifies conditions on both the `StudyInstanceUID` and `SeriesInstanceUID`. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "Statement1", "Effect": "Allow", "Action": [ "medical-imaging:SearchDICOMInstances" ], "Resource": [ "arn:aws:medical-imaging:us-west-2:account-id:datastore/your-datastore-id" ], "Condition": { "StringEquals": { "medical-imaging:StudyInstanceUID": ["123.456.789"], "medical-imaging:SeriesInstanceUID": ["1.2.3.4.5.6"] } } } ] } ``` # AWS managed policies for AWS HealthImaging AWS managed policies An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles. Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases. You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*. **Topics** + [ ## AWS managed policy: AWSHealthImagingServiceRolePolicy ](#security-iam-awsmanpol-AWSHealthImagingServiceRolePolicy) + [ ## AWS managed policy: AWSHealthImagingFullAccess ](#security-iam-awsmanpol-AWSHealthImagingFullAccess) + [ ## AWS managed policy: AWSHealthImagingReadOnlyAccess ](#security-iam-awsmanpol-AWSHealthImagingReadOnlyAccess) + [ ## HealthImaging updates to AWS managed policies ](#security-iam-awsmanpol-updates) ## AWS managed policy: AWSHealthImagingServiceRolePolicy AWSHealthImagingServiceRolePolicy This policy is attached to service-linked role `AWSServiceRoleForHealthImaging`. It grants permissions for HealthImaging to manage service operations and publish service metrics. For more information about this policy, including the JSON policy document, see [AWSHealthImagingServiceRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSHealthImagingServiceRolePolicy.html) in the *AWS Managed Policy Reference Guide*. ## AWS managed policy: AWSHealthImagingFullAccess AWSHealthImagingFullAccess You can attach the `AWSHealthImagingFullAccess` policy to your IAM identities. This policy grants administrative permission to all HealthImaging actions. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "medical-imaging:*" ], "Resource": "*" }, { "Effect": "Allow", "Action": "iam:PassRole", "Resource": "*", "Condition": { "StringEquals": { "iam:PassedToService": "medical-imaging.amazonaws.com" } } } ] } ``` ------ ## AWS managed policy: AWSHealthImagingReadOnlyAccess AWSHealthImagingReadOnlyAccess You can attach the `AWSHealthImagingReadOnlyAccess` policy to your IAM identities. This policy grants read-only permission to specific AWS HealthImaging actions. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "medical-imaging:GetDICOMImportJob", "medical-imaging:GetDatastore", "medical-imaging:GetImageFrame", "medical-imaging:GetImageSet", "medical-imaging:GetImageSetMetadata", "medical-imaging:ListDICOMImportJobs", "medical-imaging:ListDatastores", "medical-imaging:ListImageSetVersions", "medical-imaging:ListTagsForResource", "medical-imaging:SearchImageSets" ], "Resource": "*" }] } ``` ------ ## HealthImaging updates to AWS managed policies Policy updates View details about updates to AWS managed policies for HealthImaging since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the [Releases](releases.md) page. | Change | Description | Date | | --- | --- | --- | | AWSHealthImagingServiceRolePolicy | AWS HealthImaging added a new managed policy for the service-linked role that provides permissions for HealthImaging to manage service operations and publish service metrics. | February 9, 2026 | | HealthImaging started tracking changes | HealthImaging started tracking changes for its AWS managed policies. | July 19, 2023 | # Cross-service confused deputy prevention in HealthImaging Cross-service confused deputy prevention The confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the *calling service*) calls another service (the *called service*). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. We recommend using the [https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in your `ImportJobDataAccessRole` IAM role trust relationship policies to limit the permissions that AWS HealthImaging gives another service to your resource. Use `aws:SourceArn` to associate only one resource with cross-service access. Use `aws:SourceAccount` to let any resource in that account be associated with the cross-service use. If you use both global condition context keys, the `aws:SourceAccount` value and the account referenced in the `aws:SourceArn` value must use the same account ID when used in the same policy statement. The value of `aws:SourceArn` must be the ARN of the affected data store. If you don't know the full ARN of the data store, or if you are specifying multiple data stores, use the `aws:SourceArn` global context condition key with the \$1 wildcard for the unknown portions of the ARN. For example, you can set `aws:SourceArn` to `arn:aws:medical-imaging:us-west-2:111122223333:datastore/*`. In the following trust policy example, we use the `aws:SourceArn` and `aws:SourceAccount` condition key to restrict access to the service principal based on the data store's ARN to prevent the confused deputy problem. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "medical-imaging.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "ArnLike": { "aws:SourceArn": "arn:aws:medical-imaging:us-east-1:123456789012:datastore/*" }, "StringEquals": { "aws:SourceAccount": "123456789012" } } } ] } ``` ------ # Using service-linked roles for HealthImaging Using service-linked roles AWS HealthImaging uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role) that are predefined by the service and include all the permissions that the service requires to call other AWS services on your behalf. For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the IAM User Guide. ## Service-linked role permissions for HealthImaging HealthImaging uses the service-linked role named `AWSServiceRoleForHealthImaging` to perform operations in your AWS account. You need to create this service-linked role if you want HealthImaging to publish metrics about your data stores to CloudWatch. The role permissions policy named `AWSHealthImagingServiceRolePolicy` grants permissions for HealthImaging to manage service operations and publish service metrics. For managed policy updates, see [HealthImaging managed policies](https://docs.aws.amazon.com/healthimaging/latest/devguide/security-iam-awsmanpol.html#security-iam-awsmanpol-updates). ## Creating a service-linked role for HealthImaging **Create a service-linked role with the IAM Console** You can create a service-linked role using the IAM Console by Selecting `AWS Service` as the Trusted entity type, and then `HealthImaging` in the Use case drop down menu. **Create a service-linked role with the AWS CLI** In the AWS CLI, run `aws iam create-service-linked-role —aws-service-name medical-imaging.amazonaws.com` ## Deleting a service-linked role for HealthImaging You can delete a service-linked role at any time, but doing so will block HealthImaging from performing actions in your AWS account, such as publishing data store metrics to CloudWatch. **To manually delete the service-linked role using IAM** You can use the IAM console, the AWS CLI, or the AWS API to delete the `AWSServiceRoleForHealthImaging` service-linked role. For more information, see [Deleting a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*. If you deleted a service-linked role, you can use the role creation process to create a new one. # Troubleshooting AWS HealthImaging identity and access Troubleshooting Use the following information to help you diagnose and fix common issues that you might encounter when working with HealthImaging and IAM. **Topics** + [ ## I am not authorized to perform an action in HealthImaging ](#security_iam_troubleshoot-no-permissions) + [ ## I am not authorized to perform iam:PassRole ](#security_iam_troubleshoot-passrole) + [ ## I want to allow people outside of my AWS account to access my HealthImaging resources ](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in HealthImaging If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-example-widget` resource but doesn't have the fictional `AWS:GetWidget` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: AWS:GetWidget on resource: my-example-widget ``` In this case, the policy for the `mateojackson` user must be updated to allow access to the `my-example-widget` resource by using the `AWS:GetWidget` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to HealthImaging. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in HealthImaging. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. ``` User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole ``` In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I want to allow people outside of my AWS account to access my HealthImaging resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether HealthImaging supports these features, see [How AWS HealthImaging works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.