Identity and Access Management Access Analyzer helps you to set, verify, and refine your IAM policies by providing a suite of capabilities. Its features include findings for external and unused access, basic and custom policy checks for validating policies, and policy generation to generate fine-grained policies. To start using IAM Access Analyzer to identify external or unused access, you first need to create an analyzer.
External access analyzers help identify potential risks of accessing resources by enabling you to identify any resource policies that grant access to an external principal. It does this by using logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An external principal can be another Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an anonymous user. You can also use IAM Access Analyzer to preview public and cross-account access to your resources before deploying permissions changes.
Unused access analyzers help identify potential identity access risks by enabling you to identify unused IAM roles, unused access keys, unused console passwords, and IAM principals with unused service and action-level permissions.
Beyond findings, IAM Access Analyzer provides basic and custom policy checks to validate IAM policies before deploying permissions changes. You can use policy generation to refine permissions by attaching a policy generated using access activity logged in CloudTrail logs.
This guide describes the IAM Access Analyzer operations that you can call programmatically. For general information about IAM Access Analyzer, see Identity and Access Management Access Analyzer in the IAM User Guide.
tags: - name: findingAggregator paths: /findingAggregator/create: POST: summary: Amazon Web Services Createfindingaggregator description: 'Used to enable finding aggregation. Must be called from the aggregation Region. For more details about cross-Region replication, see Configuring finding aggregation in the Security Hub User Guide. ' operationId: amazonWebServicesCreateFindingAggregator tags: - findingAggregator /findingAggregator/delete/{FindingAggregatorArn+}: DELETE: summary: Amazon Web Services Deletefindingaggregator description: 'Deletes a finding aggregator. When you delete the finding aggregator, you stop finding aggregation. When you stop finding aggregation, findings that were already aggregated to the aggregation Region are still visible from the aggregation Region. New findings and finding updates are not aggregated. ' operationId: amazonWebServicesDeleteFindingAggregator tags: - findingAggregator /findingAggregator/get/{FindingAggregatorArn+}: GET: summary: Amazon Web Services Getfindingaggregator description: Returns the current finding aggregation configuration. operationId: amazonWebServicesGetFindingAggregator tags: - findingAggregator /findingAggregator/list: GET: summary: Amazon Web Services Listfindingaggregators description: If finding aggregation is enabled, then ListFindingAggregators returns the ARN of the finding aggregator. You can run this operation from any Region. operationId: amazonWebServicesListFindingAggregators tags: - findingAggregator /findingAggregator/update: PATCH: summary: Amazon Web Services Updatefindingaggregator description: 'Updates the finding aggregation configuration. Used to update the Region linking mode and the list of included or excluded Regions. You cannot use UpdateFindingAggregator to change the aggregation Region. You must run UpdateFindingAggregator from the current aggregation Region. ' operationId: amazonWebServicesUpdateFindingAggregator tags: - findingAggregator