IAM Flashcards

1
Q

In-line Policies Vs Managed Policies

A

Inline policies - attached to individuals/groups and allows for fine grain permissions.

Managed Policies - are applied to User, group, service. Any changes made to managed policies affects all linked principals/services

Managed Policy has its own ARN.

Has permissions for common use cases

Inline policies are useful if you want to maintain a strict one-to-one relationship between a policy and the identity to which it is applied. For example, if you want to be sure that the permissions in a policy are not inadvertently assigned to an identity other than the one they’re intended for. When you use an inline policy, the permissions in the policy cannot be inadvertently attached to the wrong identity. In addition, when you use the AWS Management Console to delete that identity, the policies embedded in the identity are deleted as well because they are part of the principal entity.

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

Authentication

A

Who are you

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

Authorization

A

What are you allowed to do

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

IAM QUOTAS

A

5,000 Users per Account

1user to 10groups Max

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

How do you Authenticate more than 5000 users at a time?

A
  1. IAM Roles
  2. Using Cognito
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Service-Linked Role

A

An IAM administrator can create, modify, and delete a service role from within IAM. A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service.

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

Management Account, Payment Account

A

The account in AWS organization that is billed

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

Access Key confidentiality

A
  • Access key can be public(not delicate), but Secret Keys are meant to be confidential
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Maximum number of access keys allowed per user

A
  • You can create two Access Keys MAX per user (Active or inactive) and this is for the purpose of manual key rotation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Access Keys Best practice

A

Deactivate to suspend Access whenever necessary.

Create two for rotation

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

Access Keys vs Key Pairs

A

Access Key is created to distinguish two types of users, Access keys are for users who have create and own instance. Key pairs are for those who are users of ec2 instance. Users don’t need to share access keys of owner as they don’t need to create resources thus maintaining separation of concern.

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

Default VPC CIDR

A

173.31.0.0/16

173.31.0.0/20
173.31.16.0/20
173.31.32.0/20

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

“sid” in an IAM Policy

A

Statement iD, its like a description string

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

Define Identity Federation

A

The use of IAM to issue temporary access tokens to an external Identity provider so they can access an AWS resource. They Assume the role and carry out their instructions/function.

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

IAM Role use case

A

IAM Role is designed for both AWS Resources and Non-AWS Identities to be able to access aws resources. Eg, an Application with >5,000 users needing to access aws dynamoDb

17
Q

IAM Role Validity

A