Section 2: IAM Flashcards

1
Q

SAA - CO3

A

30% Domain 1: Design Secure Architectures

26% Domain 2: Design Resilient Architectures

24% Domain 3: Design High-Performing Architectures

20% - Domain 4: Design Cost-Optimized Architectures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

VPC Interface Endpoint vs VPC Gateway Endpoint

A

https://digitalcloud.training/vpc-interface-endpoint-vs-gateway-endpoint-in-aws/

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Principal

A

A person or application that can make a request for an action or operation on an AWS resource

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

AWS Global Accelerator

A

a service that improves the availability and performance of applications with local or global users. It provides static IP addresses that act as a fixed entry point to application endpoints in a single or multiple AWS Regions, such as Application Load Balancers, Network Load Balancers or EC2 instances.

https://digitalcloud.training/amazon-route-53/

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Policy

A

Define the PERMISSIONS for the IDENTITIES or RESOURCES they are associated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Role

A

Used for DELEGATION and are ASSUMED.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Do you need to select a region with IAM?

A

No

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Trust Policy

A

Controls who can assume the role.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

AWS Security Token Service (STS)

A

Enables temporary, limited-privilege credentials to be used with identity federation / federated users, delegation, cross-account access, and IAM users / roles.

?Enables temporary, limited-privileges for IAM users and federated users. Users here and roles above from Lesson 25 - Quiz.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

AWS Security Token Service (STS) credentials include:

A
  • AccessKeyId
  • SecretAccessKey
  • Expiration
  • SessionToken

*Put in credentials file and make a profile, but they are temporary

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Federated User

A

A user outside AWS.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Temporary credentials are used with:

A

Identity Federation
Delegation
Cross-Account Access
IAM Roles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Identity-Based IAM Policies

A

JSON permissions policy documents that control what actions an identity can perform, on which resources, and under what conditions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Inline Policy

A

1:1 relationship with User, Group or Role

Lesson 18

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Managed Policy

A

AWS managed (cannot modify) or customer managed which can be attached to multiple entities (User, Group, Role).

Lesson 18

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Resource Policy

A

Attached to a resource; define permissions for a Principal accessing the resource.

JSON permissions policy documents that you attach to a resource such as an Amazon S3 bucket.

Example: ars:aws:iam::[accountId]:user/Eric

Grant the specified Principal (Eric) the permisson to perform specific actions on the resource.

Lesson 18, 20(review)

17
Q

IAM Role (construction hat)

A

Have a Trust Policy and a Permission Policy.

Lesson 18

18
Q

Trust Policy

A

Is an example of a Resource Policy.

Lesson 18

19
Q

Permissions Policy

A

Is an Identity Policy.

Lesson 18

20
Q

IAM Permissions Boundary

A

Sets the maximum permissions the entity (User or Role) can have.

Set the maximum permissions an Identity Policy can grant an IAM entity.

Lesson 19, 20

21
Q

Steps for Authorizing Request to AWS

A
  1. AWS IAM authenticates the Principal that makes the request.
  2. Request context (Actions, Resources, Principal, Environment data, Resource data) must be processed.
  3. Identity and Resource Policies must be evaluated.
  4. Then the Action will be allowed/denied.

Lesson 20

22
Q

Identity Policy

A

Attached to Users, Groups or Roles.

Lesson 20

23
Q

AWS Organizations Service Control Policies (SCP)

A

Specifies the maximum permissions for an Organization or OU.

Lesson 20

24
Q

AWS Organizations

A

A way to centrally manage multiple AWS accounts. And you can apply policies to those accounts, which determine the maximum available permission.

Lesson 20

25
Q

Session Policies

A

Used with the *AssumeRole API.

Lesson 20

26
Q

Determination Rules

A
  1. By default, all requests are implicitly denied (though the root user has full access).
  2. An explicit allow in an identity-based or resource-based policy overrides this default.
  3. If a permissions boundary, Organization’s SCP, or session policy is present, it might override the allow with an implicit deny.
  4. An implicit deny in any policy overrides any allows.

Lesson 20 (Evaluation Logic slide)

27
Q

Evaluation Logic

A
  1. Deny evaluation (No)
  2. Organizational SCP Yes)
  3. Resource Policy (No)
  4. IAM Permissions Boundaries (Yes)
  5. Session Policies (Yes)
  6. Identity Policy (Yes)

Lesson 20 (slide)

28
Q

IAM Policy Structure

A

JSON

Effect - Allow/Deny
Action - AWS API
Resource - arn
Condition - Control when policy in effect - {conditionName {key:value}}

Lesson 21

29
Q

IAM Best Practices

A
  1. Lock away your AWS account root user access keys.
  2. Create individual IAM users.
  3. Use Groups to assign permissions to IAM Users.
  4. Grant least privilege.
  5. Get started using permissions with AWS Managed Policies.
  6. Use customer managed policies instead of inline policies (assigning a policy directly to a user).
  7. Use access levels to review IAM permissions.
  8. Configure a strong password policy for your users.
  9. Enable MFA.
  10. Use Roles for applications that on EC2 instances.
  11. Use Roles to delegate permissions.
  12. Do not share access keys.
  13. Rotate credentials regularly.
  14. Remove unnecessary credentials.
  15. Use policy conditions for extra security.
  16. Monitor activity in your AWS account.

Lesson 23

30
Q

Group

A
  • Collection if users and have policies attached to them.
  • a group is not an identity and cannot be identified as a Principal in an IAM policy.
  • use Groups to assign permissions to Users.
  • use the principle of least privilege when assigning permissions.
  • Groups cannot be nested (Groups within Groups).

Lesson 24

31
Q

IAM Cheat Sheet

A
32
Q

Root account best practices

A
  • remove access keys
  • set a complex
  • enable MFA
  • use IAM users for most operations.

Lesson Quiz