AWS Cloud

Edge Delivery

A concise overview of Edge Delivery, how it relates to AWS Cloud, key considerations, and conditions to confirm.

Scope

For Edge Delivery, we define applicability from the purpose and constraints, including conditions where it should not be used. The relationship to AWS Cloud remains visible so the reasons behind each decision can be reviewed.

Design decisions

For Edge Delivery, we avoid locking the design to one model or platform, separate data, integration, and monitoring, and record the reasons for each choice. The relationship to AWS Cloud remains visible so the reasons behind each decision can be reviewed.

Validation

For Edge Delivery, we use repeatable inputs and criteria and inspect failure cases as well as expected behavior. The relationship to AWS Cloud remains visible so the reasons behind each decision can be reviewed.

Operational review

For Edge Delivery, we track changes, quality shifts, and use patterns while keeping a path for rollback. The relationship to AWS Cloud remains visible so the reasons behind each decision can be reviewed.

Human governance

For Edge Delivery, we do not leave consequential decisions to automation alone and define accountable review points. The relationship to AWS Cloud remains visible so the reasons behind each decision can be reviewed.