# Copy of 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>           |

***


---

# Agent Instructions: 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-1-design-secure-architectures/copy-of-task-statement-1.1-design-secure-access-to-aws-resources.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.