INFO 2004 Chap.10 AWS Compute Services: EC2, ECS and Lambda
AWS Compute Services: EC2, ECS and Lambda
The applied compute layer names EC2, ECS and Lambda, then adds Amazon Machine Images and Elastic Beanstalk. EC2 supplies scalable compute capacity without an up-front hardware purchase and can scale up or down. An AMI is a template for a virtual machine and one image can launch multiple instances. ECS manages containers through task definitions. Lambda runs code without the customer provisioning or managing servers.
The captured workshop then supplies the chapter's best reasoning asset: compare EC2, Lambda and containers for a start-up web application, batch data processing and microservices, and design an architecture combining at least two options with scalability and cost justification. Three tempting EC2 subtopics—instance types, purchasing options and cost optimisation—are only headings or external pointers here.
They remain explicit Canvas gaps. No instance-family names, prices, quotas or service ceilings are reconstructed.
What this chapter covers
- 01
EC2 as scalable compute capacity
- 02
AMI as a reusable machine template
- 03
ECS and task definitions
- 04
Lambda and server-management abstraction
- 05
Elastic Beanstalk as a named course service
- 06
Workshop scenario selection
- 07
Missing instance-type, purchasing and cost detail
Select and combine compute options for a mixed workload
- 1Separate the workload into persistent request handling and event-driven processing rather than forcing one choice across both.
- 1Evaluate EC2 for scalable compute capacity supporting the persistent component.
- 1Evaluate Lambda for code triggered without provisioning or managing servers in the event-driven step.
- 1Justify the combination through workload shape, scalability and cost reasoning, while leaving instance types and prices to current Canvas resources.
Key terms
- EC2
- An AWS compute service providing scalable capacity without requiring an up-front hardware investment.
- AMI
- A template used to launch virtual-machine instances; one image can support multiple launches.
- ECS
- An AWS container service described through managed containers and task definitions.
- Task definition
- The ECS concept used to describe how container tasks are configured.
- Lambda
- An AWS service for running code without provisioning or managing the underlying servers.
- Elastic Beanstalk
- A named AWS application service in the delivered compute topic; detailed mechanics are not captured here.
- Compute selection
- A scenario-led choice using workload fit, scalability, cost and operational responsibility.
AWS Compute Services: EC2, ECS and Lambda FAQ
Which three compute services does the course emphasise?
EC2, ECS and Lambda.
What is an AMI?
A template for a virtual machine that can be used to launch instances.
Are EC2 instance types documented in the captured materials?
No. The topic appears as a video heading, but the substantive teaching is absent. Confirm it on Canvas.
Can I use provider prices in a recommendation?
Only if the course materials state them. This guide keeps the decision qualitative and routes current pricing to the linked tools.
What is the workshop's key design challenge?
Choose among scenarios and combine at least two compute options, justifying scalability and cost.
Assessment move
Build a service card only from captured claims: EC2 capacity, AMI template, ECS containers and task definitions, Lambda's server-management abstraction, and the named Elastic Beanstalk topic. Then practise the three workshop scenarios and one combined design. Keep an explicit Canvas list for instance types, purchasing options and cost optimisation so familiarity with AWS does not fill the source gap.
Working through AWS Compute Services: EC2, ECS and Lambda in INFO 2004? Sia is AskSia’s AI Computer Science tutor — ask any INFO 2004 AWS Compute Services: EC2, ECS and Lambda question and get a clear, step-by-step explanation grounded in how INFO 2004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
