本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。

# IAM Access Analyzer 终端节点和配额
<a name="access-analyzer"></a>

要以编程方式连接到 AWS 服务，请使用终端节点。 AWS 服务在该服务支持的部分或全部 AWS 区域提供以下终端节点类型：IPv4 终端节点、双栈终端节点和 FIPS 终端节点。部分服务提供全局端点。有关更多信息，请参阅 [AWS 服务端点](rande.md)。

服务配额，也称为限制，是您的 AWS 账户的最大服务资源或操作数量。有关更多信息，请参阅 [AWS 服务配额](aws_service_limits.md)。

以下是该服务的服务端点和服务限额。

## 服务端点
<a name="accessanalyzer_region"></a>


| 区域名称 | 区域 | 端点 | 协议 | 
| --- | --- | --- | --- | 
| 美国东部（俄亥俄州） | us-east-2 |  access-analyzer.us-east-2.amazonaws.com <br /> access-analyzer-fips.us-east-2.api.aws <br /> access-analyzer-fips.us-east-2.amazonaws.com <br /> access-analyzer.us-east-2.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 美国东部（弗吉尼亚州北部） | us-east-1 |  access-analyzer.us-east-1.amazonaws.com <br /> access-analyzer-fips.us-east-1.api.aws <br /> access-analyzer-fips.us-east-1.amazonaws.com <br /> access-analyzer.us-east-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 美国西部（北加利福尼亚） | us-west-1 |  access-analyzer.us-west-1.amazonaws.com <br /> access-analyzer-fips.us-west-1.api.aws <br /> access-analyzer-fips.us-west-1.amazonaws.com <br /> access-analyzer.us-west-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 美国西部（俄勒冈州） | us-west-2 |  access-analyzer.us-west-2.amazonaws.com <br /> access-analyzer-fips.us-west-2.api.aws <br /> access-analyzer-fips.us-west-2.amazonaws.com <br /> access-analyzer.us-west-2.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 非洲（开普敦） | af-south-1 |  access-analyzer.af-south-1.amazonaws.com <br /> access-analyzer.af-south-1.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（香港） | ap-east-1 |  access-analyzer.ap-east-1.amazonaws.com <br /> access-analyzer.ap-east-1.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（海得拉巴） | ap-south-2 |  access-analyzer.ap-south-2.amazonaws.com <br /> access-analyzer.ap-south-2.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（雅加达） | ap-southeast-3 |  access-analyzer.ap-southeast-3.amazonaws.com <br /> access-analyzer.ap-southeast-3.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（马来西亚） | ap-southeast-5 |  access-analyzer.ap-southeast-5.amazonaws.com <br /> access-analyzer.ap-southeast-5.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（墨尔本） | ap-southeast-4 |  access-analyzer.ap-southeast-4.amazonaws.com <br /> access-analyzer.ap-southeast-4.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（孟买） | ap-south-1 |  access-analyzer.ap-south-1.amazonaws.com <br /> access-analyzer.ap-south-1.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（新西兰） | ap-southeast-6 |  access-analyzer.ap-southeast-6.amazonaws.com <br /> access-analyzer.ap-southeast-6.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（大阪） | ap-northeast-3 |  access-analyzer.ap-northeast-3.amazonaws.com <br /> access-analyzer.ap-northeast-3.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（首尔） | ap-northeast-2 |  access-analyzer.ap-northeast-2.amazonaws.com <br /> access-analyzer.ap-northeast-2.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（新加坡） | ap-southeast-1 |  access-analyzer.ap-southeast-1.amazonaws.com <br /> access-analyzer.ap-southeast-1.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（悉尼） | ap-southeast-2 |  access-analyzer.ap-southeast-2.amazonaws.com <br /> access-analyzer.ap-southeast-2.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（台北） | ap-east-2 |  access-analyzer.ap-east-2.amazonaws.com <br /> access-analyzer.ap-east-2.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（泰国） | ap-southeast-7 |  access-analyzer.ap-southeast-7.amazonaws.com <br /> access-analyzer.ap-southeast-7.api.aws  | HTTPS<br />HTTPS | 
| 亚太地区（东京） | ap-northeast-1 |  access-analyzer.ap-northeast-1.amazonaws.com <br /> access-analyzer.ap-northeast-1.api.aws  | HTTPS<br />HTTPS | 
| 加拿大（中部） | ca-central-1 |  access-analyzer.ca-central-1.amazonaws.com <br /> access-analyzer-fips.ca-central-1.api.aws <br /> access-analyzer-fips.ca-central-1.amazonaws.com <br /> access-analyzer.ca-central-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 加拿大西部（卡尔加里） | ca-west-1 |  access-analyzer.ca-west-1.amazonaws.com <br /> access-analyzer-fips.ca-west-1.api.aws <br /> access-analyzer-fips.ca-west-1.amazonaws.com <br /> access-analyzer.ca-west-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| 欧洲地区（法兰克福） | eu-central-1 |  access-analyzer.eu-central-1.amazonaws.com <br /> access-analyzer.eu-central-1.api.aws  | HTTPS<br />HTTPS | 
| 欧洲地区（爱尔兰） | eu-west-1 |  access-analyzer.eu-west-1.amazonaws.com <br /> access-analyzer.eu-west-1.api.aws  | HTTPS<br />HTTPS | 
| 欧洲地区（伦敦） | eu-west-2 |  access-analyzer.eu-west-2.amazonaws.com <br /> access-analyzer.eu-west-2.api.aws  | HTTPS<br />HTTPS | 
| 欧洲地区（米兰） | eu-south-1 |  access-analyzer.eu-south-1.amazonaws.com <br /> access-analyzer.eu-south-1.api.aws  | HTTPS<br />HTTPS | 
| 欧洲地区（巴黎） | eu-west-3 |  access-analyzer.eu-west-3.amazonaws.com <br /> access-analyzer.eu-west-3.api.aws  | HTTPS<br />HTTPS | 
| 欧洲（西班牙） | eu-south-2 |  access-analyzer.eu-south-2.amazonaws.com <br /> access-analyzer.eu-south-2.api.aws  | HTTPS<br />HTTPS | 
| 欧洲地区（斯德哥尔摩） | eu-north-1 |  access-analyzer.eu-north-1.amazonaws.com <br /> access-analyzer.eu-north-1.api.aws  | HTTPS<br />HTTPS | 
| 欧洲（苏黎世） | eu-central-2 |  access-analyzer.eu-central-2.amazonaws.com <br /> access-analyzer.eu-central-2.api.aws  | HTTPS<br />HTTPS | 
| 以色列（特拉维夫） | il-central-1 |  access-analyzer.il-central-1.amazonaws.com <br /> access-analyzer.il-central-1.api.aws  | HTTPS<br />HTTPS | 
| 墨西哥（中部） | mx-central-1 |  access-analyzer.mx-central-1.amazonaws.com <br /> access-analyzer.mx-central-1.api.aws  | HTTPS<br />HTTPS | 
| 中东（巴林） | me-south-1 |  access-analyzer.me-south-1.amazonaws.com <br /> access-analyzer.me-south-1.api.aws  | HTTPS<br />HTTPS | 
| 中东（阿联酋） | me-central-1 |  access-analyzer.me-central-1.amazonaws.com <br /> access-analyzer.me-central-1.api.aws  | HTTPS<br />HTTPS | 
| 南美洲（圣保罗） | sa-east-1 |  access-analyzer.sa-east-1.amazonaws.com <br /> access-analyzer.sa-east-1.api.aws  | HTTPS<br />HTTPS | 
|  AWS GovCloud (US-East) | us-gov-east-1 |  access-analyzer.us-gov-east-1.amazonaws.com <br /> access-analyzer.us-gov-east-1.api.aws  | HTTPS<br />HTTPS | 
|  AWS GovCloud (US-West) | us-gov-west-1 |  access-analyzer.us-gov-west-1.amazonaws.com <br /> access-analyzer.us-gov-west-1.api.aws  | HTTPS<br />HTTPS | 

## 服务限额
<a name="limits_accessanalyzer"></a>


| Name | 默认值 | 可调整 | 说明 | 
| --- | --- | --- | --- | 
| 每个分析器每小时的访问预览次数 | 每个受支持的区域：1,000 个 |  [是](https://console.aws.amazon.com/servicequotas/home/services/access-analyzer/quotas/L-8750DAE0)  | 每个分析器每小时的访问预览的最大数量。 | 
| 账户级别分析器 | 每个受支持的区域：1 个 | 否 | 每个区域每个账户可以为每种分析器类型创建的最大 AWS 账户级别分析器数量。 | 
| 每个分析器的归档规则数 | 每个受支持的区域：100 个 |  [是](https://console.aws.amazon.com/servicequotas/home/services/access-analyzer/quotas/L-1E51937C)  | 每个分析器的存档规则的最大数量。 | 
| CloudTrail 每次生成策略都会处理的日志文件 | 每个受支持的区域：10 万个 | 否 | 每次生成策略可以处理的最大 CloudTrail 日志文件数。 | 
| 并发策略生成器 | 每个受支持的区域：1 个 | 否 | 并发策略生成的最大数量。 | 
| 组织级别分析器 | 每个受支持的区域：5 个 |  [是](https://console.aws.amazon.com/servicequotas/home/services/access-analyzer/quotas/L-6F85FE0C)  | 每个区域每个 AWS 账户可以为每种分析器类型创建的最大组织级别分析器数量。 | 
| 策略生成 CloudTrail 数据大小 | 每个受支持的区域：25 GB | 否 | 每次生成策略的最大 CloudTrail 数据量。 | 
| 策略生成 CloudTrail 时间范围 | 每个受支持的区域：90 个 | 否 | 生成策略 CloudTrail 时可以选择的最大时间范围（以天为单位）。 | 
| 每天生成策略 | af-south-1：5 个<br />ap-east-1：5 个<br />ap-south-2：5<br />ap-southeast-3：5 个<br />ap-southeast-4:5<br />ca-west-1:5<br />eu-central-2：5<br />eu-south-1：5 个<br />eu-south-2：5<br />me-central-1:5<br />每个其他支持的区域：50 个 | 否 | 每天策略生成的最大数量。 |