Update wiki Home page for aws-secrets-manager-sink

gitea_admin 2026-03-11 14:34:39 +00:00
parent 80bfffb7cf
commit 0e95575076

39
Home.md

@ -1,21 +1,32 @@
# Deploy the Project on CamelX Platform
# AWS Secrets Manager Sink
Deploy on CamelX Platform in three steps
Create a secret in AWS Secrets Manager.
## Step 1: Create a release
From the project space, click on **"Create a release"**
## Metadata
The new version is automatically available in the list
| Property | Value |
|----------|-------|
| Type | sink |
| Group | AWS Secrets Manager |
| Namespace | AWS |
| Support Level | Stable |
| Provider | Apache Software Foundation |
## Step 2: Deploy
Click on **"Deploy"**
## Properties
- **Version:** Select the desired release
- **Environment:** Choose `Development`, `Staging`, or `Production`
- **Configuration:** Select the configuration source
- **Resources:** Set CPU and Memory
| Name | Type | Required | Default | Description |
|------|------|----------|---------|-------------|
| `accessKey` | string | | | The access key obtained from AWS. |
| `secretKey` | string | | | The secret key obtained from AWS. |
| `region` | string | ✓ | | The AWS region to access. |
| `useDefaultCredentialsProvider` | boolean | | `false` | Set whether the Secrets Manager client should expect to load credentials through a default credentials provider or to expect static credentials to be passed in. |
| `useProfileCredentialsProvider` | boolean | | `false` | Set whether the Secrets Manager client should expect to load credentials through a profile credentials provider. |
| `useSessionCredentials` | boolean | | `false` | Set whether the Secrets Manager client should expect to use Session Credentials. This is useful in situation in which the user needs to assume a IAM role for doing operations in Secrets Manager. |
| `profileCredentialsName` | string | | | If using a profile credentials provider this parameter will set the profile name. |
| `sessionToken` | string | | | Amazon AWS Session Token used when the user needs to assume a IAM role. |
## Step 3: Expose
Enable **"Expose"**
## Dependencies
Choose an **API Gateway** (Internal, Public, etc.)
- `camel:core`
- `camel:aws-secrets-manager`
- `camel:kamelet`