Skip to content
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.

Sign up for GitHub

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

fix(docs): broken link to blueprint in aws-plugin #580

Merged
merged 1 commit into from
Feb 11, 2025
Merged

fix(docs): broken link to blueprint in aws-plugin #580

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/main/resources/doc/io.kestra.plugin.aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ To set up the credentials in the task, you can use:
- Or the `stsRoleArn`, `stsRoleExternalII` and `stsRoleSessionName` properties for STS assume role credentials.

When defining credentials in the task, this is a best practice to use [secrets](https://kestra.io/docs/concepts/secret).
Check the blueprints such as [this one](https://kestra.io/blueprints/118-extract-data-from-an-api-and-load-it-to-s3-on-schedule-(every-friday-afternoon)),
Check the blueprints such as [this one](https://kestra.io/blueprints/api-to-s3),
showing how you can reference secrets in your AWS tasks.

The [default credentials provider chain](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials-chain.html) is an AWS credentials provider chain
Expand Down
Loading