Skip to content

Role assumption chain in AWS Tookit for VSCode

0

I updated the AWS Toolkit for VSCode from v3.46 to v3.47. I previously was able to use role assumption chains like this (config file):

[profile myauthprofile] region=eu-central-1 output=json

[profile mytestprofile] source_profile = myauthprofile role_arn = arn:aws:iam::123456789012:role/testrole region=eu-central-1 output=json

This is no longer possible in v3.47. I reverted to v3.46 for the time being.

As I cannot report the issue in GitHub, could you please verify and report it?

asked a year ago253 views

1 Answer
1

I apologize, but I cannot verify or report issues directly to AWS on your behalf. However, I can provide some information about the situation you're describing.

The issue you're experiencing with role assumption chains in the AWS Toolkit for Visual Studio Code after updating from v3.46 to v3.47 is not a known or documented problem based on the information available to me. Role assumption chains, as you've described in your config file, should generally continue to work across version updates.

That being said, issues can sometimes arise with software updates. If you're experiencing a problem with a specific version, it's a good practice to document the issue in detail, including:

  1. The exact versions involved (v3.46 and v3.47 in this case)
  2. The configuration you're using
  3. The exact error message or unexpected behavior you're seeing
  4. Steps to reproduce the issue

While I can't report the issue directly, you may want to consider the following options:

  1. Double-check your configuration to ensure there are no typos or changes that might have been introduced during the update.

  2. Look for any error messages in the AWS Toolkit logs within VS Code. These logs might provide more insight into why the role assumption chain isn't working as expected.

  3. If possible, try setting up the role assumption chain in a new VS Code workspace to see if the issue persists.

  4. Consider reaching out to AWS support or posting on the AWS forums if the issue continues. They may be able to provide more specific guidance or escalate the issue if it's indeed a bug in the new version.

  5. Keep an eye on the AWS Toolkit for VS Code documentation and release notes for any updates or known issues that might be related to your problem.

If reverting to v3.46 resolves the issue for you temporarily, that's a good workaround while you investigate further or wait for potential updates.
Sources
Troubleshooting the AWS Toolkit for Visual Studio Code - AWS Toolkit for VS Code

answered a year ago

EXPERT

reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.