Amazon Web Services(AWS):Tutorial 1

Whippyminds are coming up with a separate section for Courses and Tutorials on a wide variety of subjects. We are keeping this entire initiative to be completely free. Similar to our other blogs our intention is to provide world class educational content to our readers in an easy to understand format. We are starting with a series of tutorial-blogs on Amazon Web Services. Kindly let let us know your suggestions in the comments.

Amazon Web Services(AWS):Tutorial 1


  • Amazon Web Services is a cloud service provider which means that they provide us with servers and services(like Machine Learning Tools, Data Storage Facility etc.) that we can use on-demand and scale our products/business easily. AWS is the largest cloud service provider in the world and is used by some of the biggest companies like, Netflix.

  • AWS has Regions all around the world, whose names are: us-east-1, eu-west-3 etc. 
  • A region is a cluster of data centers. Most AWS services are region-scoped.
  • Each region has many availability zones (usually 3, min is 2, max is 6). e.g. ap-southeast-2a, ap-southeast-2b, ap-southeast-2c. Each availability zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity. These AZ are separate from each other and in separate geographical regions, so that they remain isolated from disasters and thus adds extra layer of security to our data. However, they are connected with high bandwidth, ultra-low latency network connection.
Now let's look into a very important AWS feature.


  • IAM stands for Identity and Access Management. It contains your whole AWS security i.e. Users, Groups, Roles etc. 
  • IAM has a Root account which should never be used (and shared). Users must be created with proper permissions in accordance with their roles.
  • You can configure your IAM Policies. Policies are written in JSON (JavaScript Object Notation). Permissions are governed by these JSON Policies.
  • Big enterprises usually integrate their own repository of users with IAM. This way, one can login into AWS using their company credentials. 
  • Few points to keep in mind:-
    • One IAM User per PHYSICAL PERSON.
    • One IAM Role per Application.
    • IAM credentials should NEVER BE SHARED.
    • Never, ever write IAM credentials in code.
    • And even less, NEVER EVER EVER COMMIT YOUR IAM credentials.
    • Never use the ROOT account except for initial setup.
    • Never use ROOT IAM Credentials.
We will learn more about IAM policies in details in the future. As a rule of thumb it is best to give users the minimal amount of permissions they need to perform their job also called the least privilege principles.

More stuff in Tutorial 2. Coming soon!

NOTE:- You can get all the cool plugins for your own blog/project on this website srmehranclub at 80-90% discount.