I'm Trong, a developer with the AWS development team at Mendix.
It sounds like the main issue here is integrating the AWS session token with the credential set in the AWS Authentication. From what you've mentioned, it's clear that you've already confirmed the access key and the secret access key are working as expected with the AWS CLI, provided the AWS Session Token is included.
To address your concern, if I understand correctly, you already have a session token generated, right? With the AWS Authentication module, you should still be able to authenticate with the
Credentials object. Here's a suggested approach:
Credentials object (
AccessKeyId attribute and your secret key in the
Provider attribute to
SessionToken object (
AWSAuthentication.SessionToken) and input your session token in the
Credentials_SessionToken on the object you created second in the order of the microflow's execution (following this step-by-step it would be the SessionToken object).
I hope this method clears up the authentication issue you're facing. If you run into any more challenges or need further clarification, please don't hesitate to respond to this thread, I'll be sure to keep an eye out.