[
https://issues.apache.org/jira/browse/CAMEL-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599470#comment-17599470
]
Claus Ibsen commented on CAMEL-18418:
-------------------------------------
Great the RAW fix was backported for 3.18.2
> aws-s3-sink Kamelet returns 403
> -------------------------------
>
> Key: CAMEL-18418
> URL: https://issues.apache.org/jira/browse/CAMEL-18418
> Project: Camel
> Issue Type: Bug
> Components: camel-kamelet
> Affects Versions: 3.18.0
> 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.
>
> Reporter: Bruno Meseguer
> Priority: Major
> Attachments: issue.tar.gz
>
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
