[GitHub] [pulsar] YanshuoH edited a comment on issue #9424: InvalidToken while using AWS WebIdentityTokenFile within EKS to offload a topic

[GitBox <gi...@apache.org>]

YanshuoH edited a comment on issue #9424:
URL: https://github.com/apache/pulsar/issues/9424#issuecomment-904611865


   Sorry but I've got to reopen the issue.
   
   Currently upgraded to pulsar 2.7.3, the failure still occurs.
   
   I've created another pod with the same AWS credentials injected, upload file to s3 works fine:
   
   ```
   bash-4.2# aws sts get-caller-identity
   {
       "UserId": "<omit>:botocore-session-1629808715",
       "Account": "651844176281",
       "Arn": "arn:aws-cn:sts::<omit>:assumed-role/pulsar-broker-sa/botocore-session-1629808715"
   }
   
   
   bash-4.2# aws s3 cp thing.txt s3://pulsar-cluster/pulsar-standby/
   upload: ./thing.txt to s3://pulsar-cluster/pulsar-standby/thing.txt
   ```
   
   I wonder if there is something that I've missed?
   
   I could always use a pair of static AK/SK but it seems a regression.
   
   Thanks.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org