AWS managed policies for Amazon Detective - Amazon Detective

AWS managed policies for Amazon Detective

To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself. It takes time and expertise to create IAM customer managed policies that provide your team with only the permissions they need. To get started quickly, you can use our AWS managed policies. These policies cover common use cases and are available in your AWS account. For more information about AWS managed policies, see AWS managed policies in the IAM User Guide.

AWS services maintain and update AWS managed policies. You can't change the permissions in AWS managed policies. Services occasionally add additional permissions to an AWS managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions.

Additionally, AWS supports managed policies for job functions that span multiple services. For example, the ViewOnlyAccess AWS managed policy provides read-only access to many AWS services and resources. When a service launches a new feature, AWS adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see AWS managed policies for job functions in the IAM User Guide.

AWS managed policy: AmazonDetectiveFullAccess

You can attach the AmazonDetectiveFullAccess policy to your IAM identities.

This policy grants administrative permissions that allow a principal full access to all Amazon Detective actions. You can attach this policy to a principal before they enable Detective for their account. It must also be attached to the role that is used to run the Detective Python scripts to create and manage a behavior graph.

Principals with these permissions can manage member accounts, add tags to their behavior graph, and use Detective for investigation. They can also archive GuardDuty findings. The policy provides permissions that the Detective console needs to display account names for accounts that are in AWS Organizations.

Permissions details

This policy includes the following permissions:

  • detective – Allows principals full access to all Detective actions.

  • organizations – Allows principals to retrieve from AWS Organizations information about the accounts in an organization. If an account belongs to an organization, these permissions allow the Detective console to display account names in addition to account numbers.

  • guardduty – Allows principals to get and archive GuardDuty findings from within Detective.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "detective:*", "organizations:DescribeOrganization", "organizations:ListAccounts" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "guardduty:ArchiveFindings" ], "Resource": "arn:aws:guardduty:*:*:detector/*" }, { "Effect": "Allow", "Action": [ "guardduty:GetFindings", "guardduty:ListDetectors" ], "Resource": "*" } ] }

AWS managed policy: AmazonDetectiveMemberAccess

You can attach the AmazonDetectiveMemberAccess policy to your IAM entities.

This policy provides member access to Amazon Detective and scoped access to the console UI dependencies.

With this policy, you can:

  • View invitations to Detective graph membership and accept or reject those invitations.

  • View how your activity in Detective contributes to the cost of using this service on the Usage page.

  • Resign from your membership in a graph.

This policy grants read-only permissions that allow scoped access to the Detective
 console UI dependencies.

Permissions details

This policy includes the following permissions:

  • detective – Allows member access to Detective.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "detective:AcceptInvitation", "detective:BatchGetMembershipDatasources", "detective:DisassociateMembership", "detective:GetFreeTrialEligibility", "detective:GetPricingInformation", "detective:GetUsageInformation", "detective:ListInvitations", "detective:RejectInvitation" ], "Resource": "*" } ] }

AWS managed policy: AmazonDetectiveInvestigatorAccess

You can attach the AmazonDetectiveInvestigatorAccess policy to your IAM entities.

This policy provides investigator access to the Detective service and scoped access to the Detective console UI dependencies. The policy also grants permissions to investigate in Detective to determine and root cause findings and suspicious activity.

Permissions details

This policy includes the following permissions:

  • detective – Allows principals investigator access to all Detective actions.

  • guardduty – Allows principals to get and archive GuardDuty findings from within Detective.

  • organizations – Allows principals to retrieve information about the accounts in an organization from AWS Organizations. If an account belongs to an organization, then these permissions allow the Detective console to display account names in addition to account numbers.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "detective:BatchGetGraphMemberDatasources", "detective:BatchGetMembershipDatasources", "detective:DescribeOrganizationConfiguration", "detective:GetFreeTrialEligibility", "detective:GetGraphIngestState", "detective:GetMembers", "detective:GetPricingInformation", "detective:GetUsageInformation", "detective:ListDatasourcePackages", "detective:ListGraphs", "detective:ListHighDegreeEntities", "detective:ListInvitations", "detective:ListMembers", "detective:ListOrganizationAdminAccount", "detective:ListTagsForResource", "detective:SearchGraph" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "organizations:DescribeOrganization", "organizations:ListAccounts" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "guardduty:ArchiveFindings", "guardduty:GetFindings", "guardduty:ListDetectors" ], "Resource": "*" } ] }

AWS managed policy: AmazonDetectiveServiceLinkedRole

You can't attach the AmazonDetectiveServiceLinkedRole policy to your IAM entities. This policy is attached to a service-linked role that allows Detective to perform actions on your behalf. For more information, see Using service-linked roles for Detective.

This policy grants administrative permissions that allow the service-linked role to retrieve account information for an organization.

Permissions details

This policy includes the following permissions:

  • organizations – Retrieves account information for an organization.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "organizations:ListAccounts" ], "Resource": "*" } ] }

Detective updates to AWS managed policies

View details about updates to AWS managed policies for Detective since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the Document history page.

Change Description Date

AmazonDetectiveFullAccess – Updates to an existing policy

Detective added GuardDuty GetFindingsactions to the AmazonDetectiveFullAccess policy.

These actions allow getting GuardDuty findings from within Detective.

January 17, 2023

AmazonDetectiveMemberAccess – New policy

Detective added the AmazonDetectiveMemberAccess policy.

This policy provides member access to Detective and scoped access to the console UI dependencies.

January 17, 2023

AmazonDetectiveInvestigatorAccess – New policy

Detective added the AmazonDetectiveInvestigatorAccess policy.

This policy allows the principal to conduct investigations in Detective.

January 17, 2023

AmazonDetectiveServiceLinkedRole – New policy

Detective added a new policy for its service-linked role.

The policy allows the service-linked role to retrieve information about the accounts in an organization.

December 16, 2021

Detective started to track changes

Detective started to track changes for its AWS managed policies.

May 10, 2021