AWS IAM Access Analyzer
Contains information about findings from your IAM Access Analyzer.
Sync Type: Full Synchronisation
Details
AWS IAM Access Analyzer helps identify resources in your organization and accounts that are shared with external entities. It uses mathematical analysis and automated reasoning about policies to help you understand resource access permissions and identify unintended access. This input connector retrieves findings from your IAM Access Analyzer, allowing you to monitor and analyze potential security risks related to resource sharing.
Functionality
On each sync, Monad connects to the specified IAM Access Analyzer in the configured region and retrieves its findings through the ListFindingsV2 API, paging through the results automatically.
The connector supports optional filtering to narrow down the findings based on various criteria such as resource type, finding status, principal information, and more.
Every sync re-fetches every matching finding, including ARCHIVED and RESOLVED findings unless you filter on status, so the same finding is emitted again on each run.
Requirements
- IAM Role Assumption / Static Credentials
- Example permission to attach to the role/user:
Code
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
cron | string (cron) | Yes | 0 * * * * | Cron string for scheduling the ingest of your input. eg: 0 0 * * * - Daily at midnight, or */15 * * * * - Every 15 minutes. Defaults to an hour. |
role_arn | string | No | - | The ARN of the IAM role to assume for accessing AWS resources. |
region | string | Yes | us-east-1 | The AWS region to use. Allowed values: us-east-1, us-east-2, us-west-1, us-west-2, af-south-1, ap-east-1, ap-south-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-southeast-1, ap-southeast-2, ca-central-1, ca-west-1, cn-north-1, cn-northwest-1, eu-central-1, eu-west-1, eu-west-2, eu-west-3, eu-north-1, eu-south-1, me-south-1, sa-east-1, us-gov-east-1, us-gov-west-1. |
analyzer_arn | string | Yes | - | The [ARN of the analyzer] to retrieve findings from. |
filters | array of object | No | - | Optional filters to match for the findings to return. |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
Note: Filter keys must be unique within the filters array.
Each filter must set exactly one operator: eq, neq, contains or exists.
The Region setting must be the region of the analyzer in Analyzer ARN, because Monad calls Access Analyzer in the configured region.
Secrets (Static Credentials Only)
| Secret | Type | Required | Description |
|---|---|---|---|
access_key | secret | No | The Access Key from AWS to authenticate with AWS |
secret_key | secret | No | The Secret Key from AWS to authenticate with AWS |
⚠️ Authentication: Choose either Role ARN (recommended) or static credentials. See AWS Authentication Guide for setup instructions.
Alternate Method: Real-time Events via EventBridge + SQS
This method provides real-time streaming of Access Analyzer findings as they occur, offering immediate visibility into new security issues. When Access Analyzer discovers a new finding, it automatically sends the event to an SQS queue via EventBridge, which Monad can then consume using the AWS SQS input connector.
Benefits
- Real-time alerts: Receive findings immediately as they're discovered
- Reduced API calls: No need for periodic polling of the Access Analyzer API
- Event-driven architecture: Integrates seamlessly with other AWS services
This assumes that you have an IAM Access Analyzer setup, if not, please do so.
Step 1: Create SQS Queue
- Navigate to SQS Console
- Click "Create queue"
- Configure:
- Type: Standard
- Name: access-analyzer-findings
- Click "Create queue"
- Save the queue URL for later use
Step 2: Configure SQS Queue Permissions
- In your SQS queue, go to Access policy tab
- Click "Edit"
- Replace with this policy (update with your account ID and region):
Code
Step 3: Create EventBridge Rule
- Navigate to EventBridge Console → Rules
- Click "Create rule"
- Configure basic details:
- Name: access-analyzer-to-sqs
- Description: Send Access Analyzer findings to SQS
- Event bus: default
- Rule type: Rule with an event pattern
- Click "Next"
Step 4: Configure Event Pattern
- Event source: AWS services
- AWS service: Access Analyzer
- Event type: Access Analyzer Finding
- Click "Next"
Step 5: Configure Target
- Target type: AWS service
- Select a target: SQS queue
- Queue: Select your access-analyzer-findings queue
- Click "Next" → "Next" → "Create rule"
Sample Record
Code
Sync frequency
This input runs on a cron schedule (default hourly, 0 * * * *), which you can configure on the pipeline.
See Input Sync Frequency for details.
Related Articles
Community transforms
The Monad Transforms Repository has ready-made transforms for this input. Import one into your organization, then add it to a pipeline after this input.
| Format | Transform |
|---|---|
| OCSF v1.9.0 | AWS IAM Access Analyzer Findings to OCSF v1.9.0 |
| ECS v9.5.0 | AWS IAM Access Analyzer Findings to ECS v9.5.0 |
| CEF | AWS IAM Access Analyzer Findings to CEF |
CEF transforms emit an intermediate record; add the CEF Serializer transform after one to produce the CEF:0 string.