AWSSystemsManagerForSAPFullAccess

OperatorAWS managedActivePermissions reviewedShow on map Compare

Summary

Provides full access to AWS Systems Manager for SAP service

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

Identity

ARN: arn:aws:iam::aws:policy/AWSSystemsManagerForSAPFullAccess
Default version: v3
Created: 2022-11-17
Last edited: 2024-07-10
Services: ec2, iam, ssm-sap

Control-plane actions (33)

By access level: 9 List, 3 Permissions management, 6 Read, 2 Tagging, 13 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
EC2	2 of 834	2 Write; 2 restricted, 2 conditional	ec2:StartInstances, ec2:StopInstances
IAM	1 of 190	1 Write; 1 restricted, 1 conditional	iam:CreateServiceLinkedRole
Systems Manager for SAP	All 30 actions (see the Systems Manager for SAP page)	9 List, 3 Permissions management, 6 Read, 2 Tagging, 10 Write; 30 restricted, 0 conditional	ssm-sap:*

EC2: 2 actions

ec2:StartInstances (Write)
ec2:StopInstances (Write)

IAM: 1 actions

iam:CreateServiceLinkedRole (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: scoped.

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

Why this tier

Grants 18 write, tagging or permissions-management actions, 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

AWSSystemsManagerForSAPReadOnlyAccess

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": [
    {
      "Sid": "AwsSsmForSapPermissions",
      "Effect": "Allow",
      "Action": [
        "ssm-sap:*"
      ],
      "Resource": "arn:*:ssm-sap:*:*:*"
    },
    {
      "Sid": "AwsSsmForSapServiceRoleCreationPermission",
      "Effect": "Allow",
      "Action": [
        "iam:CreateServiceLinkedRole"
      ],
      "Resource": [
        "arn:aws:iam::*:role/aws-service-role/ssm-sap.amazonaws.com/AWSServiceRoleForAWSSSMForSAP"
      ],
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": "ssm-sap.amazonaws.com"
        }
      }
    },
    {
      "Sid": "Ec2StartStopPermission",
      "Effect": "Allow",
      "Action": [
        "ec2:StartInstances",
        "ec2:StopInstances"
      ],
      "Resource": "arn:aws:ec2:*:*:instance/*",
      "Condition": {
        "StringEqualsIgnoreCase": {
          "ec2:resourceTag/SSMForSAPManaged": "True"
        }
      }
    }
  ]
}

Version history

Current version v3, edited by AWS on 2024-07-10. 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/AWSSystemsManagerForSAPFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSSystemsManagerForSAPFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSSystemsManagerForSAPFullAccess

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources

Pending editorial review. No editorial sources are listed yet.