Use one visual per major section of the article rather than one for every paragraph. For this VPC Endpoints article, these are the clearest AWS-authored images to use, in order.
1. The original problem — private subnets using NAT Gateway
Place this after “The Problem: Private Does Not Mean Disconnected.”
Caption:
Traditional AWS architecture where workloads in private subnets use NAT Gateways for outbound connectivity.
This establishes the architecture you are trying to improve.
2. Gateway VPC Endpoint for Amazon S3
Place this after “What Is a VPC Endpoint?” or at the start of “Gateway VPC Endpoints.”
Caption:
Amazon EC2 instances in private subnets accessing Amazon S3 through an S3 Gateway VPC Endpoint without requiring a NAT Gateway.
This is one of the most important visuals in the article.
3. Explain how the S3 route changes
Use this beside the section explaining:
S3 Prefix List → Gateway Endpoint
Caption:
Private Amazon S3 access using a VPC endpoint, keeping application-to-S3 communication on AWS networking.
For the text beside it, show:
Before
0.0.0.0/0 → NAT Gateway
After
S3 Prefix List → S3 Gateway Endpoint
0.0.0.0/0 → NAT Gateway
The S3 endpoint route wins for matching S3 traffic because the service prefix-list route is more specific than the default route. ( AWS Documentation ) 4. Interface VPC Endpoint / AWS PrivateLink
Place this at “Interface VPC Endpoints.”
Caption:
Interface VPC Endpoints provide private IP-based access to supported AWS services through AWS PrivateLink.
This visual clearly shows the major difference from a gateway endpoint:
Gateway Endpoint
Route-table based
Interface Endpoint
ENI + private-IP based
5. Private DNS
Use the same architectural concept immediately after “Private DNS: One of the Most Important Concepts.”
Caption:
Private DNS allows applications to use normal AWS service DNS names while directing supported service traffic to interface endpoint private IP addresses.
The key flow readers should understand is:
Application
|
service.region.amazonaws.com
|
Private DNS
|
Endpoint ENI private IP
|
AWS PrivateLink
|
AWS Service
6. Interface endpoint security
Place this beside “Interface Endpoints Have Security Groups.”
Caption:
An isolated workload accessing an AWS service through an Interface VPC Endpoint rather than requiring general internet connectivity.
Explain beside it:
Application EC2
Security Group: SG-App
|
| HTTPS 443
v
Interface Endpoint
Security Group: SG-Endpoint
A useful endpoint rule is:
Inbound
TCP 443
Source:
SG-App
7. Endpoint policies and the data perimeter
Place this under “Endpoint Policies Add Another Control Layer.”
Caption:
VPC endpoint policies can help restrict which trusted identities and resources are allowed to communicate through the endpoint.
This is an excellent security-focused image because it shows that private connectivity alone is not enough.
Your text should emphasize:
Network Path
+
Endpoint Policy
+
IAM Policy
+
Resource Policy
rather than assuming the endpoint itself grants access.
8. Complete private AWS-service architecture
Use this after “A Practical Private Application Architecture.”
Caption:
A production VPC can combine private application subnets, gateway endpoints, interface endpoints, and NAT egress depending on the destination.
Your own article diagram should appear beside these:
Private EC2
|
+--------------+--------------+
| | |
v v v
Amazon S3 AWS Services Internet
| | |
v v v
Gateway Interface NAT
Endpoint Endpoint Gateway
This is arguably the main teaching diagram of the entire article.
9. Multi-AZ Interface Endpoint design
Place this under “High Availability Matters.”
Caption:
Interface endpoints can place endpoint network interfaces across multiple Availability Zones for resilient private service connectivity.
The architectural lesson is:
AZ-A
EC2
|
Endpoint ENI A
AZ-B
EC2
|
Endpoint ENI B
For a multi-AZ application, its network dependencies should also be designed with availability in mind.
10. On-premises → AWS PrivateLink → AWS service
Place this under “What About On-Premises Access?”
Caption:
An on-premises environment can reach an S3 Interface Endpoint through private AWS connectivity such as AWS Direct Connect or Site-to-Site VPN.
This helps explain why an S3 Interface Endpoint may be required even though S3 also offers a free Gateway Endpoint.
Show:
On-Premises
|
VPN / Direct Connect
|
v
AWS VPC
|
S3 Interface Endpoint
|
AWS PrivateLink
|
Amazon S3
Gateway and interface endpoints are therefore not interchangeable.
11. Centralized endpoints for many VPCs
This is an excellent advanced visual for the article.
Place it near enterprise architecture, shared services, or centralized endpoint design.
Caption:
Centralized Interface VPC Endpoints can be placed in a networking VPC and shared with spoke VPC architectures through centralized routing and DNS design.
This adds expert-level depth because it shows the topic scaling beyond a single VPC.
12. Final comparison — NAT vs Gateway vs Interface Endpoint
Finish the article with these visuals together:
Use this caption:
Three different connectivity requirements require three different network paths: NAT Gateway for general internet egress, Gateway VPC Endpoints for services such as S3 and DynamoDB, and Interface VPC Endpoints for private-IP access to supported services through AWS PrivateLink.
Then place this underneath:
PRIVATE WORKLOAD
|
+-------------+-------------+
| | |
v v v
S3 / Supported External
DynamoDB AWS Services Internet
| | |
v v v
Gateway Interface NAT
Endpoint Endpoint Gateway
That is the visual I would use as the final takeaway.
One important improvement: don't fill the article with AWS Console screenshots. For this topic, architecture diagrams are much more educational because readers need to understand traffic paths, route selection, DNS resolution, ENIs, and security boundaries—not just where to click in the console.
Loading article