OP-03 150 150 CloudGovCo
  • Provides end-to-end automated management based on monitoring key data points such as the server, database, application, network, middleware, and custom aspects.
  • Uses tools to automate constant testing for failure.
  • Replicates data across regions, and uses multiple-availability-zone and multiple-region architectures to meet safe distance requirements for business continuity.
  • Automates zone fail-over and recovery.
  • Uses stateless services so failure cases can be rerouted.
  • Uses graceful degradation to fail to lower levels of functionality.
  • Designs with N+1 redundancy to allocate extra capacity.
  • Designs cloud architectures based on cloud principles.
  • Load balances across zones first, then instances.
  • Sends backup snapshots to different accounts across different geographical locations (including on-premises) at regular intervals.
  • Provides Cloud Design Standards for applications at each support tier.
  • Uses multiple accounts to limit the impact of compromising the primary account’s authentication credentials during a failure.
  • Provides an option for Internet connectivity completely independent of terrestrial infrastructure.
  • Provides backup Internet connections using different Tier 1 carriers or Tier 2 or 3 carriers that rely on different Tier 1 carriers.
  • Provides backup Internet connections using different medium (copper, fiber, or wireless) and different entry points.
  • Develops or procures software that is designed to function offline (to some usable extent) without connectivity.
  • Tests and validates the design, architecture, and implementation against resilient single-point failure or classical RTO/RPO depending on the appetite for downtime.