Skip to content

Commit 311596a

Browse files
docs: Fix STS commands for self-hosted and indentation corrections (#8756) (#8767)
(cherry picked from commit a97216c) Co-authored-by: Ben Radstone <[email protected]>
1 parent b6aeec1 commit 311596a

File tree

1 file changed

+39
-39
lines changed

1 file changed

+39
-39
lines changed

_partials/self-hosted/_aws-sts-config.mdx

Lines changed: 39 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -35,52 +35,52 @@ to deploy clusters in AWS using STS. Without this configuration, the STS option
3535
--data '{
3636
"username": "**********",
3737
"password": "**********"
38-
}' | jq ."Authorization")
38+
}' | jq -r ."Authorization")
3939
```
4040

4141
3. Next, prepare a payload for the AWS account you want to configure.
4242
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.
4343

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+
```
5454

5555
This avoids exposing sensitive information in the command line.
5656

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.
5858

59-
<Tabs>
59+
<Tabs>
6060

61-
<TabItem value="AWS">
61+
<TabItem value="AWS">
6262

63-
```bash
64-
curl --request POST \
65-
--url https://<palette-api-url>/v1/system/config/aws/sts/account \
66-
--header 'Authorization: $TOKEN' \
67-
--data '$CONFIG_JSON'
68-
```
63+
```bash
64+
curl --request POST \
65+
--url https://<palette-api-url>/v1/system/config/aws/sts/account \
66+
--header "Authorization: $TOKEN" \
67+
--data "$CONFIG_JSON"
68+
```
6969

70-
</TabItem>
70+
</TabItem>
7171

72-
<TabItem value="AWS GOV">
72+
<TabItem value="AWS GOV">
7373

74-
```bash
75-
curl --request POST \
76-
--url https://<palette-api-url>/v1/system/config/awsgov/sts/account \
77-
--header 'Authorization: $TOKEN' \
78-
--data '$CONFIG_JSON'
79-
```
74+
```bash
75+
curl --request POST \
76+
--url https://<palette-api-url>/v1/system/config/awsgov/sts/account \
77+
--header "Authorization: $TOKEN" \
78+
--data "$CONFIG_JSON"
79+
```
8080

81-
</TabItem>
81+
</TabItem>
8282

83-
</Tabs>
83+
</Tabs>
8484

8585

8686
## Validate
@@ -97,15 +97,15 @@ to deploy clusters in AWS using STS. Without this configuration, the STS option
9797
--data '{
9898
"password": "**********",
9999
"username": "**********"
100-
}')
101-
102-
2. Issue the following command to make an API call that confirms that the credentials were configured successfully.
100+
}' | jq -r ."Authorization")
101+
```
103102

104-
```shell
105-
curl --request GET \
106-
--url https://<palette-api-url>/v1/system/config/aws/account \
107-
--header 'Authorization: $TOKEN'
108-
```
103+
3. Issue the following command to make an API call that confirms that the credentials were configured successfully.
109104

110-
If you receive a response that contains the payload you configured, the configuration was successful.
105+
```shell
106+
curl --request GET \
107+
--url https://<palette-api-url>/v1/system/config/aws/account \
108+
--header "Authorization: $TOKEN"
109+
```
111110

111+
If you receive a response that contains the payload you configured, the configuration was successful.

0 commit comments

Comments
 (0)