aws / aws/aws-toolkit-vscode

"View Full Log Stream" repeatedly timing-out?

Open
#6,605 5 comments 0 reactions 0 assignees View on GitHub
guidance partner-team performance service:cloudwatch ux
Dominant language
TypeScript
Stars
2k
Forks
810
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## System details (run `AWS: About` and/or `Amazon Q: About`)

- OS: Linux x64 6.8.0-53-generic
- Visual Studio Code version: 1.97.2
- AWS Toolkit version: 3.46.0
- Amazon Q version: N/A

## Question

I just discovered "View Full Log Stream" after years of being frustrated that I have to request page after page of CW Log results. But both times that I've tried it, it times out.

FWIW, My .aws/credentials uses credential_process which in turn uses op, the 1Password shell plugin, so I can avoid having unencrypted credentials on-disk.

How can I avoid these timeouts?

2025-02-18 09:28:23.021 [info] Log level: info, beta=false
2025-02-18 09:28:23.021 [info] endpoints: retrieving AWS endpoints data
2025-02-18 09:28:23.021 [info] Telemetry product: AWS Toolkit For VS Code
2025-02-18 09:28:23.285 [info] Telemetry clientId: ec85fada-7876-4528-9a79-8c0ab13bd8bb
2025-02-18 09:28:23.286 [info] Telemetry sessionId: 42d8eab3-3236-41e2-8c2a-d35028b93ff9
2025-02-18 09:28:23.956 [warning] AwsContext: no default region in credentials profile, falling back to us-east-1:
2025-02-18 09:28:25.172 [info] OS: Linux x64 6.8.0-53-generic
2025-02-18 09:28:25.172 [info] Visual Studio Code extension host: 1.97.2
2025-02-18 09:28:25.172 [info] AWS Toolkit: 3.46.0
2025-02-18 09:28:25.172 [info] node: 20.18.1
2025-02-18 09:28:25.172 [info] electron: 32.2.7
2025-02-18 09:28:25.182 [info] initialized 'submitFeedback' command with default feedback id: AWS Toolkit
2025-02-18 09:28:25.213 [info] auth: Updating connection state of profile:default to authenticating
2025-02-18 09:28:40.359 [info] auth: Updating connection state of profile:default to valid
2025-02-18 09:28:40.898 [warning] Ec2MetadataClient failed to fetch token. If this is an EC2 environment, then Toolkit will fall back to IMDSv1: TimeoutError: Socket timed out without establishing a connection ()
2025-02-18 09:28:41.871 [warning] command failed (not registered?): "aws.amazonq.refreshConnectionCallback"
2025-02-18 09:31:32.564 [error] aws.loadLogStreamFile: Error: Timeout token expired
2025-02-18 09:32:40.987 [error] aws.addLogEvents: TypeError: (0 , m.localize) is not a function
2025-02-18 09:33:24.258 [info] telemetry: sent batch (size=18)
2025-02-18 09:34:57.197 [error] aws.loadLogStreamFile: Error: Timeout token expired

Contributor guide

Open the contributing guide

Research direction

Start by reproducing "View Full Log Stream" with the reported Linux, VS Code 1.97.2, and AWS Toolkit 3.46.0 setup, then inspect the log entries for aws.loadLogStreamFile and aws.addLogEvents. Done means identifying the cause of the repeated timeout and confirming that full log streams load without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript, vscode
Domain
cloud, devtools, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.