Skip to main content
IAM Policy Map

AmazonODBExadataVmClusterAdmin

OperatorJob functionActiveReviewedShow on mapCompare

Summary

Provides administrative access to manage Exadata VM cluster resources in Oracle Database@AWS. The Oracle Database@AWS User Guide says you can manage Exadata VM cluster resources and their DB nodes, and view the Exadata infrastructure and ODB network resources they depend on.

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

Identity

ARN
arn:aws:iam::aws:policy/job-function/AmazonODBExadataVmClusterAdmin
Default version
v1
Created
Last edited
Services
ec2, odb

Control-plane actions (32)

By access level: 10 List, 8 Read, 2 Tagging, 12 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
EC21 of 8341 List; 0 restricted, 0 conditionalec2:DescribeAvailabilityZones
Oracle Database@AWS31 of 969 List, 8 Read, 2 Tagging, 12 Write; 4 restricted, 0 conditionalodb:AssociateIamRoleToResource, odb:CreateCloudVmCluster, odb:CreateDbNode, odb:CreateOutboundIntegration, odb:DeleteCloudVmCluster, odb:DeleteDbNode, odb:DisassociateIamRoleFromResource, odb:GetCloudExadataInfrastructure, odb:GetCloudExadataInfrastructureUnallocatedResources, odb:GetCloudVmCluster, odb:GetDbNode, odb:GetDbServer and 19 more
EC2: 1 actions
  • ec2:DescribeAvailabilityZones (List)
Oracle Database@AWS: 31 actions
  • odb:AssociateIamRoleToResource (Write)
  • odb:CreateCloudVmCluster (Write)
  • odb:CreateDbNode (Write)
  • odb:CreateOutboundIntegration (Write)
  • odb:DeleteCloudVmCluster (Write)
  • odb:DeleteDbNode (Write)
  • odb:DisassociateIamRoleFromResource (Write)
  • odb:GetCloudExadataInfrastructure (Read)
  • odb:GetCloudExadataInfrastructureUnallocatedResources (Read)
  • odb:GetCloudVmCluster (Read)
  • odb:GetDbNode (Read)
  • odb:GetDbServer (Read)
  • odb:GetOciOnboardingStatus (Read)
  • odb:GetOdbNetwork (Read)
  • odb:InitializeService (Write)
  • odb:ListCloudExadataInfrastructures (List)
  • odb:ListCloudVmClusters (List)
  • odb:ListDbNodes (List)
  • odb:ListDbServers (List)
  • odb:ListDbSystemShapes (List)
  • odb:ListFlexComponents (List)
  • odb:ListGiVersions (List)
  • odb:ListOdbNetworks (List)
  • odb:ListSystemVersions (List)
  • odb:ListTagsForResource (Read)
  • odb:RebootDbNode (Write)
  • odb:StartDbNode (Write)
  • odb:StopDbNode (Write)
  • odb:TagResource (Tagging)
  • odb:UntagResource (Tagging)
  • odb:UpdateOutboundIntegration (Write)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

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 14 write, tagging or permissions-management actions, short of full control of any service.

Guidance

Practical scope

AllowODBActions allows odb actions on Resource "*", including odb:CreateCloudVmCluster, odb:GetCloudVmCluster, odb:DeleteCloudVmCluster, odb:ListCloudVmClusters, odb:AssociateIamRoleToResource, odb:DisassociateIamRoleFromResource, odb:CreateDbNode, odb:RebootDbNode, odb:StartDbNode, odb:StopDbNode, odb:DeleteDbNode, odb:InitializeService and read actions for Exadata infrastructure, DB servers, ODB networks, system shapes and versions. AllowEC2Actions allows ec2:DescribeAvailabilityZones. Tagging is limited to cloud-vm-cluster and db-node resources, and outbound integration actions to cloud-vm-cluster resources. The policy has no service-linked role statement.

Use cases

  • Let an administrator create, view, delete and list Exadata VM clusters, and create, start, stop, reboot and delete their DB nodes, in Oracle Database@AWS.

Prerequisites

  • The policy lacks iam:PassRole. The Oracle Database@AWS User Guide says to add it through your own customer managed policy, scoped to the role ARNs you choose and constrained with iam:PassedToService set to odb.amazonaws.com. Without it, requests to associate an IAM role with an Exadata VM cluster fail. Disassociating a role does not need it.

Best practices

  • AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.

Security considerations

  • The policy allows odb:DeleteCloudVmCluster, odb:DeleteDbNode, odb:StopDbNode and odb:RebootDbNode on Resource "*".
  • The policy has no iam:PassRole. If you add it as the guide describes, scope it to role ARNs you choose, because the IAM User Guide says to make sure a user cannot pass a role that has more permissions than you want the user to have.
  • 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. The Oracle Database@AWS User Guide says you can attach it to your IAM identities. It fits administrators who manage Exadata VM clusters and DB nodes.

Same service

Same domain

Frequently asked questions

When should I attach AmazonODBExadataVmClusterAdmin?
The Oracle Database@AWS User Guide says you can attach it to your IAM identities to manage Exadata VM cluster resources and their DB nodes. Add iam:PassRole through a customer managed policy if you need to associate IAM roles.
What does AmazonODBExadataVmClusterAdmin grant?
On all resources it allows odb actions to create, view, delete and list Exadata VM clusters, associate and disassociate IAM roles, create, start, stop, reboot and delete DB nodes, and read infrastructure, network and version information. It also allows ec2:DescribeAvailabilityZones, tagging actions on VM cluster and DB node resources, and outbound integration actions on VM cluster resources only.
What are the security risks of AmazonODBExadataVmClusterAdmin?
It can delete Exadata VM clusters and DB nodes, and stop or reboot DB nodes, on all resources. It does not include iam:PassRole. AWS managed policies don't grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowODBActions",
      "Effect": "Allow",
      "Action": [
        "odb:GetOciOnboardingStatus",
        "odb:InitializeService",
        "odb:GetCloudExadataInfrastructure",
        "odb:GetCloudExadataInfrastructureUnallocatedResources",
        "odb:ListCloudExadataInfrastructures",
        "odb:CreateCloudVmCluster",
        "odb:GetCloudVmCluster",
        "odb:DeleteCloudVmCluster",
        "odb:ListCloudVmClusters",
        "odb:AssociateIamRoleToResource",
        "odb:DisassociateIamRoleFromResource",
        "odb:CreateDbNode",
        "odb:GetDbNode",
        "odb:RebootDbNode",
        "odb:StartDbNode",
        "odb:StopDbNode",
        "odb:DeleteDbNode",
        "odb:ListDbNodes",
        "odb:GetDbServer",
        "odb:ListDbServers",
        "odb:GetOdbNetwork",
        "odb:ListOdbNetworks",
        "odb:ListDbSystemShapes",
        "odb:ListFlexComponents",
        "odb:ListGiVersions",
        "odb:ListSystemVersions",
        "odb:ListTagsForResource"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AllowEC2Actions",
      "Effect": "Allow",
      "Action": [
        "ec2:DescribeAvailabilityZones"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AllowTaggingActions",
      "Effect": "Allow",
      "Action": [
        "odb:TagResource",
        "odb:UntagResource"
      ],
      "Resource": [
        "arn:aws:odb:*:*:cloud-vm-cluster/*",
        "arn:aws:odb:*:*:db-node/*"
      ]
    },
    {
      "Sid": "AllowOutboundIntegrationActions",
      "Effect": "Allow",
      "Action": [
        "odb:CreateOutboundIntegration",
        "odb:UpdateOutboundIntegration"
      ],
      "Resource": [
        "arn:aws:odb:*:*:cloud-vm-cluster/*"
      ]
    }
  ]
}

Version history

Current version v1, edited by AWS on 2026-09-04. 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/job-function/AmazonODBExadataVmClusterAdmin
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/job-function/AmazonODBExadataVmClusterAdmin
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/job-function/AmazonODBExadataVmClusterAdmin

CloudFormation

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

Terraform

resource "aws_iam_role_policy_attachment" "job_function_amazonodbexadatavmclusteradmin" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/job-function/AmazonODBExadataVmClusterAdmin"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("job-function/AmazonODBExadataVmClusterAdmin"),
);

Sources