Skip to main content
IAM Policy Map

AmazonBioDiscoveryFullAccess

OperatorAWS managedActiveReviewedShow on mapCompare

Summary

Allows full administrative access to Amazon Bio Discovery. The policy also includes related permissions for IAM Identity Center and the identity store, EC2 networking, S3 and AWS KMS.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess
Default version
v2
Created
Last edited
Services
ec2, iam, identitystore, kms, researchstudio, s3, sso

Control-plane actions (40)

By access level: 13 List, 10 Read, 17 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
EC23 of 8343 List; 0 restricted, 0 conditionalec2:DescribeSecurityGroups, ec2:DescribeSubnets, ec2:DescribeVpcs
IAM2 of 1902 Write; 2 restricted, 2 conditionaliam:CreateServiceLinkedRole, iam:PassRole
Identity Store5 of 293 List, 2 Read; 5 restricted, 0 conditionalidentitystore:DescribeGroup, identitystore:DescribeUser, identitystore:ListGroupMembershipsForMember, identitystore:ListGroups, identitystore:ListUsers
KMS1 of 581 Write; 1 restricted, 1 conditionalkms:Decrypt
Bio DiscoveryAll 6 actions (see the Bio Discovery page)1 List, 1 Read, 4 Write; 0 restricted, 0 conditionalresearchstudio:*
S32 of 1551 List, 1 Read; 2 restricted, 2 conditionals3:GetEncryptionConfiguration, s3:ListAllMyBuckets
IAM Identity Center21 of 1265 List, 6 Read, 10 Write; 21 restricted, 0 conditionalsso:CreateApplication, sso:CreateApplicationAssignment, sso:DeleteApplication, sso:DeleteApplicationAccessScope, sso:DeleteApplicationAssignment, sso:DeleteApplicationAuthenticationMethod, sso:DeleteApplicationGrant, sso:DescribeApplication, sso:DescribeApplicationAssignment, sso:DescribeInstance, sso:DescribeRegisteredRegions, sso:GetApplicationAuthenticationMethod and 9 more
EC2: 3 actions
  • ec2:DescribeSecurityGroups (List)
  • ec2:DescribeSubnets (List)
  • ec2:DescribeVpcs (List)
IAM: 2 actions
  • iam:CreateServiceLinkedRole (Write)
  • iam:PassRole (Write)
Identity Store: 5 actions
  • identitystore:DescribeGroup (Read)
  • identitystore:DescribeUser (Read)
  • identitystore:ListGroupMembershipsForMember (List)
  • identitystore:ListGroups (List)
  • identitystore:ListUsers (List)
KMS: 1 actions
  • kms:Decrypt (Write)
S3: 2 actions
  • s3:GetEncryptionConfiguration (Read)
  • s3:ListAllMyBuckets (List)
IAM Identity Center: 21 actions
  • sso:CreateApplication (Write)
  • sso:CreateApplicationAssignment (Write)
  • sso:DeleteApplication (Write)
  • sso:DeleteApplicationAccessScope (Write)
  • sso:DeleteApplicationAssignment (Write)
  • sso:DeleteApplicationAuthenticationMethod (Write)
  • sso:DeleteApplicationGrant (Write)
  • sso:DescribeApplication (Read)
  • sso:DescribeApplicationAssignment (Read)
  • sso:DescribeInstance (Read)
  • sso:DescribeRegisteredRegions (Read)
  • sso:GetApplicationAuthenticationMethod (Read)
  • sso:GetApplicationGrant (Read)
  • sso:ListApplicationAccessScopes (List)
  • sso:ListApplicationAssignments (List)
  • sso:ListApplicationGrants (List)
  • sso:ListApplications (List)
  • sso:ListInstances (List)
  • sso:PutApplicationAccessScope (Write)
  • sso:PutApplicationAuthenticationMethod (Write)
  • sso:PutApplicationGrant (Write)

Data-plane actions (1)

By access level: 1 List.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
S31 of 251 List; 1 restricted, 1 conditionals3:ListBucket
S3: 1 actions
  • s3:ListBucket (List)

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants 17 write, tagging or permissions-management actions, short of full control of any service.
  • Grants iam:PassRole, but only for scoped roles or under conditions (for example iam:PassedToService).

Guidance

Practical scope

10 statements, all Allow. AmazonBioDiscoveryFullAccess allows researchstudio:* on Resource "*". Other statements allow 21 sso actions (application creation, assignment, grants, authentication methods and access scopes) on instance and application ARNs, 5 identitystore read actions, iam:PassRole, iam:CreateServiceLinkedRole, three EC2 describe actions (ec2:DescribeVpcs, ec2:DescribeSubnets, ec2:DescribeSecurityGroups), s3:ListAllMyBuckets, s3:ListBucket and s3:GetEncryptionConfiguration, and two kms:Decrypt statements with conditions.

Use cases

  • Give administrators full administrative access to Amazon Bio Discovery.

Best practices

  • AWS managed policies don't grant least privilege permissions. The IAM User Guide says to consider the security risk of granting principals more permissions than they need, and suggests using Access Analyzer to see which permissions principals use, then writing a custom policy or generating one with only the required permissions.

Security considerations

  • researchstudio:* on Resource "*" allows every Amazon Bio Discovery action, not only reads.
  • It includes IAM Identity Center write actions on application resources, such as sso:CreateApplication, sso:DeleteApplication, sso:CreateApplicationAssignment, sso:PutApplicationGrant and sso:PutApplicationAuthenticationMethod.
  • iam:PassRole is allowed on arn:aws:iam::*:role/* with a StringEquals condition on iam:PassedToService (researchstudio.amazonaws.com). The IAM User Guide warns that a passed role can have more permissions than the person passing it.
  • It allows iam:CreateServiceLinkedRole on arn:aws:iam::*:role/aws-service-role/researchstudio.amazonaws.com/AWSServiceRoleForAmazonBioDiscovery, and s3:ListBucket and s3:GetEncryptionConfiguration on arn:aws:s3:::* with a StringEquals condition on aws:ResourceAccount (${aws:PrincipalAccount}).
  • You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.

Assignment guidance

You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full administrative access to Amazon Bio Discovery is intended.

Same service

Same domain

Frequently asked questions

When should I attach AmazonBioDiscoveryFullAccess?
The reference page says you can attach AmazonBioDiscoveryFullAccess to your users, groups and roles, and describes it as: allows full administrative access to Amazon Bio Discovery. Attach it where administering Amazon Bio Discovery is the intended scope.
What does AmazonBioDiscoveryFullAccess grant?
It allows researchstudio:* on all resources, 21 IAM Identity Center sso actions on application ARNs, identitystore read actions, iam:PassRole to researchstudio.amazonaws.com, creation of the Amazon Bio Discovery service-linked role, EC2 describe actions, S3 bucket listing and encryption configuration reads, and kms:Decrypt through IAM Identity Center and the identity store.
What are the security risks of AmazonBioDiscoveryFullAccess?
researchstudio:* allows every Bio Discovery action, it can create and delete IAM Identity Center applications, and it can pass roles to the service. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AmazonBioDiscoveryFullAccess",
      "Effect": "Allow",
      "Action": [
        "researchstudio:*"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AmazonBioDiscoveryPassRoleAccess",
      "Effect": "Allow",
      "Action": [
        "iam:PassRole"
      ],
      "Resource": "arn:aws:iam::*:role/*",
      "Condition": {
        "StringEquals": {
          "iam:PassedToService": "researchstudio.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AmazonBioDiscoveryIdentityStoreAccess",
      "Effect": "Allow",
      "Action": [
        "identitystore:ListGroupMembershipsForMember",
        "identitystore:ListGroups",
        "identitystore:ListUsers",
        "identitystore:DescribeGroup",
        "identitystore:DescribeUser"
      ],
      "Resource": [
        "arn:aws:identitystore::*:identitystore/*",
        "arn:aws:identitystore:::user/*",
        "arn:aws:identitystore:::group/*",
        "arn:aws:identitystore:::membership/*"
      ]
    },
    {
      "Sid": "AmazonBioDiscoveryIdentityCenterAccess",
      "Effect": "Allow",
      "Action": [
        "sso:CreateApplication",
        "sso:CreateApplicationAssignment",
        "sso:DeleteApplication",
        "sso:DeleteApplicationAuthenticationMethod",
        "sso:DeleteApplicationGrant",
        "sso:DescribeApplication",
        "sso:DescribeApplicationAssignment",
        "sso:GetApplicationAuthenticationMethod",
        "sso:GetApplicationGrant",
        "sso:PutApplicationAuthenticationMethod",
        "sso:PutApplicationGrant",
        "sso:DeleteApplicationAssignment",
        "sso:DescribeInstance",
        "sso:ListInstances",
        "sso:ListApplications",
        "sso:ListApplicationAssignments",
        "sso:ListApplicationGrants",
        "sso:PutApplicationAccessScope",
        "sso:DeleteApplicationAccessScope",
        "sso:ListApplicationAccessScopes",
        "sso:DescribeRegisteredRegions"
      ],
      "Resource": [
        "arn:aws:sso:::instance/*",
        "arn:aws:sso::*:application/*/*",
        "arn:aws:sso::aws:applicationProvider/ResearchStudio"
      ]
    },
    {
      "Sid": "AmazonBioDiscoveryIdentityCenterKMSAccess",
      "Effect": "Allow",
      "Action": [
        "kms:Decrypt"
      ],
      "Resource": "*",
      "Condition": {
        "ArnLike": {
          "kms:EncryptionContext:aws:sso:instance-arn": "arn:aws:sso:::instance/*"
        },
        "StringLike": {
          "kms:ViaService": "sso.*.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AmazonBioDiscoveryIdentityStoreKMSAccess",
      "Effect": "Allow",
      "Action": [
        "kms:Decrypt"
      ],
      "Resource": "*",
      "Condition": {
        "ArnLike": {
          "kms:EncryptionContext:aws:identitystore:identitystore-arn": "arn:aws:identitystore::*:identitystore/*"
        },
        "StringLike": {
          "kms:ViaService": "identitystore.*.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AllowCreateAmazonBioDiscoveryServiceLinkedRole",
      "Effect": "Allow",
      "Action": "iam:CreateServiceLinkedRole",
      "Resource": "arn:aws:iam::*:role/aws-service-role/researchstudio.amazonaws.com/AWSServiceRoleForAmazonBioDiscovery",
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": "researchstudio.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AmazonBioDiscoveryVpcDescribeAccess",
      "Effect": "Allow",
      "Action": [
        "ec2:DescribeVpcs",
        "ec2:DescribeSubnets",
        "ec2:DescribeSecurityGroups"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AmazonBioDiscoveryS3ListBucketsAccess",
      "Effect": "Allow",
      "Action": "s3:ListAllMyBuckets",
      "Resource": "*",
      "Condition": {
        "StringEquals": {
          "s3:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Sid": "AmazonBioDiscoveryS3BucketReadAccess",
      "Effect": "Allow",
      "Action": [
        "s3:ListBucket",
        "s3:GetEncryptionConfiguration"
      ],
      "Resource": "arn:aws:s3:::*",
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    }
  ]
}

Version history

Current version v2, edited by AWS on 2026-11-06. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "amazonbiodiscoveryfullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonBioDiscoveryFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonBioDiscoveryFullAccess"),
);

Sources