AWS services used in ECS architecture
| AWS service | Description |
|---|---|
|
Compute & Serverless |
|
|
Image processing functions, API handlers |
|
|
Image transformation features (smart cropping, content moderation) |
|
|
API & Networking |
|
|
REST API for image transformation requests |
|
|
CDN for content delivery and caching |
|
|
Application load balancing (for ECS architecture) |
|
|
Storage |
|
|
Source image storage, transformed image cache |
|
|
Database |
|
|
Storing transformation policies, mappings, and origins |
|
|
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 |
|
|
Manages secrets to support URL signatures |
|
|
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.
