Choosing AWS Service

Fargate

Choose Fargate if

• You are doing Lift and shift with minimal rework
• Longer-running processes or larger deployment packages than 15 mins
• Predictable, consistent workload
• Need more than 3 GB of memory
• Application with a non-HTTP/S listener
• Run side cars with your service (agents only supported as side cars)
• Container image portability with Docker runtime

Lambda

• Tasks that run less than 15 minutes
• Spiky, unpredictable workloads
• Unknown demand
• Lighter-weight, application-focused stateless computing
• Simplified IT automation
• Real-time data processing
• Reduced complexity for development and operations

S3

• Data lakes
• Economical state store
• Claim-check pattern
• Filter data retrieved by Lambda (S3 Select)

---

Was this page helpful?

Yes No