AWSDirectoryServiceFullAccess
Summary
Provides full access to AWS Directory Service. The Directory Service Administration Guide says principals can create, configure and manage directories, including Simple AD, AD Connector and Managed Microsoft AD.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AWSDirectoryServiceFullAccess- Default version
- v6
- Created
- Last edited
- Services
- ds, ec2, iam, organizations, sns
Control-plane actions (124)
By access level: 17 List, 2 Permissions management, 28 Read, 4 Tagging, 73 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Directory Service | All 91 actions (see the Directory Service page) | 4 List, 1 Permissions management, 25 Read, 2 Tagging, 59 Write; 0 restricted, 0 conditional | ds:* |
| EC2 | 14 of 834 | 4 List, 2 Tagging, 8 Write; 2 restricted, 0 conditional | ec2:AuthorizeSecurityGroupEgress, ec2:AuthorizeSecurityGroupIngress, ec2:CreateNetworkInterface, ec2:CreateSecurityGroup, ec2:CreateTags, ec2:DeleteNetworkInterface, ec2:DeleteSecurityGroup, ec2:DeleteTags, ec2:DescribeNetworkInterfaces, ec2:DescribeSecurityGroups, ec2:DescribeSubnets, ec2:DescribeVpcs and 2 more |
| IAM | 1 of 190 | 1 List; 0 restricted, 0 conditional | iam:ListRoles |
| Organizations | 9 of 63 | 5 List, 2 Read, 2 Write; 2 restricted, 2 conditional | organizations:DescribeAccount, organizations:DescribeOrganization, organizations:DisableAWSServiceAccess, organizations:EnableAWSServiceAccess, organizations:ListAWSServiceAccessForOrganization, organizations:ListAccounts, organizations:ListAccountsForParent, organizations:ListOrganizationalUnitsForParent, organizations:ListRoots |
| SNS | 9 of 40 | 3 List, 1 Permissions management, 1 Read, 4 Write; 5 restricted, 0 conditional | sns:CreateTopic, sns:DeleteTopic, sns:GetTopicAttributes, sns:ListSubscriptions, sns:ListSubscriptionsByTopic, sns:ListTopics, sns:SetTopicAttributes, sns:Subscribe, sns:Unsubscribe |
EC2: 14 actions
- ec2:AuthorizeSecurityGroupEgress (Write)
- ec2:AuthorizeSecurityGroupIngress (Write)
- ec2:CreateNetworkInterface (Write)
- ec2:CreateSecurityGroup (Write)
- ec2:CreateTags (Tagging)
- ec2:DeleteNetworkInterface (Write)
- ec2:DeleteSecurityGroup (Write)
- ec2:DeleteTags (Tagging)
- ec2:DescribeNetworkInterfaces (List)
- ec2:DescribeSecurityGroups (List)
- ec2:DescribeSubnets (List)
- ec2:DescribeVpcs (List)
- ec2:RevokeSecurityGroupEgress (Write)
- ec2:RevokeSecurityGroupIngress (Write)
IAM: 1 actions
- iam:ListRoles (List)
Organizations: 9 actions
- organizations:DescribeAccount (Read)
- organizations:DescribeOrganization (Read)
- organizations:DisableAWSServiceAccess (Write)
- organizations:EnableAWSServiceAccess (Write)
- organizations:ListAWSServiceAccessForOrganization (List)
- organizations:ListAccounts (List)
- organizations:ListAccountsForParent (List)
- organizations:ListOrganizationalUnitsForParent (List)
- organizations:ListRoots (List)
SNS: 9 actions
- sns:CreateTopic (Write)
- sns:DeleteTopic (Write)
- sns:GetTopicAttributes (Read)
- sns:ListSubscriptions (List)
- sns:ListSubscriptionsByTopic (List)
- sns:ListTopics (List)
- sns:SetTopicAttributes (Permissions management)
- sns:Subscribe (Write)
- sns:Unsubscribe (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 at least 80% of the write and permissions-management actions of: ds (60 of 60).
Guidance
Practical scope
The first statement, DirectoryServiceFullAccess, allows ds:* plus listed actions for EC2 (network interfaces, security groups, subnets and VPCs), SNS (topic and subscription reads), iam:ListRoles and AWS Organizations (list and describe actions) on Resource "*". DirectoryServiceEventTopic allows sns:CreateTopic, sns:DeleteTopic, sns:SetTopicAttributes, sns:Subscribe and sns:Unsubscribe on topics named DirectoryMonitoring*. DirectoryServiceOrganizations allows organizations:EnableAWSServiceAccess and organizations:DisableAWSServiceAccess only when organizations:ServicePrincipal is ds.amazonaws.com. DirectoryServiceTags allows ec2:CreateTags and ec2:DeleteTags on network interfaces and security groups.
Use cases
- Give administrators full access to AWS Directory Service, including the network resources that directories need.
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
- ds:* allows every Directory Service action on all resources. The Directory Service Administration Guide says this includes managing directory sharing, trust relationships and monitoring configurations.
- The EC2 actions on Resource "*" include ec2:AuthorizeSecurityGroupIngress, ec2:AuthorizeSecurityGroupEgress, ec2:RevokeSecurityGroupIngress, ec2:CreateSecurityGroup, ec2:DeleteSecurityGroup and ec2:DeleteNetworkInterface.
- The policy can enable and disable AWS service access for Directory Service in AWS Organizations (organizations:EnableAWSServiceAccess and organizations:DisableAWSServiceAccess).
- 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 Directory Service Administration Guide says you can attach it to your IAM identities. It fits where full administrative access to Directory Service is intended.
Related policies
Same service
- AdministratorAccess-AWSElasticBeanstalk
- AIDevOpsReleaseManagementVPCPolicy
- AmazonAppStreamServiceAccess
- AmazonBioDiscoveryServiceLinkedRolePolicy
- AmazonDataZoneEnvironmentRolePermissionsBoundary
- AmazonDataZoneProjectDeploymentPermissionsBoundary
- AmazonDataZoneProjectRolePermissionsBoundary
- AmazonDataZoneSageMakerProvisioningRolePolicy
Same domain
Frequently asked questions
- When should I attach AWSDirectoryServiceFullAccess?
- The Directory Service Administration Guide says you can attach it to your IAM identities, and that it grants administrative permissions with full access to all Directory Service actions. Attach it where that administrative scope is intended.
- What does AWSDirectoryServiceFullAccess grant?
- It allows ds:*, EC2 network and security group actions, SNS topic reads, iam:ListRoles and Organizations list and describe actions on all resources, SNS topic management for topics named DirectoryMonitoring*, enabling and disabling Directory Service access in Organizations, and tagging of network interfaces and security groups.
- What are the security risks of AWSDirectoryServiceFullAccess?
- ds:* covers every Directory Service action on all resources, the EC2 actions let a principal change security group rules, and the Organizations statement can enable or disable service access. 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
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DirectoryServiceFullAccess",
"Effect": "Allow",
"Action": [
"ds:*",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:CreateNetworkInterface",
"ec2:CreateSecurityGroup",
"ec2:DeleteNetworkInterface",
"ec2:DeleteSecurityGroup",
"ec2:DescribeNetworkInterfaces",
"ec2:DescribeSubnets",
"ec2:DescribeVpcs",
"ec2:RevokeSecurityGroupEgress",
"ec2:RevokeSecurityGroupIngress",
"ec2:DescribeSecurityGroups",
"sns:GetTopicAttributes",
"sns:ListSubscriptions",
"sns:ListSubscriptionsByTopic",
"sns:ListTopics",
"iam:ListRoles",
"organizations:ListAccountsForParent",
"organizations:ListRoots",
"organizations:ListAccounts",
"organizations:DescribeOrganization",
"organizations:DescribeAccount",
"organizations:ListOrganizationalUnitsForParent",
"organizations:ListAWSServiceAccessForOrganization"
],
"Resource": "*"
},
{
"Sid": "DirectoryServiceEventTopic",
"Effect": "Allow",
"Action": [
"sns:CreateTopic",
"sns:DeleteTopic",
"sns:SetTopicAttributes",
"sns:Subscribe",
"sns:Unsubscribe"
],
"Resource": "arn:aws:sns:*:*:DirectoryMonitoring*"
},
{
"Sid": "DirectoryServiceOrganizations",
"Effect": "Allow",
"Action": [
"organizations:EnableAWSServiceAccess",
"organizations:DisableAWSServiceAccess"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"organizations:ServicePrincipal": "ds.amazonaws.com"
}
}
},
{
"Sid": "DirectoryServiceTags",
"Effect": "Allow",
"Action": [
"ec2:CreateTags",
"ec2:DeleteTags"
],
"Resource": [
"arn:aws:ec2:*:*:network-interface/*",
"arn:aws:ec2:*:*:security-group/*"
]
}
]
}
Version history
Current version v6, edited by AWS on 2024-04-02. 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/AWSDirectoryServiceFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSDirectoryServiceFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSDirectoryServiceFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWSDirectoryServiceFullAccessTerraform
resource "aws_iam_role_policy_attachment" "awsdirectoryservicefullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWSDirectoryServiceFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWSDirectoryServiceFullAccess"),
);Sources
- AWSDirectoryServiceFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for AWS Directory Service (retrieved ; supports summary, useCases, securityConsiderations, assignmentGuidance, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)