mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-16 03:27:01 +02:00
d206599b80
The new STS path allows for obtaining the same credentials that you would get from the AWS "creds" path, except it will also provide a security token, and will not have an annoyingly long propagation time before returning to the user.
63 lines
1.7 KiB
Go
63 lines
1.7 KiB
Go
package aws
|
|
|
|
import (
|
|
"fmt"
|
|
|
|
"github.com/hashicorp/vault/logical"
|
|
"github.com/hashicorp/vault/logical/framework"
|
|
)
|
|
|
|
func pathSTS(b *backend) *framework.Path {
|
|
return &framework.Path{
|
|
Pattern: "sts/" + framework.GenericNameRegex("name"),
|
|
Fields: map[string]*framework.FieldSchema{
|
|
"name": &framework.FieldSchema{
|
|
Type: framework.TypeString,
|
|
Description: "Name of the role",
|
|
},
|
|
},
|
|
|
|
Callbacks: map[logical.Operation]framework.OperationFunc{
|
|
logical.ReadOperation: b.pathSTSRead,
|
|
},
|
|
|
|
HelpSynopsis: pathSTSHelpSyn,
|
|
HelpDescription: pathSTSHelpDesc,
|
|
}
|
|
}
|
|
|
|
func (b *backend) pathSTSRead(
|
|
req *logical.Request, d *framework.FieldData) (*logical.Response, error) {
|
|
policyName := d.Get("name").(string)
|
|
|
|
// Read the policy
|
|
policy, err := req.Storage.Get("policy/" + policyName)
|
|
if err != nil {
|
|
return nil, fmt.Errorf("error retrieving role: %s", err)
|
|
}
|
|
if policy == nil {
|
|
return logical.ErrorResponse(fmt.Sprintf(
|
|
"Role '%s' not found", policyName)), nil
|
|
}
|
|
|
|
// Use the helper to create the secret
|
|
return b.secretAccessKeysAndTokenCreate(
|
|
req.Storage, req.DisplayName, policyName, string(policy.Value))
|
|
}
|
|
|
|
const pathSTSHelpSyn = `
|
|
Generate an access key pair + security token for a specific role.
|
|
`
|
|
|
|
const pathSTSHelpDesc = `
|
|
This path will generate a new, never before used key pair + security token for
|
|
accessing AWS. The IAM policy used to back this key pair will be
|
|
the "name" parameter. For example, if this backend is mounted at "aws",
|
|
then "aws/sts/deploy" would generate access keys for the "deploy" role.
|
|
|
|
Note, these credentials are instantiated using the AWS STS backend.
|
|
|
|
The access keys will have a lease associated with them. The access keys
|
|
can be revoked by using the lease ID.
|
|
`
|