Tuesday 18 July 2017

Amazon Web Services - Identity Access Management

What is IAM?

Essentially, IAM allows you to manage users and their level of access to the AWS Console. It is important to understand IAM and how it works, both for the exam and for administration a company's AWS account in real life.

What does IAM gives you?
  • Centralised control of your AWS account 
  • Shared Access to you AWS account
  • Granular Permissions
  • Identity Federation( including Active Directory, Facebook, Linkedin etc)
  • Multifactor Authentication
  • Provide temporary access of users/devices and services where necessary
  • Allows you to set up your own password rotation policy 
  • Integrates with many different AWS services
  • Supports PCI DSS Compliance

Critical Terms:
  • Users - End Users (think people)
  • Groups - A collection of users under one set of permissions.
  • Roes - You create roles and can then assign them to AWS resources.
  • Policies - A document that defines one (or more permissions)

LAB:

Create Groups: An IAM group is a collection of IAM users. Groups let you specify permissions for multiple users, which can make it easier to manage the permissions for those users. For example, you could have a group called Admins and give that group the types of permissions that administrators typically need. Any user in that group automatically has the permissions that are assigned to the group.
  1. SG_SYSTEM_ADMIN
  2. SG_S3_RW
  3. SG_S3_R

Create User:
  1. SANDEEP - SG_SYSTEM_ADMIN
  2. PAWAN - SG_S3_RW
  3. POONAM - SG_S3_RW
  4. ISHAN - SG_S3_RW
  5. HIMANSHU - SG_S3_R
  6. JITENDER - SG_S3_R
  
Create Roles: it a way to allow one AWS service to interact with another AWS service.
S3-ADMIN-ACCESS

Policy / Permissions:
Can add permissions to individually or to group.
  1. AmazonGlacierReadOnlyAccess - AWS Managed Policy
  2. IAMUserChangePassword - AWS Manage Policy
  3. AmazonS3ReadOnlyAccess - AWS Manage Policy from group HR

IAM Consists of the below:
  1. Users
  2. Groups (A way to group our users and apply polices to them collectively)
  3. Roles
  4. Policy Documents (json doc)
  5. IAM is universal. It does not apply to regions at this time.
  6. The root account is simply the account created when first setup AWS account. It has complete Admin access. 
  7. New users has NO permissions when first created.
  8. New users are assigned Access Key ID & Secret Access Keys when first created. You can use this to access AWS via the APIs and command line.
  9. You only get to view these once. If you loose them, you have to regenerate them. So save them in a secure location. 
  10. Always setup Multifactor Authentication on your root account.
  11. You can create and customise your own password rotation policies.




No comments:

Post a Comment

Jenkins Startup and Configuration

Steps to setup jenkins on ubuntu:- -After installation. check the jenkins services running on not on the server. sudo service jenk...