-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] data prepper secret extensions #5202
[DOC] data prepper secret extensions #5202
Conversation
Signed-off-by: George Chen <[email protected]>
Signed-off-by: George Chen <[email protected]>
Signed-off-by: George Chen <[email protected]>
Signed-off-by: George Chen <[email protected]>
Signed-off-by: George Chen <[email protected]>
| Option | Required | Type | Description | | ||
|:-----------------|:---------|:---------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| secret_id | Yes | String | The AWS secret name or ARN. | | ||
| region | No | String | The AWS region of the secret. Defaults to `us-east-1`. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chenqi0805 , Does this default to us-east-1
? I'd think it uses the AWS SDK's default. This can be the AWS_REGION
environment variable or us-east-1
. Do we know for sure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We do default to us-east-1
the same way as the S3 DLQ in opensearch sink
refresh_interval: <YOUR_REFRESH_INTERVAL_2> | ||
``` | ||
|
||
###### Secrets refreshment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not use "refreshment" here. A drink may be a refreshment. :)
I'd prefer "Refreshing secrets" or "Automatically refreshing secrets".
|
||
###### Secrets refreshment | ||
|
||
For each individual secret configuration, the latest secret value is polled on a regular interval to support secrets refreshment in AWS Secrets Manager. The refreshed secret values are utilized by certain pipeline plugins to refresh their components, e.g. connection and authentication to the backend service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
support secrets refreshment in
change to
support refreshing secrets in
| secret_id | Yes | String | The AWS secret name or ARN. | | ||
| region | No | String | The AWS region of the secret. Defaults to `us-east-1`. | | ||
| sts_role_arn | No | String | The AWS Security Token Service (AWS STS) role to assume for requests to AWS Secrets Manager. Defaults to `null`, which will use the [standard SDK behavior for credentials](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html). | | ||
| refresh_interval | No | Duration | The refreshment interval for AWS secrets extension plugin to poll new secret values. See [Secrets refreshment](#secrets-refreshment) for details. Defaults to `PT1H`. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my note below. Let's change the link from "Secrets refreshment" to "Automatically refreshing secrets"
|
||
In `pipelines.yaml`, secret values can be referenced within pipeline plugins using the following formats: | ||
|
||
* plaintext: `${{aws_secrets:<YOUR_SECRET_CONFIG_ID>}}`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be clearly state in the preceding paragraph that users need to replace <YOUR_SECRET_CONFIG_ID> including the <>.
Signed-off-by: George Chen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @chenqi0805 !
* ADD: extension docs in data-prepper-config Signed-off-by: George Chen <[email protected]> * MAINT: updating secrets extension doc Signed-off-by: George Chen <[email protected]> * MAINT: fix links Signed-off-by: George Chen <[email protected]> * MAINT: fix one more dead link Signed-off-by: George Chen <[email protected]> * MAINT: renaming Signed-off-by: George Chen <[email protected]> * Update configuring-data-prepper.md * Update pipelines.md --------- Signed-off-by: George Chen <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> (cherry picked from commit 9617548) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* ADD: extension docs in data-prepper-config * MAINT: updating secrets extension doc * MAINT: fix links * MAINT: fix one more dead link * MAINT: renaming * Update configuring-data-prepper.md * Update pipelines.md --------- (cherry picked from commit 9617548) Signed-off-by: George Chen <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Naarcha-AWS <[email protected]>
* ADD: extension docs in data-prepper-config Signed-off-by: George Chen <[email protected]> * MAINT: updating secrets extension doc Signed-off-by: George Chen <[email protected]> * MAINT: fix links Signed-off-by: George Chen <[email protected]> * MAINT: fix one more dead link Signed-off-by: George Chen <[email protected]> * MAINT: renaming Signed-off-by: George Chen <[email protected]> * Update configuring-data-prepper.md * Update pipelines.md --------- Signed-off-by: George Chen <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]>
Description
This PR adds Data Prepper 2.5 documentation on AWS secrets extension plugin details into both data-prepper-config YAML and pipelines configuration YAML.
Issues Resolved
Closes #5115 .
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.