Opt into Amazon/Other
When starting a new project we should check the .env file for Amazon/other 3rd party credentials and use them if available and ignore if not. 

The boilerplate sets it up but they are not used directly. I personally like that it is documented on how to set it up and would like a document showing how to move forward with common usage patterns; however, it adds complexity to getting started. It would be nice to: 

```
git clone && npm i 
```

Any objections to this? It would need to throw an error when users are trying to build for production. What else would need to change? 
