feat(ai): Update docs to reflect AWS identity usage for AWS Guardrails Plugin#5514
Open
tysoekong wants to merge 1 commit into
Open
feat(ai): Update docs to reflect AWS identity usage for AWS Guardrails Plugin#5514tysoekong wants to merge 1 commit into
tysoekong wants to merge 1 commit into
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Use the AI AWS Guardrails plugin how-to to describe using either static AWS access keys or an AWS IAM role attached to the workload (for example, EKS Pod Identity / instance profile) when authenticating the plugin to AWS.
Changes:
- Expands the AWS prerequisites to describe multiple AWS identity options.
- Adds separate configuration guidance for static access keys vs. workload-attached IAM roles.
- Adds a note about optionally assuming a secondary role via
aws_assume_role_arn.
Comment on lines
+56
to
60
| To complete this tutorial, you will need either: | ||
|
|
||
| 1. The following credentials: | ||
|
|
||
| * AWS_REGION |
Comment on lines
+149
to
+151
| Whereas for an assigned Web Identity / Instance Profile / etc IAM Role, simply leave the `aws_access_key_id` and `aws_secret_access_key` | ||
| fields empty. In this setup example, Kong will run through the [standard credentials provider chain](https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/guide_credentials_default_chain.html) and select the first successfully | ||
| authenticated credential set. |
Comment on lines
+161
to
+171
| variables: | ||
| guardrails_id: | ||
| value: $GUARDRAILS_ID | ||
| guardrails_version: | ||
| value: $GUARDRAILS_VERSION | ||
| aws_region: | ||
| value: $AWS_REGION | ||
| aws_access_key_id: | ||
| value: $AWS_ACCESS_KEY_ID | ||
| aws_secret_access_key: | ||
| value: $AWS_SECRET_ACCESS_KEY |
Comment on lines
+174
to
+175
| You can also set the `aws_assume_role_arn` to also use the assigned identity to assume a **second** role, | ||
| either in the same AWS account or in another. |
|
|
||
| Now, we can configure our AI AWS Guardrails plugin to enforce content moderation policies by attaching a predefined Bedrock guardrail to requests. | ||
|
|
||
| For static IAM keys, configure the plugin as follows: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds (vague) instructions for configuring the AI AWS Guardrails with an assigned AWS Identity (e.g. https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html, IAM Instance Profile, etcetera).
Please can you proof read and adjust so that it fits the required grammar :)
Preview Links
Checklist
descriptionentry in frontmatter.