-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
unable to capture/except sts error since upgrading from 1.13.1 #1866
Comments
@pcanham - Thank you for your post. I am not able to reproduce the issue when i ran your code with latest version of botocore. Can you please make sure that you are able to run sts assume_role call without error before running the script ? If you are getting error with If you are not getting error with sts |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Hi, I have upgraded the library to 1.13.13 and get errors still here is the stacktrace
I have tested the permissions via the aws cli and have no issues with the AssumeRole operation. To ensure this was not a permissions issue i have also moved to a different role which would give me full admin access to the account (created via AWS Organisations) called "OrganizationAccountAccessRole" format of the boto3 credentials file is
primary is the master account and 'XXXXXXX' is the account which i am trying to perform the STS checks against. I havent had a chance to check the code, but from looking at the logging outputs for 1.13.1 and 1.13.13 there is a warning which is extra which i am wondering is invalidating something
Additional Notes, if you go into IAM and then Account settings, i have on purpose disabled certain STS endpoints, not sure whether this is why i am getting the stack trace |
Thought I would test with the latest version and it still fails. Version : 1.13.40
|
Bit more information, found my script was not displaying the following error
|
@pcanham - Sorry for the late reply. It looks like the credentials being used to the make the initial assume role call are expired. Can you make any other API calls with the original credentials? |
The following code snippet use to work for finding out whether STS was enabled within a specific AWS region, but since upgrading the botocore library this is failing, for some reason you are not able to capture the error, it just performs a stacktrace
Error
Additional information, the permissions i am getting is from an AssumeRole which works with the aws cli tool, using role_arn and source_profile within the credentials file
The text was updated successfully, but these errors were encountered: