Getting started with AWS IAM Access Analyzer
Use the information in this topic to learn about the requirements necessary to use and manage AWS IAM Access Analyzer, and then how to enable Access Analyzer. To learn more about the service-linked role for Access Analyzer, see Using service-linked roles for AWS IAM Access Analyzer.
Permissions required to use Access Analyzer
To successfully configure and use Access Analyzer, the account you use must be granted the required permissions.
AWS managed policies for Access Analyzer
AWS IAM Access Analyzer provides AWS managed policies to help you get started quickly.
-
IAMAccessAnalyzerFullAccess - Allows full access to Access Analyzer for administrators. This policy also allows creating the service-linked roles that are required to allow Access Analyzer to analyze resources in your account or AWS organization.
-
IAMAccessAnalyzerReadOnlyAccess - Allows read-only access to Access Analyzer. You must add additional policies to your IAM identities (users, groups of users, or roles) to allow them to view their findings.
Resources defined by AWS IAM Access Analyzer
To view the resources defined by Access Analyzer, see Resource types defined by AWS IAM Access Analyzer in the Service Authorization Reference.
Required Access Analyzer service permissions
Access Analyzer uses a service-linked role named AWSServiceRoleForAccessAnalyzer to grant the service
read-only access to analyze AWS resources with resource-based policies on your behalf.
When you create an analyzer with your account as the zone of trust, the service creates the
role in your account. When you create an analyzer with your organization as the zone of
trust, the service creates a role in each account that belongs to your organization. For
more information, see Using service-linked roles for
AWS IAM Access Analyzer.
Access Analyzer is Regional. You must enable Access Analyzer in each Region independently.
In some cases, after you enable Access Analyzer, the Findings page loads with no findings. This might be due to a delay in the console for populating your findings. You need to manually refresh the browser to view your findings. If you still don't see any findings, it's because you have no supported resources in your account that can be accessed by an external entity. If a policy that grants access to an external entity is applied to a resource, Access Analyzer generates a finding.
It may take up to 30 minutes after a policy is modified for Access Analyzer to analyze the resource and then either generate a new finding or update an existing finding for the access to the resource.
Enabling Access Analyzer
To enable Access Analyzer in a Region, you must create an analyzer in that Region. You must create an analyzer in each Region in which you want to monitor access to your resources.
To create an analyzer with the account as the zone of trust
-
Open the IAM console at https://console.aws.amazon.com/iam/
. -
Choose Access analyzer.
-
Choose Create analyzer.
-
On the Create analyzer page, confirm that the Region displayed is the Region where you want to enable Access Analyzer.
-
Enter a name for the analyzer.
-
Choose the account as the zone of trust for the analyzer.
Note If your account is not the AWS Organizations management account or delegated administrator account, you can create only one analyzer with your account as the zone of trust.
-
Optional. Add any tags that you want to apply to the analyzer.
-
Choose Create Analyzer.
When you create an analyzer to enable Access Analyzer, a service-linked role named
AWSServiceRoleForAccessAnalyzer is created in your account.
To create an analyzer with the organization as the zone of trust
-
Open the IAM console at https://console.aws.amazon.com/iam/
. -
Choose Access analyzer.
-
Choose Create analyzer.
-
On the Create analyzer page, confirm that the Region displayed is the Region where you want to enable Access Analyzer.
-
Enter a name for the analyzer.
-
Choose your organization as the zone of trust for the analyzer.
-
Optional. Add any tags that you want to apply to the analyzer.
-
Choose Create Analyzer.
When you create an analyzer with the organization as the zone of trust, a service-linked
role named AWSServiceRoleForAccessAnalyzer is created in each account of your organization.
Access Analyzer status
To view the status of your analyzers, choose Analyzers. Analyzers created for an organization or account can have the following status:
| Status | Description |
|---|---|
|
Active |
The analyzer is actively monitoring resources within its zone of trust. The analyzer actively generates new findings and updates existing findings. |
|
Creating |
The creation of the analyzer is still in progress. The analyzer becomes active once creation is complete. |
|
Disabled |
The analyzer is disabled due to an action taken by the AWS Organizations administrator. For example, removing the analyzer’s account as the delegated administrator for Access Analyzer. When the analyzer is in a disabled state it does not generate new findings or update existing findings. |
|
Failed |
The creation of the analyzer failed due to a configuration issue. The analyzer won't generate any findings. Delete the analyzer and create a new analyzer. |
Access Analyzer quotas
Access Analyzer has the following quotas:
| Resource | Default quota | Maximum quota |
|---|---|---|
|
Maximum analyzers with an account zone of trust |
1 |
1 |
|
Maximum analyzers with an organization zone of trust |
5 |
20¹ |
|
Maximum archive rules per analyzer |
100 Each archive rule can have up to 20 values per criterion. |
1,000¹ |
Maximum number of access previews per analyzer per hour |
1,000 |
1,000 |
AWS CloudTrail log files processed per policy generations |
100,000 |
100,000 |
Concurrent policy generations |
1 |
1 |
Policy generation AWS CloudTrail data size |
25 GB |
25 GB |
Policy generation AWS CloudTrail time range |
90 days |
90 days |
Policy generations per day |
Africa (Cape Town): 5 Asia Pacific (Hong Kong): 5 Europe (Milan): 5 Middle East (Bahrain): 5 All other supported regions: 50 Canceled policy generation requests apply to the daily quota. |
Africa (Cape Town): 5 Asia Pacific (Hong Kong): 5 Europe (Milan): 5 Middle East (Bahrain): 5 All other supported regions: 50 |
¹Some quotas are customer-configurable using Service Quotas.
