You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/backend_guide.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,9 +180,9 @@ data "scaleway_rdb_instance" "mybackend" {
180
180
181
181
## Using s3 compatible backend
182
182
183
-
You can use scaleway object-storage bucket as an S3 compatible backend to store your terraform tfstate file just like you would do with AWS s3
183
+
You can use scaleway object-storage bucket as an S3 compatible backend to store your terraform .tfstate file just like you would do with AWS s3
184
184
185
-
### by using hardcoded credetials (NOT RECOMENDED)
185
+
### by using hardcoded credetials (NOT RECOMMENDED)
186
186
```
187
187
terraform {
188
188
backend "s3" {
@@ -200,7 +200,7 @@ terraform {
200
200
}
201
201
```
202
202
203
-
### by using credetials environment variables
203
+
### by using credentials environment variables
204
204
```
205
205
$ export SCW_ACCESS_KEY="XXXXXXXXXXX"
206
206
$ export SCW_SECRET_KEY="YYYYYYYYYYY"
@@ -218,15 +218,15 @@ terraform {
218
218
```
219
219
220
220
### and with the shared congfiguration file ?
221
-
scaleway scwcli privide you with a credential file
221
+
scaleway scw-cli provide you with a credential file
222
222
>~/$HOME/.config/scw/config.yaml
223
223
224
-
to generate your credential fil you can run scw init at first run or login for every new key pairs generated
224
+
to generate your credential file you can run scw init at first run or login for every new key pairs generated
225
225
```
226
226
scw login
227
227
```
228
228
229
-
it will generate scw shared configuration fil folowinng this format
229
+
it will generate scw shared configuration file folowinng this format
230
230
```
231
231
profiles:
232
232
myProfile1:
@@ -242,7 +242,7 @@ profiles:
242
242
243
243
actualy terraform backend "s3" is not aware of any other kind of s3 compatible bucket and is by default assuming you ar using aws's S3 service
244
244
245
-
so in order to read scw ccredentials, do not try to use `profile = myProfile1` it will not work, unless you copy scw credentials into aws shared configuration file
245
+
so in order to read scw ccredentials, do not try to use `profile = myProfile1` it will not work, unless you can copy your scw credentials into aws shared configuration file
246
246
247
247
>~/$HOME/.aws/credentials
248
248
@@ -268,4 +268,4 @@ terraform {
268
268
}
269
269
}
270
270
```
271
-
now run terraform init and backend s3 should be able to use scaleway object storage instead of aws s3.
271
+
now run terraform init and the s3 backend should be able to use scaleway object storage instead of aws s3.
0 commit comments