AWS Identity & Access Management

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/49

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

50 Terms

1
New cards

IAM

Identity and Access Management, It lets you create and manage users, groups, roles, and permissions to control who can do what in your AWS environment.

2
New cards

Root account

Default AWS account created with AWS setup; should not be used or shared.

3
New cards

Why shouldn't the root account be used?

It's a best practice to avoid using the root account because it has full, unrestricted access and cannot be limited—using it increases the risk of accidental or malicious changes.

4
New cards

User (IAM)

An individual identity in AWS with specific credentials (username, password, access keys) used to access and interact with AWS services.

5
New cards

Group (IAM)

A collection of users; cannot contain other groups.

6
New cards

Can users belong to multiple groups?

Yes, users can belong to multiple groups or none at all.

7
New cards

Why create users and groups in AWS?

To securely manage individual access and simplify permission management for a collection of users.

8
New cards

Policy (IAM)

JSON documents that define permissions for users or groups.

9
New cards

What principle should policies follow in AWS?

Least privilege—users get only the permissions they need.

10
New cards

What is IAM policy inheritance?

Users inherit policies attached to their group.

11
New cards

What are inline policies in IAM?

Policies directly attached to individual users.

12
New cards

What are the main components of an IAM policy?

Version, Id (optional), Statement(s).

13
New cards

What does an IAM policy Statement include?

Sid (optional), Effect (Allow/Deny), Principal, Action, Resource, Condition (optional).

14
New cards

What is the recommended version for IAM policies?

"2012-10-17"

15
New cards

Why enforce a strong password policy in AWS?

To increase account security.

16
New cards

What can AWS password policies enforce?

Minimum length, character types, password changes, expiration, reuse prevention.

17
New cards

What is MFA in AWS?

Multi-Factor Authentication combines password + physical device for security.

18
New cards

Why use MFA?

If password is compromised, attacker still needs physical device to access account.

19
New cards

Name some virtual MFA devices.

Google Authenticator, Authy.

20
New cards

What is a U2F security key?

A hardware device supporting multiple users, e.g. YubiKey.

21
New cards

Give an example of hardware MFA key fobs.

Gemalto, SurePassId.

22
New cards

How can users access AWS?

AWS Management Console (password + MFA), AWS CLI (access keys), AWS SDK (access keys).

23
New cards

What are access keys in AWS?

Secret credentials like a username (Access Key ID) and password (Secret Access Key) for CLI/SDK.

24
New cards

How should access keys be treated?

As secrets; never share them.

25
New cards

What is the AWS CLI?

A command-line tool to interact with AWS services via public APIs.

26
New cards

Why use AWS CLI?

To script and manage AWS resources as an alternative to the Console.

27
New cards

What is the AWS SDK?

Language-specific libraries to programmatically access AWS services.

28
New cards

Which languages are supported by AWS SDK?

JavaScript, Python, PHP, .NET, Ruby, Java, Go, Node.js, C++, and mobile/IoT SDKs.

29
New cards

What is AWS CloudShell?

A browser-based shell inside AWS Console for managing AWS resources.

30
New cards

Name key features of AWS CloudShell.

Pre-authenticated with IAM credentials, pre-installed tools, 1 GB persistent storage, secure isolated environment.

31
New cards

Why do some AWS services need IAM roles?

To perform actions on your behalf securely with assigned permissions.

32
New cards

What is an IAM role?

A set of permissions assigned to AWS services to act on your account.

33
New cards

Name common AWS service roles.

EC2 instance roles, Lambda function roles, CloudFormation roles.

34
New cards

What is the IAM Credentials Report?

A report listing all users and the status of their credentials at the account level.

35
New cards

What does IAM Access Advisor (last-access) show?

Permissions granted to a user and when those services were last accessed.

36
New cards

Why use IAM Access Advisor?

To review and refine user permissions.

37
New cards

What is a key best practice for the root account?

Only use it for AWS account setup; avoid regular use.

38
New cards

What is the recommended user-to-AWS-user ratio?

One physical user should have one AWS user account.

39
New cards

How should permissions be assigned?

Assign users to groups, and assign permissions to groups.

40
New cards

Why create a strong password policy?

To enhance account security.

41
New cards

What security feature should be enforced on IAM users?

Multi-Factor Authentication (MFA).

42
New cards

When should you use IAM Roles?

To give permissions to AWS services securely.

43
New cards

What is the use of Access Keys?

For programmatic access via CLI and SDK.

44
New cards

How do you audit AWS permissions?

Use IAM Credentials Report and IAM Access Advisor.

45
New cards

What is a critical sharing rule for IAM?

Never share IAM users or access keys.

46
New cards

What security responsibilities does AWS have?

Infrastructure security, service configuration/vulnerability analysis, compliance validation.

47
New cards

What security responsibilities do you have?

Manage users/groups/roles/policies, enable MFA, rotate keys, apply least privilege, review permissions.

48
New cards

What is recommended for key management?

Rotate all your keys often.

49
New cards

What should you use to apply appropriate permissions?

AWS IAM tools.

50
New cards

Why analyze access patterns?

To review and adjust permissions for security.