AWS managed policies for AWS HealthOmics

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 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 in the IAM User Guide.

AWS managed policy: AWSHealthOmicsServiceLinkedRolePolicy

This policy is attached to a service-linked role that allows HealthOmics to perform actions on your behalf. You can't attach AWSHealthOmicsServiceLinkedRolePolicy to your users, groups, or roles. For more information, see Using a service-linked role.

For more information about this policy, including the JSON policy document, see AWSHealthOmicsServiceLinkedRolePolicy in the AWS Managed Policy Reference Guide.

AWS managed policy: AmazonOmicsFullAccess

You can attach the AmazonOmicsFullAccess policy to your IAM identities to give them full access to HealthOmics.

This policy grants full access permissions to all HealthOmics actions. When you create an annotation or variant store, Omics will also give you access tothat store through a Resource Share Invitation in the Resource Access Manager (RAM) console. For more information on Resource Share invitations through Lake Formation, see the Cross-account data sharing in Lake Formation. For an Omics admin policy, you also need the following permissions to access your Amazon S3 bucket.

JSON

{
	"Version":"2012-10-17",		 	 	 
	"Statement": [
		{
			"Effect": "Allow",
			"Action": [
				"omics:*"
			],
			"Resource": "*"
		},
		{
			"Effect": "Allow",
			"Action": [
				"ram:AcceptResourceShareInvitation",
				"ram:GetResourceShareInvitations"
			],
			"Resource": "*",
			"Condition": {
				"StringEquals": {
					"aws:CalledViaLast": "omics.amazonaws.com"
				}
			}
		},
		{
			"Effect": "Allow",
			"Action": "iam:PassRole",
			"Resource": "*",
			"Condition": {
				"StringEquals": {
					"iam:PassedToService": "omics.amazonaws.com"
				}
			}
		}
	]
}
        

AWS managed policy: AmazonOmicsReadOnlyAccess

You can attach the AWSOmicsReadOnlyAccess policy to your IAM identities when you wish to limit the permissions for that identity to read-only access.

JSON

{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "omics:Get*",
                "omics:List*"
            ],
            "Resource": "*"
        }
    ]
}

HealthOmics updates to AWS managed policies

View details about updates to AWS managed policies for HealthOmics since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the HealthOmics Document history page.