> For the complete documentation index, see [llms.txt](https://awsarch.adot8.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://awsarch.adot8.com/module-2.md). # Module 2 ### AWS Business Operations

### Role of a cloud architect | Plan | Research | Build | | ----------------------------------------------------- | ------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Set technical cloud strategy with business leads. | Investigate cloud services specifications and workload requirements | Design the transformation roadmap with milestones, work streams, and owners. | | Analyze solutions for business needs and requirements | Review existing workload architectures | Manage the adoption and migration | | | Design prototype solutions | | ### AWS Well-Architected Framework {% embed url="" %}

### AWS WA Tool Checks out your environment and gives you recommendations to be compliant with best practices and the AWS Well-Architected Framework

The AWS Well-Architected Framework provides a consistent approach to evaluating cloud architectures and guidance to help implement designs ### Design Trade-offs * Evaluate trade-offs so you can select an optimal approach. * Examples of trade-offs include the following * Trade consistency, durability, and space for time and latency to deliver higher performance. * For new features, prioritize speed to market over cost. * Base design decisions on empirical data {% hint style="info" %} Do you need CloudFront if you don't have customers outside your country? {% endhint %} ### Implement scalability

{% embed url="" %} ### Automating your environment

* No need for human-interaction to spin up another EC2 instance if this were to occur over night ### Infrustructure as Code (IaC) * Use files with code to deploy applications or instances * Rapidly deploy duplicate environments. * Reduce configuration errors from manual configuration. * Propagate changes consistently to all stacks

{% hint style="info" %} All someone will have to do is fill in the blanks (IP = ?) {% endhint %} ### Treating resources as disposable * Automate deployment of new resources with identical configurations * Stop resources that are not in use * Test updates on new resources, and then replace old resources with updated ones ### Designing architectures with independent components

### Design services, not servers * When appropriate, consider using containers or a serverless solution. * Message queues can handle communication between applications. * Static web assets can be stored off the server, such as on Amazon Simple Storage Service (Amazon S3). * Managed AWS services can handle user authentication and user state storage. {% hint style="info" %} A **queue** can be used to prevent from applications from crashing when experiencing high workloads (e.g. online store sending orders to a shipping service. **Queue** in the middle of the two) {% endhint %} ### Database solution requirements * Read and write needs * Total storage requirements * Typical object size and nature of access to these objects * Durability requirements * Latency requirements * Maximum concurrent users to support * Nature of queries * Required strength of integrity controls ### Avoiding Single Points of Failure

### Caching

### AWS Infrustructure Topics

{% embed url="" %}