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: _partials/self-hosted/_aws-sts-config.mdx
+39-39Lines changed: 39 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,52 +35,52 @@ to deploy clusters in AWS using STS. Without this configuration, the STS option
35
35
--data '{
36
36
"username": "**********",
37
37
"password": "**********"
38
-
}'| jq ."Authorization")
38
+
}'| jq -r ."Authorization")
39
39
```
40
40
41
41
3. Next, prepare a payload for the AWS account you want to configure.
42
42
Use the following JSON payload as a template and replace the `accessKey`, `secretKey`, and `accountId` fields with the AWS access key, secret key, and account ID of your AWS account.
43
43
44
-
```json
45
-
CONFIG_JSON=$(cat <<EOF
46
-
{
47
-
"accessKey": "**********",
48
-
"secretKey": "**********",
49
-
"accountId": "123456789"
50
-
}
51
-
EOF
52
-
)
53
-
```
44
+
```json
45
+
CONFIG_JSON=$(cat <<EOF
46
+
{
47
+
"accessKey": "**********",
48
+
"secretKey": "**********",
49
+
"accountId": "123456789"
50
+
}
51
+
EOF
52
+
)
53
+
```
54
54
55
55
This avoids exposing sensitive information in the command line.
56
56
57
-
2. Issue the following command to invoke the {props.edition} API to configure the AWS account to your instance.
57
+
4. Issue the following command to invoke the {props.edition} API to configure the AWS account to your instance.
0 commit comments