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.

Sign up for GitHub

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

Jump to bottom

[v14] docs: include sts.amazonaws.com in troubleshooting #43649

Merged
merged 2 commits into from
Jun 28, 2024
Merged

[v14] docs: include sts.amazonaws.com in troubleshooting #43649

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4382d41
docs: include sts.amazonaws.com in troubleshooting
stevenGravy Jun 28, 2024
36670db
docs: update verbiage on connection failure
stevenGravy Jun 28, 2024
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
9 changes: 7 additions & 2 deletions docs/pages/application-access/cloud-apis/aws-console.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -672,10 +672,11 @@ username which you can search for to get the events history:

Read this section if you run into issues while following this guide.

### `Internal Server Error`
### `Internal Server Error` or fails to connect in Web UI

When visiting the AWS Management Console from the Teleport Web UI, you may see
an `InternalServer Error` message instead of the AWS Management Console.
an `InternalServer Error` message or other connection issues instead of the
AWS Management Console.

If this happens, check the Teleport Application Service logs:

Expand All @@ -702,6 +703,10 @@ $ kubectl -n teleport-agent logs statefulset/teleport-kube-agent
If the Teleport Application Service encounters an error sending a request to the
AWS API, the logs will show the error message stack trace.

Within the logs you may see a connection failure such as a i/o timeout
regarding `sts.amazonaws.com:443`. The Teleport Application Service requires
connecting to `https://sts.amazonaws.com` to create an authorized AWS console session.

### The Application Service is not authorized to assume a role

If the Teleport Application Service fails to assume the `ExampleReadOnlyAccess`
Expand Down
Loading