Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Tal authored Aug 28, 2017
1 parent 047d9e6 commit 7a9e8a3
Showing 1 changed file with 19 additions and 13 deletions.
32 changes: 19 additions & 13 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,36 +2,35 @@

## Motivation

Many startups are now setting up on aws infrastructure and its long before they figure out importance of IAM role, to be fair its of least importance initially because its not worth the time and energy, businesses initially should focus on product itself. But what if there was hand holding and it won't take too much time to setup IAM roles. After all you want to be secure in initial phases. Forget startups even midsize and some large companies make this mistake and later it becomes too much tech debt.
Many startups are now setting up on AWS infrastructure, but it’s long before they figure out the importance of IAM’s role. To be fair, it’s of least importance initially, as the necessary time and energy are hard to justify. Rather, businesses should first focus on the product itself. But imagine if there was a hand holding the business owner, making the setup of IAM roles expedient and easy. After all, security is your priority at the outset. Let alone startups, even midsize and some large companies make this crucial mistake and accumulate large tech debt.

This project focuses on creating skeleton of IAM Roles for startups with which they can get started with little or no modifications. The project focuses on multi size startups.
This project focuses on creating a skeleton of IAM roles for startups, with the ability to get started with little or no modifications. The project focuses on multi-size startups:

- Small - 5 people
- Midsize - 12 people
- Midsize - ~12 people
- Large - 40 or above

## Role of security
## Role of Security

In this project we trying keep security above everything, we are trying to avoid accidental deletions. We are assuming that every team member will logging in from known IPs. As added layer of security we are making MFA mandatory for every user that logs in, even admins.
In this project, we try to place security above everything. We are trying to avoid accidental deletions. We are assuming that every team member will log in from known IPs. As an added layer of security, we are making MFA mandatory for every user that logs in, even admins.

## Assumptions

We are working with following assumtions:
We are working with the following assumptions:

- We are assuming generic job roles.
- In case an employees is wearing multiple hats, make sure you
- update the accordingly. We have tried to block certain destructive actions like bucket deletion, accidental terminations for users who are not aws admin like frontend, backend engineers.
- We have tried to blacklist instead of whitelist to keep the roles look more clean.
Presence of generic job roles.
In case an employee is wearing multiple hats, make sure you update accordingly. We have tried to block certain destructive actions like bucket deletion, accidental terminations for users who are not AWS admin like frontend and backend engineers.
Use of blacklist instead of whitelist to keep the roles tidy.

## Job Profiles

We are considering job profiles across different verticals i.e: business, finance, tech and ops.
We are considering job profiles across different verticals, i.e: business, finance, tech and ops.

read [ROLES.md](https://github.com/Singapore-Tech-Entrepreneurs/Startup-AWS-IAM-Roles/blob/master/ROLES.md) for role and its assumption details.

## Setting up Roles
## Setting Up Roles

Create groups based on job profiles and attach policy documents from this project to it. Now create users and assign them to these groups.
Create groups based on job profiles and attach policy documents from this project. Then create users and assign them to these groups.

## Contributing

Expand All @@ -41,3 +40,10 @@ Create groups based on job profiles and attach policy documents from this projec
- Commit your changes: git commit -m 'feat: add new feature' -m 'add my-new-feature, use it as: my-new-feautre(args)' -m 'closes #26'
- Push to the branch: git push origin my-new-feature
- Submit a pull request :D


## Contributors

- Padmakar Ojha @dvopsway
- Michael Amurjuev @LawTech Enthusiast
- Kj Venky @kjvenky

0 comments on commit 7a9e8a3

Please sign in to comment.