Update wiki Home page for aws-ses-sink

gitea_admin 2026-03-11 14:34:40 +00:00
parent 3fc5521bcf
commit 6977b7ad38

40
Home.md

@ -1,21 +1,33 @@
# Deploy the Project on CamelX Platform
# AWS SES Sink
Deploy on CamelX Platform in three steps
Send email through the Amazon Simple Email Service (SES).
## 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 SES |
| 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 |
|------|------|----------|---------|-------------|
| `from` | string | ✓ | | From address |
| `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` | If true, the SES client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key). |
| `useProfileCredentialsProvider` | boolean | | `false` | Set whether the SES client should expect to load credentials through a profile credentials provider. |
| `useSessionCredentials` | boolean | | `false` | Set whether the SES 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 SES. |
| `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:aws2-ses`
- `camel:kamelet`