This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git


The following commit(s) were added to refs/heads/main by this push:
     new c0cea61d1 chore: the S3 event source can log in with an IAM role, the 
S3 sinks can use a KMS key and a storage class (#3170) (#3206)
c0cea61d1 is described below

commit c0cea61d1c41b3962ced4c4886f3c1d6dad767f4
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Nov 18 20:55:19 2026 +0100

    chore: the S3 event source can log in with an IAM role, the S3 sinks can 
use a KMS key and a storage class (#3170) (#3206)
    
    aws-s3-event-based-source took only accessKey and secretKey, so it could not
    run with an IAM role (EKS IRSA or Pod Identity, ECS, EC2), an AWS profile or
    session credentials. It now has the credential options of aws-s3-source and
    aws-s3-sink: useDefaultCredentialsProvider, useProfileCredentialsProvider 
with
    profileCredentialsName, and useSessionCredentials with sessionToken. They go
    both to the aws2-sqs consumer and to the aws2-s3 getObject call, and
    accessKey and secretKey are no longer required. The keys of the getObject
    call are now in RAW(): before, a secret key with a + failed with
    SignatureDoesNotMatch, because the + was read as a space.
    
    aws-s3-sink and aws-s3-streaming-upload-sink take useAwsKMS and awsKMSKeyId
    to encrypt the files with a KMS key (SSE-KMS), as a bucket policy may
    require, useSSES3 to ask for SSE-S3 in the request, and storageClass.
    The streaming sink passes them to its multipart uploads.
    
    All new options are optional and have no default, so that with them unset
    the endpoint URIs are as before (apart from RAW() on the getObject keys).
    
    Co-authored-by: Claude Opus 5.5 <[email protected]>
---
 .../aws-s3-event-based-source-description.adoc     | 41 ++++++++++++++++++++--
 .../ROOT/partials/aws-s3-sink-description.adoc     | 33 +++++++++++++++++
 .../aws-s3-streaming-upload-sink-description.adoc  | 38 +++++++++++++++++++-
 kamelets/aws-s3-event-based-source.kamelet.yaml    | 40 +++++++++++++++++----
 kamelets/aws-s3-sink.kamelet.yaml                  | 24 +++++++++++--
 kamelets/aws-s3-streaming-upload-sink.kamelet.yaml | 26 ++++++++++++--
 .../main/resources/META-INF/kamelets-index.json    |  6 ++--
 .../aws-s3-event-based-source.kamelet.yaml         | 40 +++++++++++++++++----
 .../resources/kamelets/aws-s3-sink.kamelet.yaml    | 24 +++++++++++--
 .../aws-s3-streaming-upload-sink.kamelet.yaml      | 26 ++++++++++++--
 10 files changed, 270 insertions(+), 28 deletions(-)

diff --git 
a/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc 
b/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc
index 75260112b..d6d2ccb7a 100644
--- a/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc
+++ b/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc
@@ -2,10 +2,47 @@
 
 === Authentication methods
 
-Access Key/Secret Key is the basic method for authenticating to the AWS SQS 
Service.
+The Kamelet logs in with the same credentials to the SQS queue and, when 
`getObject` is true, to the bucket. It can use:
+
+- an access key and a secret key, in `accessKey` and `secretKey`;
+- temporary credentials, such as the ones AWS STS gives when you assume an IAM 
role, with `useSessionCredentials` set to `true` and `accessKey`, `secretKey` 
and `sessionToken`;
+- the credentials of the environment, with `useDefaultCredentialsProvider` set 
to `true`, and no keys;
+- a profile of the AWS credentials file (`~/.aws/credentials`), with 
`useProfileCredentialsProvider` set to `true` and the name of the profile in 
`profileCredentialsName`, and no keys.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS, which is how an IAM role reaches a pod on 
Amazon EKS (IRSA).
+ - The shared credentials and config files.
+ - Container credentials - loaded when the environment variable 
`AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` (Amazon ECS) or 
`AWS_CONTAINER_CREDENTIALS_FULL_URI` (EKS Pod Identity) is set.
+ - Amazon EC2 Instance profile credentials.
+
+For more information, see the 
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS
 credentials documentation]
+
+=== Example with the IAM Role of the Pod
+
+On Kubernetes, with an IAM role given to the pod through IRSA or EKS Pod 
Identity, no keys are needed:
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:aws-s3-event-based-source"
+      parameters:
+        queueNameOrArn: "s3-events"
+        region: "eu-west-1"
+        useDefaultCredentialsProvider: true
+        getObject: true
+      steps:
+        - to:
+            uri: "kamelet:log-sink"
+----
+
+The role needs the permission to receive and delete the messages of the queue 
and, with `getObject`, to read the files of the bucket.
 
 === Required Setup
 
 To use this Kamelet you'll need to set up Eventbridge on your bucket and 
subscribe Eventbridge bus to an SQS Queue.
-      
+
 For doing this you'll need to enable Eventbridge notification on your bucket 
and creating a rule on Eventbridge console related to all the events on S3 
bucket and pointing to the SQS Queue specified as parameter in this Kamelet.
diff --git a/docs/modules/ROOT/partials/aws-s3-sink-description.adoc 
b/docs/modules/ROOT/partials/aws-s3-sink-description.adoc
index 19c1a366a..7e15e746e 100644
--- a/docs/modules/ROOT/partials/aws-s3-sink-description.adoc
+++ b/docs/modules/ROOT/partials/aws-s3-sink-description.adoc
@@ -26,3 +26,36 @@ In the header, you can optionally set the `file` / `ce-file` 
property to specify
 If you do not set the property in the header, the Kamelet uses a generated 
unique ID for the file name.
 
 When the `keyName` option is set, the `file` / `ce-file` header is not used, 
and every message is written to that key, replacing the previous file.
+
+=== Example with Encryption by a KMS Key and a Storage Class
+
+A bucket policy can require every file to be encrypted with a given key of AWS 
KMS (SSE-KMS); an upload without it is
+refused with `AccessDenied`. Set **useAwsKMS** and **awsKMSKeyId** to encrypt 
the files with that key, and
+**storageClass** to store them in another class than `STANDARD`:
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:kafka-source"
+      parameters:
+        topic: "invoices"
+        bootstrapServers: "kafka.example.com:9092"
+        saslAuthType: "NONE"
+      steps:
+        - to:
+            uri: "kamelet:aws-s3-sink"
+            parameters:
+              bucketNameOrArn: "my-bucket"
+              region: "eu-west-1"
+              useDefaultCredentialsProvider: true
+              useAwsKMS: true
+              awsKMSKeyId: 
"arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab"
+              storageClass: "STANDARD_IA"
+----
+
+The credentials need the permission to use the key (`kms:GenerateDataKey`), 
and whoever reads the files the permission
+to decrypt with it (`kms:Decrypt`). Without **awsKMSKeyId**, **useAwsKMS** has 
no effect. To ask for the encryption with keys that S3 manages
+(SSE-S3) instead, as some bucket policies require, set **useSSES3** to `true`. 
The storage class can be any class of
+S3, such as `STANDARD_IA`, `INTELLIGENT_TIERING` or `GLACIER_IR`; a file in 
`GLACIER` or `DEEP_ARCHIVE` must be restored
+before it can be read. A `CamelAwsS3StorageClass` header on the message takes 
precedence over **storageClass**.
diff --git 
a/docs/modules/ROOT/partials/aws-s3-streaming-upload-sink-description.adoc 
b/docs/modules/ROOT/partials/aws-s3-streaming-upload-sink-description.adoc
index b68b62218..b58bc916c 100644
--- a/docs/modules/ROOT/partials/aws-s3-streaming-upload-sink-description.adoc
+++ b/docs/modules/ROOT/partials/aws-s3-streaming-upload-sink-description.adoc
@@ -21,6 +21,42 @@ For more information, see the 
https://docs.aws.amazon.com/sdk-for-java/latest/de
 
 === File names
 
-This Kamelet uses no headers: the name of the files comes from the `keyName` 
option.
+The name of the files comes from the `keyName` option, not from headers.
 
 With the default `namingStrategy` of `progressive` and a `keyName` of 
`logs/app.log`, the first file is `logs/app.log` and the next ones are 
`logs/app-1.log`, `logs/app-2.log` and so on. With `random` or `timestamp`, a 
random ID or the time in milliseconds is added to the name instead of a number.
+
+=== Example with Encryption by a KMS Key and a Storage Class
+
+A bucket policy can require every file to be encrypted with a given key of AWS 
KMS (SSE-KMS); an upload without it is
+refused with `AccessDenied`. Set **useAwsKMS** and **awsKMSKeyId** to encrypt 
the files with that key, and
+**storageClass** to store them in another class than `STANDARD`:
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:kafka-source"
+      parameters:
+        topic: "invoices"
+        bootstrapServers: "kafka.example.com:9092"
+        saslAuthType: "NONE"
+      steps:
+        - setBody:
+            simple: "$\{body}\n"
+        - to:
+            uri: "kamelet:aws-s3-streaming-upload-sink"
+            parameters:
+              bucketNameOrArn: "my-bucket"
+              region: "eu-west-1"
+              useDefaultCredentialsProvider: true
+              keyName: "invoices/invoices.jsonl"
+              useAwsKMS: true
+              awsKMSKeyId: 
"arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab"
+              storageClass: "STANDARD_IA"
+----
+
+The credentials need the permission to use the key (`kms:GenerateDataKey`), 
and whoever reads the files the permission
+to decrypt with it (`kms:Decrypt`). Without **awsKMSKeyId**, the files are 
encrypted with the key that AWS manages for S3 (`aws/s3`). To ask for the 
encryption with keys that S3 manages
+(SSE-S3) instead, as some bucket policies require, set **useSSES3** to `true`. 
The storage class can be any class of
+S3, such as `STANDARD_IA`, `INTELLIGENT_TIERING` or `GLACIER_IR`; a file in 
`GLACIER` or `DEEP_ARCHIVE` must be restored
+before it can be read. A `CamelAwsS3StorageClass` header on the message takes 
precedence over **storageClass**.
diff --git a/kamelets/aws-s3-event-based-source.kamelet.yaml 
b/kamelets/aws-s3-event-based-source.kamelet.yaml
index ac584bd35..8a4542964 100644
--- a/kamelets/aws-s3-event-based-source.kamelet.yaml
+++ b/kamelets/aws-s3-event-based-source.kamelet.yaml
@@ -39,10 +39,8 @@ spec:
 
       Output: the body is the EventBridge event, as JSON text: `detail-type` 
says what happened (such as `Object Created` or `Object Deleted`), 
`detail.bucket.name` is the bucket and `detail.object.key` the key of the file. 
With `getObject` set to true, the event of a file uploaded with a simple upload 
(PutObject) carries the content of the file instead, as a stream, with the 
`CamelAwsS3ProducedBucketName` and `CamelAwsS3ProducedKey` headers; the other 
events then come as parsed JSON (a  [...]
 
-      Good to know: it needs a setup in AWS. In the properties of the bucket, 
turn on sending events to Amazon EventBridge; then create an EventBridge rule 
for the events of source `aws.s3` and that bucket, with the queue as its 
target. Each event is deleted from the queue once it has been processed, unless 
`deleteAfterRead` is false. The files stay in the bucket. `getObject` skips 
files created by a multipart upload or a copy, and never connects through 
`uriEndpointOverride`.
+      Good to know: it needs a setup in AWS. In the properties of the bucket, 
turn on sending events to Amazon EventBridge; then create an EventBridge rule 
for the events of source `aws.s3` and that bucket, with the queue as its 
target. Each event is deleted from the queue once it has been processed, unless 
`deleteAfterRead` is false. The files stay in the bucket. `getObject` skips 
files created by a multipart upload or a copy, and never connects through 
`uriEndpointOverride`. It logs in [...]
     required:
-      - accessKey
-      - secretKey
       - queueNameOrArn
       - region
     type: object
@@ -59,7 +57,7 @@ spec:
         default: true
       accessKey:
         title: Access Key
-        description: The access key ID of an IAM user, which you create in the 
AWS console under IAM, Users, Security credentials. Use it together with 
`secretKey`.
+        description: The access key ID of an IAM user, which you create in the 
AWS console under IAM, Users, Security credentials. Use it together with 
`secretKey`. Leave both out when `useDefaultCredentialsProvider` or 
`useProfileCredentialsProvider` is true.
         type: string
         format: password
         x-descriptors:
@@ -117,6 +115,31 @@ spec:
         description: If true, the queue is created when it does not exist. A 
name that ends in `.fifo` creates a FIFO queue. The credentials need the 
permission to create queues.
         type: boolean
         default: false
+      useDefaultCredentialsProvider:
+        title: Default Credentials Provider
+        description: "If true, the credentials are found in the environment 
instead of in `accessKey` and `secretKey`: the `AWS_ACCESS_KEY_ID` and 
`AWS_SECRET_ACCESS_KEY` environment variables, the `~/.aws/credentials` file, 
or the IAM role of the EC2 instance, ECS task or Kubernetes pod the integration 
runs on."
+        type: boolean
+      useProfileCredentialsProvider:
+        title: Profile Credentials Provider
+        description: If true, the credentials are read from a named profile in 
the AWS credentials file (`~/.aws/credentials`), as the AWS CLI does. Name the 
profile in `profileCredentialsName`.
+        type: boolean
+      useSessionCredentials:
+        title: Session Credentials
+        description: "If true, it logs in with temporary credentials: 
`accessKey`, `secretKey` and `sessionToken`, such as the ones AWS STS gives 
when you assume an IAM role."
+        type: boolean
+      profileCredentialsName:
+        title: Profile Credentials Name
+        description: The name of the profile in the AWS credentials file. Only 
used when `useProfileCredentialsProvider` is true; when it is not set, the 
default profile is used.
+        example: production
+        type: string
+        pattern: "^[A-Za-z0-9_.@-]+$"
+      sessionToken:
+        title: Session Token
+        description: The session token of temporary credentials, which comes 
with their access key and secret key, for example from AWS STS when you assume 
an IAM role. Only used when `useSessionCredentials` is true.
+        type: string
+        format: password
+        x-descriptors:
+          - 'urn:camel:group:credentials'
       amazonAWSHost:
         title: AWS Host
         description: The host name of AWS. Leave it as `amazonaws.com` for 
AWS. Any other value is the address to connect to instead, as `host:port`, 
together with `protocol`; `uriEndpointOverride` does the same.
@@ -155,7 +178,7 @@ spec:
         default: false
       getObject:
         title: Get Object
-        description: If true, for an event of a file uploaded with a simple 
upload (PutObject), it fetches the file and sends its content instead of the 
event. It connects to S3 with `accessKey`, `secretKey` and `region` only, not 
with `uriEndpointOverride`.
+        description: If true, for an event of a file uploaded with a simple 
upload (PutObject), it fetches the file and sends its content instead of the 
event. It connects to S3 with the same credentials as the queue and with 
`region`, not with `uriEndpointOverride`.
         type: boolean
         default: false
   dataTypes:
@@ -196,6 +219,11 @@ spec:
         region: "{{region}}"
         secretKey: "RAW({{?secretKey}})"
         uriEndpointOverride: "{{?uriEndpointOverride}}"
+        useDefaultCredentialsProvider: "{{?useDefaultCredentialsProvider}}"
+        useProfileCredentialsProvider: "{{?useProfileCredentialsProvider}}"
+        profileCredentialsName: "{{?profileCredentialsName}}"
+        useSessionCredentials: "{{?useSessionCredentials}}"
+        sessionToken: "RAW({{?sessionToken}})"
       steps:
         - choice:
             precondition: true
@@ -229,7 +257,7 @@ spec:
                                   jsonpath:
                                     expression: "$.detail.bucket.name"
                             - toD:
-                                uri: 
"aws2-s3:${exchangeProperty.aws-s3-bucket}?accessKey={{accessKey}}&secretKey={{secretKey}}&region={{region}}&operation=getObject&keyName=${exchangeProperty.aws-s3-name}"
+                                uri: 
"aws2-s3:${exchangeProperty.aws-s3-bucket}?accessKey=RAW({{?accessKey}})&secretKey=RAW({{?secretKey}})&region={{region}}&operation=getObject&keyName=${exchangeProperty.aws-s3-name}&useDefaultCredentialsProvider={{?useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{?useProfileCredentialsProvider}}&profileCredentialsName={{?profileCredentialsName}}&useSessionCredentials={{?useSessionCredentials}}&sessionToken=RAW({{?sessionToken}})"
         - to:
             uri: kamelet:sink
 
diff --git a/kamelets/aws-s3-sink.kamelet.yaml 
b/kamelets/aws-s3-sink.kamelet.yaml
index 76bacd134..5ef5ea9a1 100644
--- a/kamelets/aws-s3-sink.kamelet.yaml
+++ b/kamelets/aws-s3-sink.kamelet.yaml
@@ -41,7 +41,7 @@ spec:
 
       Output: the message is unchanged. The `CamelAwsS3Key` and 
`CamelAwsS3ETag` headers give the key and the ETag of the uploaded file.
 
-      Good to know: a file with the same key is replaced without warning. When 
`keyName` is set, the `file` header is ignored and every message replaces the 
same file. To copy files from `aws-s3-source` under their own names, set the 
`file` header from its `CamelAwsS3Key` header first. It also works with 
S3-compatible storage, such as MinIO, through `overrideEndpoint`, 
`uriEndpointOverride` and `forcePathStyle`.
+      Good to know: a file with the same key is replaced without warning. When 
`keyName` is set, the `file` header is ignored and every message replaces the 
same file. To copy files from `aws-s3-source` under their own names, set the 
`file` header from its `CamelAwsS3Key` header first. It also works with 
S3-compatible storage, such as MinIO, through `overrideEndpoint`, 
`uriEndpointOverride` and `forcePathStyle`. To encrypt the files with a key of 
AWS KMS, as a bucket policy may require,  [...]
     required:
       - bucketNameOrArn
       - region
@@ -124,6 +124,26 @@ spec:
         description: The key (the path of the file in the bucket) to write 
every message to, such as `reports/latest.csv`. When it is set, the `file` 
header is not used and each message replaces the file of the previous one. When 
it is not set, the key comes from the `file` header, or is a generated unique 
ID.
         example: reports/latest.csv
         type: string
+      useAwsKMS:
+        title: Use AWS KMS
+        description: "If true, each file is encrypted in S3 with a key of AWS 
KMS (SSE-KMS): the key in `awsKMSKeyId`. Use it when the bucket policy requires 
SSE-KMS, or a key of your own. The credentials need the permission to use the 
key (`kms:GenerateDataKey`), and readers of the files the permission to decrypt 
with it (`kms:Decrypt`). Without `awsKMSKeyId`, it has no effect."
+        type: boolean
+      awsKMSKeyId:
+        title: AWS KMS Key ID
+        description: The KMS key to encrypt the files with, as its key ID, 
such as `1234abcd-12ab-34cd-56ef-1234567890ab`, or its ARN, such as 
`arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab`. 
Use the ARN for a key of another AWS account. Only used when `useAwsKMS` is 
true.
+        example: 
arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
+        type: string
+        pattern: "^[A-Za-z0-9:/_-]+$"
+      useSSES3:
+        title: Use SSE-S3
+        description: If true, the upload asks S3 to encrypt each file with 
keys that S3 manages (SSE-S3, `AES256`), in the `x-amz-server-side-encryption` 
header that some bucket policies require. S3 encrypts new files this way 
anyway, unless the bucket is set to another encryption. Do not combine it with 
`useAwsKMS`.
+        type: boolean
+      storageClass:
+        title: Storage Class
+        description: "The storage class of the files: `STANDARD`, 
`STANDARD_IA`, `ONEZONE_IA`, `INTELLIGENT_TIERING`, `GLACIER_IR`, `GLACIER`, 
`DEEP_ARCHIVE` or `REDUCED_REDUNDANCY`. A file in `GLACIER` or `DEEP_ARCHIVE` 
must be restored before it can be read. When it is not set, the files are 
stored as `STANDARD`. A `CamelAwsS3StorageClass` header on the message takes 
precedence."
+        example: STANDARD_IA
+        type: string
+        pattern: "^[A-Z_]+$"
   dataTypes:
     in:
       headers:
@@ -177,4 +197,4 @@ spec:
                                 simple:
                                   expression: "${exchangeId}"
         - to:
-            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&forcePathStyle={{forcePathStyle}}&keyName={{?keyName}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&uriEndpointOverride={{?uriEndpointOverride}}&useDefaultCredentialsProvider={{useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{useProfil
 [...]
+            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&forcePathStyle={{forcePathStyle}}&keyName={{?keyName}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&uriEndpointOverride={{?uriEndpointOverride}}&useDefaultCredentialsProvider={{useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{useProfil
 [...]
diff --git a/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml 
b/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
index 4e75c3c23..a3c7d0fce 100644
--- a/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
+++ b/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
@@ -36,11 +36,11 @@ spec:
 
       Use it to store a stream of small records, such as log lines, events or 
sensor readings, as a few large files instead of one file per message. To 
upload one file per message, use `aws-s3-sink`.
 
-      Input: the body is added to the end of the current file as it is, as 
text, bytes or a stream. Nothing is put between two messages: end each message 
with a line break if the file must have one record per line. Headers are not 
used: the names of the files come from `keyName`.
+      Input: the body is added to the end of the current file as it is, as 
text, bytes or a stream. Nothing is put between two messages: end each message 
with a line break if the file must have one record per line. The names of the 
files come from `keyName`, not from headers.
 
       Output: the message is unchanged. The message that completes a file gets 
the `CamelAwsS3ETag` header of that file.
 
-      Good to know: a file is uploaded when it has `batchMessageNumber` 
messages or `batchSize` bytes, or when `streamingUploadTimeout` has passed; 
until then it is not in the bucket. With the default `namingStrategy` of 
`progressive`, the first file is named `keyName`, such as `logs/app.log`, and 
the next ones `logs/app-1.log`, `logs/app-2.log` and so on. With 
`restartingPolicy` set to `override`, a new run starts again from `keyName` and 
replaces the files of the earlier run.
+      Good to know: a file is uploaded when it has `batchMessageNumber` 
messages or `batchSize` bytes, or when `streamingUploadTimeout` has passed; 
until then it is not in the bucket. With the default `namingStrategy` of 
`progressive`, the first file is named `keyName`, such as `logs/app.log`, and 
the next ones `logs/app-1.log`, `logs/app-2.log` and so on. With 
`restartingPolicy` set to `override`, a new run starts again from `keyName` and 
replaces the files of the earlier run. To encryp [...]
     required:
       - bucketNameOrArn
       - region
@@ -149,6 +149,26 @@ spec:
         description: If true, the bucket name is put in the path of the 
address (`https://host/my-bucket/key`) instead of in the host name 
(`https://my-bucket.host/key`). S3-compatible storage such as MinIO often needs 
it.
         type: boolean
         default: false
+      useAwsKMS:
+        title: Use AWS KMS
+        description: "If true, each file is encrypted in S3 with a key of AWS 
KMS (SSE-KMS): the key in `awsKMSKeyId`. Use it when the bucket policy requires 
SSE-KMS, or a key of your own. The credentials need the permission to use the 
key (`kms:GenerateDataKey`), and readers of the files the permission to decrypt 
with it (`kms:Decrypt`). Without `awsKMSKeyId`, the key that AWS manages for S3 
(`aws/s3`) is used."
+        type: boolean
+      awsKMSKeyId:
+        title: AWS KMS Key ID
+        description: The KMS key to encrypt the files with, as its key ID, 
such as `1234abcd-12ab-34cd-56ef-1234567890ab`, or its ARN, such as 
`arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab`. 
Use the ARN for a key of another AWS account. Only used when `useAwsKMS` is 
true.
+        example: 
arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
+        type: string
+        pattern: "^[A-Za-z0-9:/_-]+$"
+      useSSES3:
+        title: Use SSE-S3
+        description: If true, the upload asks S3 to encrypt each file with 
keys that S3 manages (SSE-S3, `AES256`), in the `x-amz-server-side-encryption` 
header that some bucket policies require. S3 encrypts new files this way 
anyway, unless the bucket is set to another encryption. Do not combine it with 
`useAwsKMS`.
+        type: boolean
+      storageClass:
+        title: Storage Class
+        description: "The storage class of the files: `STANDARD`, 
`STANDARD_IA`, `ONEZONE_IA`, `INTELLIGENT_TIERING`, `GLACIER_IR`, `GLACIER`, 
`DEEP_ARCHIVE` or `REDUCED_REDUNDANCY`. A file in `GLACIER` or `DEEP_ARCHIVE` 
must be restored before it can be read. When it is not set, the files are 
stored as `STANDARD`. A `CamelAwsS3StorageClass` header on the message takes 
precedence."
+        example: STANDARD_IA
+        type: string
+        pattern: "^[A-Z_]+$"
   dependencies:
     - "camel:aws2-s3"
     - "camel:kamelet"
@@ -157,4 +177,4 @@ spec:
       uri: kamelet:source
       steps:
         - to:
-            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&batchMessageNumber={{batchMessageNumber}}&batchSize={{batchSize}}&forcePathStyle={{forcePathStyle}}&keyName={{keyName}}&namingStrategy={{namingStrategy}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&restartingPolicy={{restartingPolicy}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&streamingUplo
 [...]
+            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&batchMessageNumber={{batchMessageNumber}}&batchSize={{batchSize}}&forcePathStyle={{forcePathStyle}}&keyName={{keyName}}&namingStrategy={{namingStrategy}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&restartingPolicy={{restartingPolicy}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&streamingUplo
 [...]
diff --git 
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json 
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index e4ffb2c59..b6bc5691c 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -195,7 +195,7 @@
     "supportLevel" : "Preview",
     "title" : "AWS S3 Event Based Source",
     "summary" : "Receives the events of an Amazon S3 bucket, such as a new or 
a deleted file, from the Amazon SQS queue that Amazon EventBridge sends them 
to, one message per event.",
-    "description" : "Receives the events of an Amazon S3 bucket, such as a new 
or a deleted file, from the Amazon SQS queue that Amazon EventBridge sends them 
to, one message per event.\n\nUse it to react to new files in a bucket as soon 
as they arrive, without listing the bucket again and again, for example to 
process uploaded documents or imported data files. To read the files of a 
bucket by polling it, use `aws-s3-source`.\n\nOutput: the body is the 
EventBridge event, as JSON text: `d [...]
+    "description" : "Receives the events of an Amazon S3 bucket, such as a new 
or a deleted file, from the Amazon SQS queue that Amazon EventBridge sends them 
to, one message per event.\n\nUse it to react to new files in a bucket as soon 
as they arrive, without listing the bucket again and again, for example to 
process uploaded documents or imported data files. To read the files of a 
bucket by polling it, use `aws-s3-source`.\n\nOutput: the body is the 
EventBridge event, as JSON text: `d [...]
     "group" : "AWS S3 Event-Based",
     "namespace" : "AWS",
     "provider" : "Apache Software Foundation"
@@ -205,7 +205,7 @@
     "supportLevel" : "Stable",
     "title" : "AWS S3 Sink",
     "summary" : "Uploads each message as a file (object) to an Amazon S3 
bucket, under a key (file name) taken from a header, the `keyName` option, or a 
generated ID.",
-    "description" : "Uploads each message as a file (object) to an Amazon S3 
bucket, under a key (file name) taken from a header, the `keyName` option, or a 
generated ID.\n\nUse it to store data in S3 for other systems or for archiving, 
such as exported records, received documents or events. To collect many small 
messages into a few large files, use `aws-s3-streaming-upload-sink`.\n\nInput: 
the body is the content of the file, as text, bytes, a stream or a file. Turn 
structured data such [...]
+    "description" : "Uploads each message as a file (object) to an Amazon S3 
bucket, under a key (file name) taken from a header, the `keyName` option, or a 
generated ID.\n\nUse it to store data in S3 for other systems or for archiving, 
such as exported records, received documents or events. To collect many small 
messages into a few large files, use `aws-s3-streaming-upload-sink`.\n\nInput: 
the body is the content of the file, as text, bytes, a stream or a file. Turn 
structured data such [...]
     "group" : "AWS S3",
     "namespace" : "AWS",
     "provider" : "Apache Software Foundation"
@@ -225,7 +225,7 @@
     "supportLevel" : "Stable",
     "title" : "AWS S3 Streaming upload Sink",
     "summary" : "Writes many messages into a few large files in an Amazon S3 
bucket, adding each message to the current file and starting a new file after a 
number of messages or bytes.",
-    "description" : "Writes many messages into a few large files in an Amazon 
S3 bucket, adding each message to the current file and starting a new file 
after a number of messages or bytes.\n\nUse it to store a stream of small 
records, such as log lines, events or sensor readings, as a few large files 
instead of one file per message. To upload one file per message, use 
`aws-s3-sink`.\n\nInput: the body is added to the end of the current file as it 
is, as text, bytes or a stream. Nothing  [...]
+    "description" : "Writes many messages into a few large files in an Amazon 
S3 bucket, adding each message to the current file and starting a new file 
after a number of messages or bytes.\n\nUse it to store a stream of small 
records, such as log lines, events or sensor readings, as a few large files 
instead of one file per message. To upload one file per message, use 
`aws-s3-sink`.\n\nInput: the body is added to the end of the current file as it 
is, as text, bytes or a stream. Nothing  [...]
     "group" : "AWS S3",
     "namespace" : "AWS",
     "provider" : "Apache Software Foundation"
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
index ac584bd35..8a4542964 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
@@ -39,10 +39,8 @@ spec:
 
       Output: the body is the EventBridge event, as JSON text: `detail-type` 
says what happened (such as `Object Created` or `Object Deleted`), 
`detail.bucket.name` is the bucket and `detail.object.key` the key of the file. 
With `getObject` set to true, the event of a file uploaded with a simple upload 
(PutObject) carries the content of the file instead, as a stream, with the 
`CamelAwsS3ProducedBucketName` and `CamelAwsS3ProducedKey` headers; the other 
events then come as parsed JSON (a  [...]
 
-      Good to know: it needs a setup in AWS. In the properties of the bucket, 
turn on sending events to Amazon EventBridge; then create an EventBridge rule 
for the events of source `aws.s3` and that bucket, with the queue as its 
target. Each event is deleted from the queue once it has been processed, unless 
`deleteAfterRead` is false. The files stay in the bucket. `getObject` skips 
files created by a multipart upload or a copy, and never connects through 
`uriEndpointOverride`.
+      Good to know: it needs a setup in AWS. In the properties of the bucket, 
turn on sending events to Amazon EventBridge; then create an EventBridge rule 
for the events of source `aws.s3` and that bucket, with the queue as its 
target. Each event is deleted from the queue once it has been processed, unless 
`deleteAfterRead` is false. The files stay in the bucket. `getObject` skips 
files created by a multipart upload or a copy, and never connects through 
`uriEndpointOverride`. It logs in [...]
     required:
-      - accessKey
-      - secretKey
       - queueNameOrArn
       - region
     type: object
@@ -59,7 +57,7 @@ spec:
         default: true
       accessKey:
         title: Access Key
-        description: The access key ID of an IAM user, which you create in the 
AWS console under IAM, Users, Security credentials. Use it together with 
`secretKey`.
+        description: The access key ID of an IAM user, which you create in the 
AWS console under IAM, Users, Security credentials. Use it together with 
`secretKey`. Leave both out when `useDefaultCredentialsProvider` or 
`useProfileCredentialsProvider` is true.
         type: string
         format: password
         x-descriptors:
@@ -117,6 +115,31 @@ spec:
         description: If true, the queue is created when it does not exist. A 
name that ends in `.fifo` creates a FIFO queue. The credentials need the 
permission to create queues.
         type: boolean
         default: false
+      useDefaultCredentialsProvider:
+        title: Default Credentials Provider
+        description: "If true, the credentials are found in the environment 
instead of in `accessKey` and `secretKey`: the `AWS_ACCESS_KEY_ID` and 
`AWS_SECRET_ACCESS_KEY` environment variables, the `~/.aws/credentials` file, 
or the IAM role of the EC2 instance, ECS task or Kubernetes pod the integration 
runs on."
+        type: boolean
+      useProfileCredentialsProvider:
+        title: Profile Credentials Provider
+        description: If true, the credentials are read from a named profile in 
the AWS credentials file (`~/.aws/credentials`), as the AWS CLI does. Name the 
profile in `profileCredentialsName`.
+        type: boolean
+      useSessionCredentials:
+        title: Session Credentials
+        description: "If true, it logs in with temporary credentials: 
`accessKey`, `secretKey` and `sessionToken`, such as the ones AWS STS gives 
when you assume an IAM role."
+        type: boolean
+      profileCredentialsName:
+        title: Profile Credentials Name
+        description: The name of the profile in the AWS credentials file. Only 
used when `useProfileCredentialsProvider` is true; when it is not set, the 
default profile is used.
+        example: production
+        type: string
+        pattern: "^[A-Za-z0-9_.@-]+$"
+      sessionToken:
+        title: Session Token
+        description: The session token of temporary credentials, which comes 
with their access key and secret key, for example from AWS STS when you assume 
an IAM role. Only used when `useSessionCredentials` is true.
+        type: string
+        format: password
+        x-descriptors:
+          - 'urn:camel:group:credentials'
       amazonAWSHost:
         title: AWS Host
         description: The host name of AWS. Leave it as `amazonaws.com` for 
AWS. Any other value is the address to connect to instead, as `host:port`, 
together with `protocol`; `uriEndpointOverride` does the same.
@@ -155,7 +178,7 @@ spec:
         default: false
       getObject:
         title: Get Object
-        description: If true, for an event of a file uploaded with a simple 
upload (PutObject), it fetches the file and sends its content instead of the 
event. It connects to S3 with `accessKey`, `secretKey` and `region` only, not 
with `uriEndpointOverride`.
+        description: If true, for an event of a file uploaded with a simple 
upload (PutObject), it fetches the file and sends its content instead of the 
event. It connects to S3 with the same credentials as the queue and with 
`region`, not with `uriEndpointOverride`.
         type: boolean
         default: false
   dataTypes:
@@ -196,6 +219,11 @@ spec:
         region: "{{region}}"
         secretKey: "RAW({{?secretKey}})"
         uriEndpointOverride: "{{?uriEndpointOverride}}"
+        useDefaultCredentialsProvider: "{{?useDefaultCredentialsProvider}}"
+        useProfileCredentialsProvider: "{{?useProfileCredentialsProvider}}"
+        profileCredentialsName: "{{?profileCredentialsName}}"
+        useSessionCredentials: "{{?useSessionCredentials}}"
+        sessionToken: "RAW({{?sessionToken}})"
       steps:
         - choice:
             precondition: true
@@ -229,7 +257,7 @@ spec:
                                   jsonpath:
                                     expression: "$.detail.bucket.name"
                             - toD:
-                                uri: 
"aws2-s3:${exchangeProperty.aws-s3-bucket}?accessKey={{accessKey}}&secretKey={{secretKey}}&region={{region}}&operation=getObject&keyName=${exchangeProperty.aws-s3-name}"
+                                uri: 
"aws2-s3:${exchangeProperty.aws-s3-bucket}?accessKey=RAW({{?accessKey}})&secretKey=RAW({{?secretKey}})&region={{region}}&operation=getObject&keyName=${exchangeProperty.aws-s3-name}&useDefaultCredentialsProvider={{?useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{?useProfileCredentialsProvider}}&profileCredentialsName={{?profileCredentialsName}}&useSessionCredentials={{?useSessionCredentials}}&sessionToken=RAW({{?sessionToken}})"
         - to:
             uri: kamelet:sink
 
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
index 76bacd134..5ef5ea9a1 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
@@ -41,7 +41,7 @@ spec:
 
       Output: the message is unchanged. The `CamelAwsS3Key` and 
`CamelAwsS3ETag` headers give the key and the ETag of the uploaded file.
 
-      Good to know: a file with the same key is replaced without warning. When 
`keyName` is set, the `file` header is ignored and every message replaces the 
same file. To copy files from `aws-s3-source` under their own names, set the 
`file` header from its `CamelAwsS3Key` header first. It also works with 
S3-compatible storage, such as MinIO, through `overrideEndpoint`, 
`uriEndpointOverride` and `forcePathStyle`.
+      Good to know: a file with the same key is replaced without warning. When 
`keyName` is set, the `file` header is ignored and every message replaces the 
same file. To copy files from `aws-s3-source` under their own names, set the 
`file` header from its `CamelAwsS3Key` header first. It also works with 
S3-compatible storage, such as MinIO, through `overrideEndpoint`, 
`uriEndpointOverride` and `forcePathStyle`. To encrypt the files with a key of 
AWS KMS, as a bucket policy may require,  [...]
     required:
       - bucketNameOrArn
       - region
@@ -124,6 +124,26 @@ spec:
         description: The key (the path of the file in the bucket) to write 
every message to, such as `reports/latest.csv`. When it is set, the `file` 
header is not used and each message replaces the file of the previous one. When 
it is not set, the key comes from the `file` header, or is a generated unique 
ID.
         example: reports/latest.csv
         type: string
+      useAwsKMS:
+        title: Use AWS KMS
+        description: "If true, each file is encrypted in S3 with a key of AWS 
KMS (SSE-KMS): the key in `awsKMSKeyId`. Use it when the bucket policy requires 
SSE-KMS, or a key of your own. The credentials need the permission to use the 
key (`kms:GenerateDataKey`), and readers of the files the permission to decrypt 
with it (`kms:Decrypt`). Without `awsKMSKeyId`, it has no effect."
+        type: boolean
+      awsKMSKeyId:
+        title: AWS KMS Key ID
+        description: The KMS key to encrypt the files with, as its key ID, 
such as `1234abcd-12ab-34cd-56ef-1234567890ab`, or its ARN, such as 
`arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab`. 
Use the ARN for a key of another AWS account. Only used when `useAwsKMS` is 
true.
+        example: 
arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
+        type: string
+        pattern: "^[A-Za-z0-9:/_-]+$"
+      useSSES3:
+        title: Use SSE-S3
+        description: If true, the upload asks S3 to encrypt each file with 
keys that S3 manages (SSE-S3, `AES256`), in the `x-amz-server-side-encryption` 
header that some bucket policies require. S3 encrypts new files this way 
anyway, unless the bucket is set to another encryption. Do not combine it with 
`useAwsKMS`.
+        type: boolean
+      storageClass:
+        title: Storage Class
+        description: "The storage class of the files: `STANDARD`, 
`STANDARD_IA`, `ONEZONE_IA`, `INTELLIGENT_TIERING`, `GLACIER_IR`, `GLACIER`, 
`DEEP_ARCHIVE` or `REDUCED_REDUNDANCY`. A file in `GLACIER` or `DEEP_ARCHIVE` 
must be restored before it can be read. When it is not set, the files are 
stored as `STANDARD`. A `CamelAwsS3StorageClass` header on the message takes 
precedence."
+        example: STANDARD_IA
+        type: string
+        pattern: "^[A-Z_]+$"
   dataTypes:
     in:
       headers:
@@ -177,4 +197,4 @@ spec:
                                 simple:
                                   expression: "${exchangeId}"
         - to:
-            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&forcePathStyle={{forcePathStyle}}&keyName={{?keyName}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&uriEndpointOverride={{?uriEndpointOverride}}&useDefaultCredentialsProvider={{useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{useProfil
 [...]
+            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&forcePathStyle={{forcePathStyle}}&keyName={{?keyName}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&uriEndpointOverride={{?uriEndpointOverride}}&useDefaultCredentialsProvider={{useDefaultCredentialsProvider}}&useProfileCredentialsProvider={{useProfil
 [...]
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
index 4e75c3c23..a3c7d0fce 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-streaming-upload-sink.kamelet.yaml
@@ -36,11 +36,11 @@ spec:
 
       Use it to store a stream of small records, such as log lines, events or 
sensor readings, as a few large files instead of one file per message. To 
upload one file per message, use `aws-s3-sink`.
 
-      Input: the body is added to the end of the current file as it is, as 
text, bytes or a stream. Nothing is put between two messages: end each message 
with a line break if the file must have one record per line. Headers are not 
used: the names of the files come from `keyName`.
+      Input: the body is added to the end of the current file as it is, as 
text, bytes or a stream. Nothing is put between two messages: end each message 
with a line break if the file must have one record per line. The names of the 
files come from `keyName`, not from headers.
 
       Output: the message is unchanged. The message that completes a file gets 
the `CamelAwsS3ETag` header of that file.
 
-      Good to know: a file is uploaded when it has `batchMessageNumber` 
messages or `batchSize` bytes, or when `streamingUploadTimeout` has passed; 
until then it is not in the bucket. With the default `namingStrategy` of 
`progressive`, the first file is named `keyName`, such as `logs/app.log`, and 
the next ones `logs/app-1.log`, `logs/app-2.log` and so on. With 
`restartingPolicy` set to `override`, a new run starts again from `keyName` and 
replaces the files of the earlier run.
+      Good to know: a file is uploaded when it has `batchMessageNumber` 
messages or `batchSize` bytes, or when `streamingUploadTimeout` has passed; 
until then it is not in the bucket. With the default `namingStrategy` of 
`progressive`, the first file is named `keyName`, such as `logs/app.log`, and 
the next ones `logs/app-1.log`, `logs/app-2.log` and so on. With 
`restartingPolicy` set to `override`, a new run starts again from `keyName` and 
replaces the files of the earlier run. To encryp [...]
     required:
       - bucketNameOrArn
       - region
@@ -149,6 +149,26 @@ spec:
         description: If true, the bucket name is put in the path of the 
address (`https://host/my-bucket/key`) instead of in the host name 
(`https://my-bucket.host/key`). S3-compatible storage such as MinIO often needs 
it.
         type: boolean
         default: false
+      useAwsKMS:
+        title: Use AWS KMS
+        description: "If true, each file is encrypted in S3 with a key of AWS 
KMS (SSE-KMS): the key in `awsKMSKeyId`. Use it when the bucket policy requires 
SSE-KMS, or a key of your own. The credentials need the permission to use the 
key (`kms:GenerateDataKey`), and readers of the files the permission to decrypt 
with it (`kms:Decrypt`). Without `awsKMSKeyId`, the key that AWS manages for S3 
(`aws/s3`) is used."
+        type: boolean
+      awsKMSKeyId:
+        title: AWS KMS Key ID
+        description: The KMS key to encrypt the files with, as its key ID, 
such as `1234abcd-12ab-34cd-56ef-1234567890ab`, or its ARN, such as 
`arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab`. 
Use the ARN for a key of another AWS account. Only used when `useAwsKMS` is 
true.
+        example: 
arn:aws:kms:eu-west-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
+        type: string
+        pattern: "^[A-Za-z0-9:/_-]+$"
+      useSSES3:
+        title: Use SSE-S3
+        description: If true, the upload asks S3 to encrypt each file with 
keys that S3 manages (SSE-S3, `AES256`), in the `x-amz-server-side-encryption` 
header that some bucket policies require. S3 encrypts new files this way 
anyway, unless the bucket is set to another encryption. Do not combine it with 
`useAwsKMS`.
+        type: boolean
+      storageClass:
+        title: Storage Class
+        description: "The storage class of the files: `STANDARD`, 
`STANDARD_IA`, `ONEZONE_IA`, `INTELLIGENT_TIERING`, `GLACIER_IR`, `GLACIER`, 
`DEEP_ARCHIVE` or `REDUCED_REDUNDANCY`. A file in `GLACIER` or `DEEP_ARCHIVE` 
must be restored before it can be read. When it is not set, the files are 
stored as `STANDARD`. A `CamelAwsS3StorageClass` header on the message takes 
precedence."
+        example: STANDARD_IA
+        type: string
+        pattern: "^[A-Z_]+$"
   dependencies:
     - "camel:aws2-s3"
     - "camel:kamelet"
@@ -157,4 +177,4 @@ spec:
       uri: kamelet:source
       steps:
         - to:
-            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&batchMessageNumber={{batchMessageNumber}}&batchSize={{batchSize}}&forcePathStyle={{forcePathStyle}}&keyName={{keyName}}&namingStrategy={{namingStrategy}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&restartingPolicy={{restartingPolicy}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&streamingUplo
 [...]
+            uri: 
"aws2-s3:{{bucketNameOrArn}}?accessKey=RAW({{?accessKey}})&autoCreateBucket={{autoCreateBucket}}&batchMessageNumber={{batchMessageNumber}}&batchSize={{batchSize}}&forcePathStyle={{forcePathStyle}}&keyName={{keyName}}&namingStrategy={{namingStrategy}}&overrideEndpoint={{overrideEndpoint}}&profileCredentialsName={{?profileCredentialsName}}&region={{region}}&restartingPolicy={{restartingPolicy}}&secretKey=RAW({{?secretKey}})&sessionToken=RAW({{?sessionToken}})&streamingUplo
 [...]

Reply via email to