Skip to content

Commit

Permalink
added "Why?" section
Browse files Browse the repository at this point in the history
  • Loading branch information
ckelner committed Jan 17, 2016
1 parent 883e430 commit 391468f
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ The latest deployed version can be found at: [http://awsresco.s3-website-us-east
- [How it works](#how-it-works)
- [Security?](#security)
- [AWS IAM Policy for access](#aws-iam-policy-for-access)
- [Why?](#why)
- [Gaps](#gaps)
- [Screenshots](#screenshots)
- [Development](#development)
Expand Down Expand Up @@ -49,6 +50,9 @@ The policy you use for AWSResco should follow the least privilege access rules.
}
```

## Why?
In my time with working with AWS, the question of "Am I utilizing my reservations correctly?" has come up many times. AWS doesn't provide an interface, tool, or output that I am aware of that can provide this information in an easily consumable way.

## Gaps
Currently AWSResco does not take into account `OfferingType`, it assumes that only `"Heavy Utilization"` is being used as that was the original use case for the tool. There are plans to support all `OfferingType` variations - see [Issue#3](https://github.com/ckelner/AWSResco/issues/3).

Expand Down

0 comments on commit 391468f

Please sign in to comment.