Pipeline failed: An error occurred (SignatureDoesNotMatch) when calling the AssumeRole operation #733
              
                Unanswered
              
          
                  
                    
                      gberlot-luna
                    
                  
                
                  asked this question in
                How do I
              
            Replies: 1 comment 1 reply
-
| 
         @gberlot-luna it sounds like the error may be related to not having MFA set up correctly? Does this KB post help solve your issue https://github.com/orgs/gruntwork-io/discussions/6  | 
  
Beta Was this translation helpful? Give feedback.
                  
                    1 reply
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We just finished to configure pipeline using the following documentation: https://github.com/gruntwork-clients/infrastructure-live-luna-solutions-llc-2/blob/main/docs/03-configure-gw-pipelines.md (We used the example that's on the documentation to trigger it)
however the following error was displayed.
2023-06-07 20:52:57 [INFO] [aws-auth] Assuming role arn:aws:iam::XXXXXXXXX:role/allow-auto-deploy-from-other-accounts. These creds will expire after 3600 seconds.
An error occurred (SignatureDoesNotMatch) when calling the AssumeRole operation: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
Error: Process completed with exit code 123.
Please advice, how to fix it.
Tracked in ticket #110240
Beta Was this translation helpful? Give feedback.
All reactions