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.

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

Add support for refreshing AWS Credentials #1268

Open
EronWright opened this issue Jan 12, 2024 · 1 comment
Open

Add support for refreshing AWS Credentials #1268

EronWright opened this issue Jan 12, 2024 · 1 comment
Labels
kind/enhancement Improvements or new features

Comments

@EronWright
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The security token doesn't seem to get refreshed as necessary during a long-running provider operation. For example, this CI job was polling an outstanding CC request and eventually died due to an expired token.

  @ updating......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
  ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
  ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
  ....................................................................................................................................................................................................................................................................................................................................................................................................................
   +  aws-native:iam:Role role-15 creating (3516s) error: getting resource request status: operation error CloudControl: GetResourceRequestStatus, https response error StatusCode: 400, RequestID: 4f0d08e2-9afb-40d1-ac6f-8a706210b5e4, api error ExpiredTokenException: The security token included in the request is expired
   +  aws-native:iam:Role role-15 **creating failed** error: getting resource request status: operation error CloudControl: GetResourceRequestStatus, https response error StatusCode: 400, RequestID: 4f0d08e2-9afb-40d1-ac6f-8a706210b5e4, api error ExpiredTokenException: The security token included in the request is expired
   +  pulumi:pulumi:Stack aws-parallel-ts-p-it-runner-parallel-t-3a900e5a creating (3521s) error: update failed
   +  pulumi:pulumi:Stack aws-parallel-ts-p-it-runner-parallel-t-3a900e5a **creating failed (4s)** 1 error; 2 warnings
  Diagnostics:
    pulumi:pulumi:Stack (aws-parallel-ts-p-it-runner-parallel-t-3a900e5a):
      warning: using pulumi-resource-aws-native from $PATH at /home/runner/work/pulumi-aws-native/pulumi-aws-native/bin/pulumi-resource-aws-native
      warning: using pulumi-resource-aws-native from $PATH at /home/runner/work/pulumi-aws-native/pulumi-aws-native/bin/pulumi-resource-aws-native
      error: update failed

It may be related to aws/aws-cli#9034 and/or aws/aws-sdk-go-v2#2135.

@EronWright EronWright added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Jan 12, 2024
@EronWright
Copy link
Contributor Author

See also: #1182

@mjeffryes mjeffryes removed the needs-triage Needs attention from the triage team label Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants