id: aws-regions
name: AWS regions and Local Zones
domain: docs.aws.amazon.com
kind: cloud_provider
mode: html
priority: 1
license: "Publicly published provider documentation (AWS Global Infrastructure docs); facts only"
attribution: "Amazon Web Services — docs.aws.amazon.com"
homepage: https://aws.amazon.com/about-aws/global-infrastructure/
coverage: { global: true }
implementation: cloud_regions
fetch:
  level: 1
  maxLevel: 2
  rpm: 10
  concurrency: 1
  respectRobots: true
  maxCreditsPerRun: 0
discovery:
  seeds:
    - { url: "https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html", group: regions, pageType: cloud_region }
    - { url: "https://docs.aws.amazon.com/local-zones/latest/ug/available-local-zones.html", group: regions, pageType: cloud_region }
schedule:
  regions: weekly
extractors:
  regions:
    match: ["/global-infrastructure/latest/regions/aws-regions\\.html"]
    kind: cloud_region
    parser: cloud_aws_docs_regions_v1
  local_zones:
    match: ["/local-zones/latest/ug/available-local-zones\\.html"]
    kind: cloud_region
    parser: cloud_aws_local_zones_v1
defaults:
  providerName: AWS
notes: >
  Static docs tables: 34 commercial regions (code, name, AZ count, geography, opt-in) and ~45 Local Zone groups
  (externalIds.kind = local_zone, zone names/ids, parent region). The AZ docs page is fetched once per run for the
  state-level geography (Virginia, Ohio, …). The marketing pages (regions_az/, localzones/locations/) are JS-heavy
  and not needed; the regional-services JSON (api.regional-table…) only lists service × region and is not used.