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

acosentino pushed a commit to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git

commit 3798fa6662691971ed2d3373446f94816694499c
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Fri Jan 31 10:01:06 2025 +0100

    Kamelets Catalog - Make the description a one liner - AWS STS Assume Role 
Action
    
    Signed-off-by: Andrea Cosentino <anco...@gmail.com>
---
 .../aws-sts-assume-role-action-description.adoc    | 27 ++++++++++++++++++++++
 kamelets/aws-sts-assume-role-action.kamelet.yaml   | 11 +--------
 .../aws-sts-assume-role-action.kamelet.yaml        | 11 +--------
 3 files changed, 29 insertions(+), 20 deletions(-)

diff --git 
a/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc 
b/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc
new file mode 100644
index 00000000..8813d017
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc
@@ -0,0 +1,27 @@
+== AWS STS Assume Role Action Kamelet Description
+
+=== Authentication methods
+
+In this Kamelet you have the possibility of avoiding the usage of explicit 
static credentials by specifying the useDefaultCredentialsProvider option and 
set it to true.
+
+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.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the 
environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials. 
+ 
+You have also the possibility of using Profile Credentials Provider, by 
specifying the useProfileCredentialsProvider option to true and 
profileCredentialsName to the profile name.
+
+Only one of access key/secret key or default credentials provider could be used
+
+For more information about this you can look at 
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS
 credentials documentation]
+
+=== Required Headers
+
+In this Kamelet you have to specify the following headers:
+
+- `role-arn` / `ce-role-arn` property to specify the role ARN you want to 
assume.
+- `role-session-name` / `ce-role-session-name` property to specify the role 
Session name you want to use.
diff --git a/kamelets/aws-sts-assume-role-action.kamelet.yaml 
b/kamelets/aws-sts-assume-role-action.kamelet.yaml
index 7648a601..72a25098 100644
--- a/kamelets/aws-sts-assume-role-action.kamelet.yaml
+++ b/kamelets/aws-sts-assume-role-action.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
 spec:
   definition:
     title: "AWS STS Assume Role Action"
-    description: |-
-      Assume a role through STS
-
-      Access Key/Secret Key are the basic method for authenticating to the AWS 
STS Service. These parameters are optional because the Kamelet provides the 
'useDefaultCredentialsProvider'.
-      
-      When using a default Credentials Provider the Translate client will load 
the credentials through this provider and won't use the static credential. This 
is reason for not having the access key and secret key as mandatory parameter 
for this Kamelet.
-      
-      In the headers, you have to specify the `role-arn` / `ce-role-arn` 
property to specify the role ARN you want to assume.
-
-      In the headers, you have to specify the `role-session-name` / 
`ce-role-session-name` property to specify the role Session name you want to 
use.
+    description: Assume a role through STS
     required:
       - region
     type: object
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
index 7648a601..72a25098 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
 spec:
   definition:
     title: "AWS STS Assume Role Action"
-    description: |-
-      Assume a role through STS
-
-      Access Key/Secret Key are the basic method for authenticating to the AWS 
STS Service. These parameters are optional because the Kamelet provides the 
'useDefaultCredentialsProvider'.
-      
-      When using a default Credentials Provider the Translate client will load 
the credentials through this provider and won't use the static credential. This 
is reason for not having the access key and secret key as mandatory parameter 
for this Kamelet.
-      
-      In the headers, you have to specify the `role-arn` / `ce-role-arn` 
property to specify the role ARN you want to assume.
-
-      In the headers, you have to specify the `role-session-name` / 
`ce-role-session-name` property to specify the role Session name you want to 
use.
+    description: Assume a role through STS
     required:
       - region
     type: object

Reply via email to