blob: a25f9ef33bfa411d4f551972d924ba71cc5ed766 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
---
title: Managing AWS secrets
description: with the CLI and with terraform/OpenTofu
date: 2024-08-13
tags:
- aws
- OpenTofu
- terraform
---
## Introduction
Managing secrets in AWS is not an everyday task that allows me to naturally remember the specifics when I need them, especially the `--name` and `--secret-id` CLI inconsistency. I found I was lacking some simple notes that would prevent me from having to search the web in the future, here they are.
## CLI
### Creating secrets
From a simple string:
``` shell
aws --profile common secretsmanager create-secret \
--name test-string \
--secret-string 'test'
```
From a text file:
``` shell
aws --profile common secretsmanager create-secret \
--name test-text \
--secret-string "$(cat ~/Downloads/adyxax.2024-07-31.private-key.pem)"
```
For binary file we `base64` encode the data:
``` shell
aws --profile common secretsmanager create-secret \
--name test-binary \
--secret-binary "$(cat ~/Downloads/some-blob|base64)"
```
### Updating secrets
Beware that all the other aws secretsmanager commands use the `--secret-id` flag instead of the `--name` we needed when creating the secret.
Update a secret string with:
``` shell
aws --profile common secretsmanager update-secret \
--secret-id test-string \
--secret-string 'test'
```
### Reading secrets
Listing:
``` shell
aws --profile common secretsmanager list-secrets | jq -r '[.SecretList[].Name]'
```
Getting a secret value:
``` shell
aws --profile common secretsmanager get-secret-value --secret-id test-string
```
### Deleting secrets
``` shell
aws --profile common secretsmanager delete-secret --secret-id test-string
```
## Terraform
### Resource
Secret string:
``` hcl
resource "random_password" "main" {
length = 64
special = false
lifecycle {
ignore_changes = [special]
}
}
resource "aws_secretsmanager_secret" "main" {
name = "grafana-admin-password"
}
resource "aws_secretsmanager_secret_version" "main" {
secret_id = aws_secretsmanager_secret.main.id
secret_string = random_password.main.result
}
```
Secret binary:
``` hcl
resource "random_bytes" "main" {
length = 32
}
resource "aws_secretsmanager_secret" "main" {
name = "data-encryption-key"
}
resource "aws_secretsmanager_secret_version" "main" {
secret_id = aws_secretsmanager_secret.main.id
secret_binary = random_bytes.main.base64
}
```
### Datasource
``` hcl
data "aws_secretsmanager_secret_version" "main" {
secret_id = "test"
}
```
Using the datasource differs if it contains a `secret_string` or a `secret_binary`. In most cases you will know your secret data therefore know which one to use. If for some reason you do not, this might be one of the rare legitimate use cases for the [try function](https://developer.hashicorp.com/terraform/language/functions/try):
``` hcl
try(
data.aws_secretsmanager_secret_version.main.secret_binary,
data.aws_secretsmanager_secret_version.main.secret_string,
)
```
## Conclusion
Once upon a time I wrote many small and short articles like this one but for some reason stopped. I will try to take on this habit again.
|
