Skip to content

AWS Connection not working anymore #6040

@ruipinto-pleo

Description

@ruipinto-pleo

Describe the bug
AWS Connection doesn't seem to be working with both JVM apps or the terminal.

To reproduce

  1. "Open AWS Local terminal" via side bar, the resulting console is not authenticated
Image Image

This used to work, now I have to login again whenever I open a console.

  1. Adding a connection to Kotlin App doesn't trigger any AWS auth or provide credentials to it
Image
! Caused by: SdkClientException: Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChain(credentialsProviders=[SystemPropertyCredentialsProvider(),(...)environment variables are set., InstanceProfileCredentialsProvider(): Failed to load credentials from IMDS.]
! at SdkClientException$BuilderImpl.build(SdkClientException.java:130)
! at AwsCredentialsProviderChain.resolveCredentials(AwsCredentialsProviderChain.java:130)
! at LazyAwsCredentialsProvider.resolveCredentials(LazyAwsCredentialsProvider.java:45)
! at DefaultCredentialsProvider.resolveCredentials(DefaultCredentialsProvider.java:134)
! at AwsCredentialsProvider.resolveIdentity(AwsCredentialsProvider.java:54)
! at SecretsManagerAuthSchemeInterceptor.lambda$trySelectAuthScheme$4(SecretsManagerAuthSchemeInterceptor.java:134)
! at MetricUtils.reportDuration(MetricUtils.java:81)
! at SecretsManagerAuthSchemeInterceptor.trySelectAuthScheme(SecretsManagerAuthSchemeInterceptor.java:134)
! at SecretsManagerAuthSchemeInterceptor.selectAuthScheme(SecretsManagerAuthSchemeInterceptor.java:81)
! at SecretsManagerAuthSchemeInterceptor.beforeExecution(SecretsManagerAuthSchemeInterceptor.java:61)
! at ExecutionInterceptorChain.lambda$beforeExecution$1(ExecutionInterceptorChain.java:59)
! at java.base/ArrayList.forEach(ArrayList.java:1596)
! at ExecutionInterceptorChain.beforeExecution(ExecutionInterceptorChain.java:59)
! at AwsExecutionContextBuilder.runInitialInterceptors(AwsExecutionContextBuilder.java:315)
! at AwsExecutionContextBuilder.invokeInterceptorsAndCreateExecutionContext(AwsExecutionContextBuilder.java:151)
! at AwsSyncClientHandler.invokeInterceptorsAndCreateExecutionContext(AwsSyncClientHandler.java:67)
! at BaseSyncClientHandler.lambda$execute$1(BaseSyncClientHandler.java:76)
! at BaseSyncClientHandler.measureApiCallSuccess(BaseSyncClientHandler.java:182)
! at BaseSyncClientHandler.execute(BaseSyncClientHandler.java:74)
! at SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
! at AwsSyncClientHandler.execute(AwsSyncClientHandler.java:53)

This was working recently, I've tried to update IntelliJ to the latest version, still running into issues.

Expected behavior

When running an app or the terminal, the AWS connection should be provided automatically when setup, so the app/terminal can use it to interact with AWS resources.

Screenshots

Your Environment

  • OS: macOS Sequoia Version 15.6.1 (24G90)
  • JetBrains product: IntelliJ IDEA Ultimate
  • JetBrains product version: IntelliJ IDEA 2025.2.2 (Ultimate Edition) Build #IU-252.26199.169, built on September 18, 2025
  • AWS Toolkit version: 3.94.252
  • SAM CLI version:
  • JVM/Python version:

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugWe can reproduce the issue and confirmed it is a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions