AWS services used in ECS architecture
| AWS service | Description |
|---|---|
|
Compute & Serverless |
|
|
Management API handlers, configuration redeployment triggers, and custom resources |
|
|
Content-aware smart cropping (face, label, custom label, text, and logo detection) and content moderation (v8.1+) |
|
|
API & Networking |
|
|
REST API for the management API (Admin UI CRUD operations on origins, mappings, and transformation policies) |
|
|
CDN for content delivery and caching |
|
|
Application Load Balancer that distributes image transformation requests across ECS tasks |
|
|
Storage |
|
|
Source image storage, transformed image cache |
|
|
Database |
|
|
Storing transformation policies, mappings, and origins; caching Amazon Rekognition detection results (a dedicated |
|
|
Authentication & Authorization |
|
|
User authentication for admin UI |
|
|
Roles, policies, and permissions |
|
|
Monitoring & Logging |
|
|
Supporting service for metrics, dashboards, alarms, and log management |
|
|
Container Services (ECS Architecture) |
|
|
Container orchestration for image processor |
|
|
Container image registry |
|
|
VPC, subnets, security groups for ECS |
|
|
Automation & Events |
|
|
Event-driven automation |
|
|
ECS task auto-scaling |
|
|
Security & Encryption |
|
|
Encryption key management |
|
|
Stores the secret used to derive the encryption key for the management API’s encrypted pagination tokens (v8.1+) |
|
|
Deployment & Management |
|
|
Infrastructure as code |
|
|
Infrastructure definition framework |
Important
Configuration Delay and Cached Images
Changes to origins, transformation policies, or mappings may take up to 5 minutes to propagate across all image processing tasks. During this period, some requests may still use the previous configuration. Configuration updates do not automatically refresh cached images. Cached images processed with previous settings will remain available until they expire or are manually invalidated.
