- Newest
- Most votes
- Most comments
The error you’re seeing likely stems from a mismatch in cryptographic algorithms between Power Automate and the AWS SFTP server. Review the HMAC algorithms and key exchange algorithms supported on both sides. You may need to adjust the AWS SFTP configuration or check for any algorithm compatibility issues with Power Automate. Additionally, ensure the private key format is correct and that the AWS endpoint and security settings are properly configured
AWS Transfer uses the latest available security policy by default. A list of them is in this documentation article: https://docs.aws.amazon.com/transfer/latest/userguide/security-policies.html
While using the latest policy is recommended, since Power Automate appears to be lagging behind in development, you'll probably need to switch AWS Transfer to use an older security policy. My guess would be Power Automate might be using hmac-sha2-256
, in which case the policy you should try is TransferSecurityPolicy-2022-03
. You can select the policy in the server's properties in the console: https://docs.aws.amazon.com/transfer/latest/userguide/edit-server-config.html#edit-cryptographic-algorithm
Ok thanks will try this,,, i thought i can do anything inside power automate,, but seems the fix will be inside AWS ..Thanks will try and keep you posted.
The error "Server HMAC algorithm not found" you're encountering when trying to connect Power Automate to Amazon Web Services (AWS) via SFTP-SSH suggests there might be a mismatch in the supported encryption algorithms between Power Automate and the AWS SFTP server.
This issue is likely not specific to Power Automate or AWS individually, but rather a compatibility problem between the two services' supported HMAC (Hash-based Message Authentication Code) algorithms for SSH connections.
To resolve this issue, you can try the following steps:
-
Verify that you're using the correct and most up-to-date SSH key. Ensure that the private key you're using in Power Automate matches the public key registered with your AWS SFTP server.
-
Check if your AWS Transfer Family server (which handles SFTP connections) is configured to support the HMAC algorithms that Power Automate is attempting to use. You may need to adjust the server's security policy to include additional HMAC algorithms.
-
Make sure you're using the correct endpoint URL for your AWS SFTP server. Double-check that it's formatted correctly and points to the right AWS region.
-
Verify that the username you're using has the necessary permissions to access the AWS SFTP server.
-
Ensure that the fingerprint you've provided matches the server's actual fingerprint. You can obtain the correct fingerprint using the
ssh-keyscan
command against your AWS SFTP server.
If these steps don't resolve the issue, you may need to contact AWS support to check if there are any specific configuration requirements for connecting Power Automate to their SFTP service. Additionally, you could explore using alternative connection methods, such as setting up an AWS API Gateway as an intermediary between Power Automate and your AWS resources.
It's worth noting that while this error is challenging, it doesn't necessarily mean that Power Automate cannot connect to AWS. It's more likely that some configuration adjustments are needed to ensure compatibility between the two services.
Sources
TestConnection - AWS Transfer Family
VALIDATION_ERROR_INVALID_SSH_KEY_NAME - Amazon EMR
Relevant content
- asked 12 days ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks the options inside Power Automate is very limited, and i already passed all the needed parameters