[CAMEL-18418] aws-s3-sink Kamelet returns 403

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.18.0
• Fix Version/s: 3.18.2, 3.19.0
• Component/s: camel-kamelet

Environment

The problem has been reproduced using an OpenShift Data Foundation instance deployed in an OpenShift 4.10 environment.

Find attached a compressed file containing the sample code to reproduce the problem. Note the same code using the Camel component instead of Kamelet works well.

 

• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Bruno Meseguer
• Created: 22/Aug/22 11:26
• Updated: 02/Sep/22 12:37
• Resolved: 02/Sep/22 12:37

Description

The Kamelet `aws-s3-sink` returns 403 against a ceph based S3 service.

It seems to be related to the accessKey and secretKey parameters resolution.

A workaround that works is to edit the original Kamelet and hardcode the accessKey and secretKey in the aws2-s3 Camel component.

 

Issue Links

• relates to: CAMEL-18435 camel-core - RAW values should be kept as-s