this will give people some basic idea of using the dotenv file
This commit is contained in:
12
README.md
12
README.md
@@ -3,6 +3,14 @@ Weird AWS Attack Library (AAL)
|
||||
|
||||
<img src="http://earnthis.net/wp-content/uploads/2013/12/150490_large.jpg" align="center" height="240" width="350">
|
||||
|
||||
# Credentials
|
||||
|
||||
You will want to copy the `env.sample` file over to a `.env` file in your weirdAAL directory. Then place the relevant keys where applicable. Example:
|
||||
|
||||
```bash
|
||||
weirdAAL$ cp env.sample .env
|
||||
```
|
||||
|
||||
# Examples
|
||||
|
||||
## IAM
|
||||
@@ -18,7 +26,3 @@ Weird AWS Attack Library (AAL)
|
||||
## EC2
|
||||
- ec2_review_encrypted_volumes.py -- review ec2 instances for encryption status -write out unencrypted ones to file
|
||||
(port of https://gist.github.com/cktricky/0fa3b13ca4306bcd1ec384e88eac3f55)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
3
env.sample
Normal file
3
env.sample
Normal file
@@ -0,0 +1,3 @@
|
||||
[default]
|
||||
aws_access_key_id = <insert key id>
|
||||
aws_secret_access_key = <insert secret key>
|
||||
Reference in New Issue
Block a user