> 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-1-design-secure-architectures/task-statement-1.1-design-secure-access-to-aws-resources.md).

# Task Statement 1.1: Design secure access to AWS resources

We will explore how SecureCart, a growing e-commerce company, builds secure access to AWS resources using best practices, role-based access control (RBAC), multi-account security, and federated access.

We’ll focus on different aspects of AWS Identity & Access Management (IAM), AWS security best practices, and access controls across multiple accounts.

| **Order** | **Topic**                                                  | **Key AWS Services**                                      |
| --------- | ---------------------------------------------------------- | --------------------------------------------------------- |
| **1**     | AWS Identity & Access Management (IAM) Fundamentals        | Users, Groups, Roles, Policies,Federation,Access Analyzer |
| **2**     | Role-Based Access Control (RBAC) and Temporary Credentials | IAM Roles, AWS STS, IAM Policies                          |
| **3**     | Securing Access Across Multiple AWS Accounts               | AWS Organizations, SCPs, AWS Control Tower                |
| **4**     | Federated Access and Directory Services                    | AWS IAM Identity Center (SSO), AWS STS, AD Federation     |
| **5**     | IAM Policies and Resource Policies                         | IAM Conditions, Resource Policies, Access Analyzer        |
| **6**     | Hands-on Labs & Final Challenge                            | <p></p><p>Real-world IAM security scenarios</p>           |

***