spb/datacenterindex

1id: aws-regions2name: AWS regions and Local Zones3domain: docs.aws.amazon.com4kind: cloud_provider5mode: html6priority: 17license: "Publicly published provider documentation (AWS Global Infrastructure docs); facts only"8attribution: "Amazon Web Services — docs.aws.amazon.com"9homepage: https://aws.amazon.com/about-aws/global-infrastructure/10coverage: { global: true }11implementation: cloud_regions12fetch:13  level: 114  maxLevel: 215  rpm: 1016  concurrency: 117  respectRobots: true18  maxCreditsPerRun: 019discovery:20  seeds:21    - { url: "https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html", group: regions, pageType: cloud_region }22    - { url: "https://docs.aws.amazon.com/local-zones/latest/ug/available-local-zones.html", group: regions, pageType: cloud_region }23schedule:24  regions: weekly25extractors:26  regions:27    match: ["/global-infrastructure/latest/regions/aws-regions\\.html"]28    kind: cloud_region29    parser: cloud_aws_docs_regions_v130  local_zones:31    match: ["/local-zones/latest/ug/available-local-zones\\.html"]32    kind: cloud_region33    parser: cloud_aws_local_zones_v134defaults:35  providerName: AWS36notes: >37  Static docs tables: 34 commercial regions (code, name, AZ count, geography, opt-in) and ~45 Local Zone groups38  (externalIds.kind = local_zone, zone names/ids, parent region). The AZ docs page is fetched once per run for the39  state-level geography (Virginia, Ohio, …). The marketing pages (regions_az/, localzones/locations/) are JS-heavy40  and not needed; the regional-services JSON (api.regional-table…) only lists service × region and is not used.41