AWS prescriptive-guidance documentation change
Summary
Updated image paths, changed section headers from markdown headings to bold formatting, standardized CloudFront naming ('Amazon CloudFront' to 'AWS CloudFront'), added 'pattern' to routing method names, and corrected a diagram label.
Security assessment
Changes involve formatting improvements, image path updates, and minor text refinements without introducing security content. Existing security mention (CloudFront field-level encryption) remains unchanged. No vulnerability fixes or new security features documented.
Diff
diff --git a/prescriptive-guidance/latest/cloud-design-patterns/api-routing-path.md b/prescriptive-guidance/latest/cloud-design-patterns/api-routing-path.md index eacfb9abd..740dee644 100644 --- a//prescriptive-guidance/latest/cloud-design-patterns/api-routing-path.md +++ b//prescriptive-guidance/latest/cloud-design-patterns/api-routing-path.md @@ -19 +19 @@ Path-based routing is considered a simple mechanism for sharing an HTTP API. How -On AWS, there are multiple ways to share an API and route effectively to the correct service. The following sections discuss three approaches: HTTP service reverse proxy, API Gateway, and Amazon CloudFront. None of the suggested approaches for unifying API services relies on the downstream services running on AWS. The services could run anywhere without issue or on any technology, as long as they're HTTP-compatible. +On AWS, there are multiple ways to share an API and route effectively to the correct service. The following sections discuss three approaches: HTTP service reverse proxy, API Gateway, and AWS CloudFront. None of the suggested approaches for unifying API services relies on the downstream services running on AWS. The services could run anywhere without issue or on any technology, as long as they're HTTP-compatible. @@ -38 +38 @@ The following diagram illustrates the HTTP service reverse proxy method. - + @@ -44 +44 @@ To get ready for operational production readiness, you will want to be able to a -### Pros +**Pros** @@ -48 +48 @@ The ultimate aim of the HTTP service reverse proxy method is to create a scalabl -### Cons +**Cons** @@ -60 +60 @@ You probably don't want to get too granular by mapping every path in every servi - + @@ -62 +62 @@ You probably don't want to get too granular by mapping every path in every servi -### Pros +**Pros** @@ -79 +79 @@ For control over more complex workflows, such as changing request attributes, RE -### Cons +**Cons** @@ -87 +87 @@ You can use the [dynamic origin selection feature](https://docs.aws.amazon.com/A -### Typical use case +**Typical use case** @@ -91 +91 @@ The routing logic lives as code within the Lambda@Edge function, so it supports - + @@ -93 +93 @@ The routing logic lives as code within the Lambda@Edge function, so it supports -### Pros +**Pros** @@ -99 +99 @@ Also, CloudFront supports [field-level encryption](https://docs.aws.amazon.com/A -### Cons +**Cons** @@ -111 +111 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Hostname routing +Hostname routing pattern @@ -113 +113 @@ Hostname routing -HTTP header routing +HTTP header routing pattern