> For the complete documentation index, see [llms.txt](https://awsinpractice.itassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://awsinpractice.itassist.com/study-group/aws-certified-solutions-architect-associate/domain-3/task-statement-3.2-design-high-performing-and-elastic-compute-solutions.md).

# Task Statement 3.2: Design High-Performing and Elastic Compute Solutions

### **📌 Task Statement 3.2: Design High-Performing and Elastic Compute Solutions**

This study group focuses on **designing scalable, high-performing, and elastic compute architectures** that **dynamically adjust to workload demands** while maintaining cost efficiency.

We will follow **SecureCart**, an e-commerce platform, as they **optimize their compute workloads**, transition to **event-driven compute solutions**, and explore **containerized and serverless architectures**.

***

### **📅 Study Group Agenda**

| **Week**   | **Topic**                                    | **Key AWS Services**                                    |
| ---------- | -------------------------------------------- | ------------------------------------------------------- |
| **Week 1** | AWS Compute Services & Use Cases             | EC2, Fargate, Lambda, AWS Batch                         |
| **Week 2** | Elastic & Auto-Scaling Compute Architectures | EC2 Auto Scaling, AWS Auto Scaling                      |
| **Week 3** | Decoupling Workloads for Performance         | SQS, SNS, EventBridge, Step Functions                   |
| **Week 4** | Serverless & Containerized Compute Solutions | AWS Lambda, AWS Fargate, ECS, EKS                       |
| **Week 5** | Compute Optimization & Cost Efficiency       | Right-Sizing EC2, Compute Savings Plans, Spot Instances |
| **Week 6** | Hands-on Labs & Final Challenge              | Implementing a High-Performance AWS Compute Solution    |

### **Final Study Group Summary**

| **Week**   | **Focus Area**                         | **Outcome**                                      |
| ---------- | -------------------------------------- | ------------------------------------------------ |
| **Week 1** | AWS Compute Services & Use Cases       | Select the Best Compute Service for Workloads    |
| **Week 2** | Elastic & Auto-Scaling Architectures   | Implement Auto Scaling for Compute Resources     |
| **Week 3** | Decoupling Workloads for Performance   | Use SQS, SNS, & EventBridge for Scalable Systems |
| **Week 4** | Serverless & Containerized Compute     | Deploy Lambda, Fargate, ECS, & EKS               |
| **Week 5** | Compute Optimization & Cost Efficiency | Optimize EC2, Lambda, & Compute Costs            |
| **Week 6** | Hands-on Scenarios                     | Implement a Scalable Compute Solution            |

***

### **🚀 Next Steps**

Would you like:\
✅ **Terraform automation scripts for AWS compute services?**\
✅ **Scenario-based quizzes for each study group session?**\
✅ **Instructor-led deep-dive discussions?**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://awsinpractice.itassist.com/study-group/aws-certified-solutions-architect-associate/domain-3/task-statement-3.2-design-high-performing-and-elastic-compute-solutions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.