Amazon Access Analyzer
Amazon Access Analyzer by Amazon Web Services (AWS) identifies resources that grant access to external or public principals — such as S3 buckets, IAM roles, KMS keys, Lambda functions, Secrets Manager secrets, and SQS queues — helping you quickly answer "which of my resources are reachable from outside this account?" You can bring finding and finding definition data from Amazon Access Analyzer into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with Amazon Access Analyzer and how to obtain that information from Amazon. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Amazon Access Analyzer from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Amazon Access Analyzer with Brinqa:
-
Access key ID and Secret access key: The access keys associated with the AWS account. The account must have the required read-only permissions for IAM Access Analyzer. For additional information, see Create an IAM user for AWS access.
-
Default region: The AWS region for the connector. If not specified, the connector uses the AWS Default Region Provider Chain to automatically determine the most appropriate region. For additional information on the AWS Default Region Provider Chain, refer to the AWS documentation.
Create an IAM user for AWS access
The connector authenticates using the AWS SDK's credential resolution chain. If an assume-role ARN is configured, the connector assumes that IAM role using the provided credentials. Otherwise, it uses the provided access keys directly, falling back to the AWS Default Credential Provider Chain (environment variables, ~/.aws/credentials, or EC2 instance metadata).
The IAM user or role must have the following permissions:
access-analyzer:ListAnalyzers
access-analyzer:ListFindings
Additional settings
The Amazon Access Analyzer connector contains additional options for specific configuration:
- Assume role ARN: ARN of an IAM role to assume. Comma-separated to assume multiple roles in the same sync.
- Session duration: Assume-role session duration in seconds. The default setting is 3600.
- Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
- Parallel requests: The maximum number of parallel API requests. The default setting is 8.
- Maximum retries: The maximum number of times that the integration attempts to connect to the Amazon Access Analyzer API before giving up and reporting a failure. The default setting is 10.
Types of data to retrieve
The Amazon Access Analyzer connector can retrieve the following types of data from the Amazon Access Analyzer API:
Table 1: Data retrieved from Amazon Access Analyzer
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Finding | Yes | Finding |
| FindingDefinition | Yes | Finding Definition |
For detailed steps on how to view the data retrieved from Amazon Access Analyzer in the Brinqa Platform, see How to view your data.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
Finding
Table 2: Finding attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
FindingSummary.action | ACTIONS |
AnalyzerSummary.arn | ANALYZER_ARN |
FindingSummary.analyzedAt | ANALYZED_AT |
Constant AWS | CLOUD_PROVIDER |
FindingSummary.condition (entries rendered key=value) | CONDITION |
FindingSummary.error | ERROR |
FindingSummary.id | FINDING_ID |
FindingSummary.createdAt | FIRST_FOUND |
| Sync timestamp | LAST_CAPTURED |
FindingSummary.updatedAt | LAST_FOUND |
FindingSummary.id | NAME |
FindingSummary.principal (entries rendered key=value) | PRINCIPAL |
FindingSummary.statusAsString | PROVIDER_STATUS |
| Analyzer region | REGION |
FindingSummary.resource | RESOURCE |
FindingSummary.resourceOwnerAccount | RESOURCE_OWNER_ACCOUNT |
FindingUtils.normalizeFindingStatus(rawStatus) (defaults ACTIVE) | SOURCE_STATUS |
FindingSummary.resource | TARGETS |
AccessAnalyzer:{resourceType}:public={bool} | TYPE |
{analyzerArn}/{findingId} | UID |
FindingDefinition
Table 3: FindingDefinition attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
Constant Access Analyzer | CATEGORIES |
Constant AWS | CLOUD_PROVIDER |
| Generated (narrative explaining public vs cross-account shape) | DESCRIPTION |
FindingSummary.isPublic | IS_PUBLIC |
| Sync timestamp | LAST_CAPTURED |
Generated (e.g. "AWS::S3::Bucket allows public access") | NAME |
| Generated (remediation guidance) | RECOMMENDATION |
FindingSummary.resourceTypeAsString | RESOURCE_TYPE |
FindingSummary.resourceType (or Unknown) | TAGS |
AccessAnalyzer:{resourceType}:public={bool} | UID |
Operation options
The Amazon Access Analyzer connector does not support operation options at this time.
APIs
The Amazon Access Analyzer connector uses the AWS IAM Access Analyzer API. Specifically, it uses the following endpoints:
Table 4: Amazon Access Analyzer API endpoints
| Connector Object | API Endpoint |
|---|---|
| Finding | access-analyzer:ListAnalyzersaccess-analyzer:ListFindings |
| FindingDefinition | access-analyzer:ListAnalyzersaccess-analyzer:ListFindings (shared cache) |
Changelog
The Amazon Access Analyzer connector has undergone the following changes:
This connector is part of a bundled release with other connectors from the same vendor. If a version shows "No change", it means that the connector version was updated for consistency as part of the bundle, but no functional changes were made to this specific connector. You can update to or skip this version without affecting your existing configuration.
Table 5: Amazon Access Analyzer connector changelog
| Version | Description | Date Published |
|---|---|---|
| 3.1.0 | Initial Integration+ release. | June 1st, 2026 |