We would like to have option to specify the AWS assume role instead of specifying the AWS access key and secret key. Eventually we would like to use the same connection in "Aws Secret Manager: Update Secret" task to update the secret in AWS cloud.
by: Vijay G. | 15 days ago | Integrations
Comments
This change is scheduled to be included in the upcoming 25.1 maintenance release, planned for the end of August 2025.
After investigating, we found that the AWS Secrets Manager plugin is implemented in Jython and therefore cannot use AWS AssumeRole unless both the access key and secret key are explicitly defined in the connection.
To address this limitation, we propose extending the existing AWS Container plugin with two new tasks: Read Secret and Update Secret. These tasks would use the current AWS Container plugin connection to retrieve and update secrets as expected.
Please let us know if this approach would meet your needs.