mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-01 11:08:10 +00:00
Add Quick Start for AWS
This commit is contained in:
@@ -20,4 +20,80 @@ on every path, use `vault help` after mounting the backend.
|
|||||||
|
|
||||||
## Quick Start
|
## Quick Start
|
||||||
|
|
||||||
TODO
|
Mount the aws secret backend using the `vault mount` command:
|
||||||
|
|
||||||
|
```text
|
||||||
|
$ vault mount aws
|
||||||
|
Successfully mounted 'aws' at 'aws'!
|
||||||
|
```
|
||||||
|
|
||||||
|
Configure the root credentials that are used to manage IAM credentials:
|
||||||
|
|
||||||
|
```text
|
||||||
|
$ vault write aws/config/root \
|
||||||
|
access_key=AKIAJWVN5Z4FOFT7NLNA \
|
||||||
|
secret_key=R4nm063hgMVo4BTT5xOs5nHLeLXA6lar7ZJ3Nt0i \
|
||||||
|
region=us-east-1
|
||||||
|
```
|
||||||
|
|
||||||
|
The following parameters are required:
|
||||||
|
|
||||||
|
- `access_key` - the AWS access key that has permission to manage IAM
|
||||||
|
credentials.
|
||||||
|
- `secret_key` - the AWS secret key that has permission to manage IAM
|
||||||
|
credentials.
|
||||||
|
- `region` the AWS region for API calls.
|
||||||
|
|
||||||
|
Create an IAM policy:
|
||||||
|
|
||||||
|
```text
|
||||||
|
$ vault write aws/policy/deploy \
|
||||||
|
name=deploy \
|
||||||
|
policy=@policy.json
|
||||||
|
```
|
||||||
|
|
||||||
|
This path will generate a new, never before used key pair for
|
||||||
|
accessing AWS. The IAM policy used to back this key pair will be
|
||||||
|
the "name" parameter, which is "deploy" in this example.
|
||||||
|
|
||||||
|
The `@` tells Vault to load the policy from the file named `policy.json`. Here
|
||||||
|
is an example IAM policy to get started:
|
||||||
|
|
||||||
|
```javascript
|
||||||
|
{
|
||||||
|
"Version": "2012-10-17",
|
||||||
|
"Statement": {
|
||||||
|
"Effect": "Allow",
|
||||||
|
"Action": "iam:*",
|
||||||
|
"Resource": "*"
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
For more information on IAM policies, please see the
|
||||||
|
[AWS IAM policy documentation](http://docs.aws.amazon.com/IAM/latest/UserGuide/PoliciesOverview.html).
|
||||||
|
|
||||||
|
Vault can now generate IAM credentials under the given policy:
|
||||||
|
|
||||||
|
```text
|
||||||
|
$ vault read aws/deploy
|
||||||
|
Key Value
|
||||||
|
lease_id aws/deploy/7cb8df71-782f-3de1-79dd-251778e49f58
|
||||||
|
lease_duration 3600
|
||||||
|
access_key AKIAIOMYUTSLGJOGLHTQ
|
||||||
|
secret_key BK9++oBABaBvRKcT5KEF69xQGcH7ZpPRF3oqVEv7
|
||||||
|
```
|
||||||
|
|
||||||
|
If you run the command again, you will get a new set of credentials:
|
||||||
|
|
||||||
|
```text
|
||||||
|
$ vault read aws/deploy
|
||||||
|
Key Value
|
||||||
|
lease_id aws/deploy/82d89562-ff19-382e-6be9-cb45c8f6a42d
|
||||||
|
lease_duration 3600
|
||||||
|
access_key AKIAJZ5YRPHFH3QHRRRQ
|
||||||
|
secret_key vS61xxXgwwX/V4qZMUv8O8wd2RLqngXz6WmN04uW
|
||||||
|
```
|
||||||
|
|
||||||
|
If you get stuck at any time, simply run `vault help aws` or with a subpath for
|
||||||
|
interactive help output.
|
||||||
|
|||||||
Reference in New Issue
Block a user