Skip to main content
IAM Policy Map

ROSAIngressOperatorPolicy

OperatorService roleActivePermissions reviewedShow on mapCompare

Summary

Allows the OpenShift Ingress Operator to provision and manage load balancers and domain name system (DNS) configurations for Red Hat OpenShift Service on AWS (ROSA) clusters. The policy allows read access to tag values, which the operator filters for Route 53 resources to discover hosted zones.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN
arn:aws:iam::aws:policy/service-role/ROSAIngressOperatorPolicy
Default version
v4
Created
Last edited
Services
elasticloadbalancing, route53, tag

Control-plane actions (4)

By access level: 2 List, 1 Read, 1 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
ELB1 of 771 List; 0 restricted, 0 conditionalelasticloadbalancing:DescribeLoadBalancers
Route 532 of 711 List, 1 Write; 1 restricted, 1 conditionalroute53:ChangeResourceRecordSets, route53:ListHostedZones
Resource Group Tagging1 of 91 Read; 0 restricted, 0 conditionaltag:GetResources
ELB: 1 actions
  • elasticloadbalancing:DescribeLoadBalancers (List)
Route 53: 2 actions
  • route53:ChangeResourceRecordSets (Write)
  • route53:ListHostedZones (List)
Resource Group Tagging: 1 actions
  • tag:GetResources (Read)

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: all-resources.

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

Why this tier

  • Grants 1 write, tagging or permissions-management action, short of full control of any service.

Guidance

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Same service

Same domain

Frequently asked questions

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "elasticloadbalancing:DescribeLoadBalancers",
        "route53:ListHostedZones",
        "tag:GetResources"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "route53:ChangeResourceRecordSets"
      ],
      "Resource": "*",
      "Condition": {
        "ForAllValues:StringLike": {
          "route53:ChangeResourceRecordSetsNormalizedRecordNames": [
            "*.openshiftapps.com",
            "*.devshift.org",
            "*.openshiftusgov.com",
            "*.devshiftusgov.com"
          ]
        }
      }
    }
  ]
}

Version history

Current version v4, edited by AWS on 2026-02-12. 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/service-role/ROSAIngressOperatorPolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/service-role/ROSAIngressOperatorPolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/service-role/ROSAIngressOperatorPolicy

CloudFormation

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

Terraform

resource "aws_iam_role_policy_attachment" "service_role_rosaingressoperatorpolicy" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/service-role/ROSAIngressOperatorPolicy"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("service-role/ROSAIngressOperatorPolicy"),
);

Sources

Pending editorial review. No editorial sources are listed yet.