Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[version-4-3] docs: aws sts creds (#5135) #5139

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 22 additions & 7 deletions _partials/self-hosted/_aws-sts-config.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -85,12 +85,27 @@ to deploy clusters in AWS using STS. Without this configuration, the STS option

## Validate

Issue the following command to make an API call that confirms that the credentials were configured successfully.
1. Open a terminal session.

```bash
curl --request POST \
--url https://<palette-api-url>/v1/system/config/aws/account \
--header 'Authorization: $TOKEN'
```
2. Log in to the {props.edition} System API by using the `/v1/auth/syslogin` endpoint.
Use the curl command below and replace the `example.com` placeholder URL with the URL of your {props.edition} instance.
Ensure you replace the credentials below with your system console credentials.

```shell
TOKEN=$(curl --insecure --location 'https://example.com/v1/auth/syslogin' \
--header 'Content-Type: application/json' \
--data '{
"password": "**********",
"username": "**********"
}')

2. Issue the following command to make an API call that confirms that the credentials were configured successfully.

```shell
curl --request GET \
--url https://<palette-api-url>/v1/system/config/aws/account \
--header 'Authorization: $TOKEN'
```

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

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