fix(ai-gateway): AI entities pages audit - #6807
Open
tomek-labuk wants to merge 4 commits into
Open
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
cloudjumpercat
approved these changes
Aug 25, 2026
cloudjumpercat
left a comment
cloudjumpercat
left a comment
Contributor
There was a problem hiding this comment.
A few nitpicks/link fixes. I flagged it in a comment, but just wanted to mention that some of the schema links didn't seem active and the linked params were missing from the schema in the docs. I"m guessing that's because we haven't updated the schema in the docs yet? Either way, I'm approving this just in case the schema will be updated later.
|
|
||
| - q: How do I authenticate to an upstream service that requires AWS IAM (SigV4) signing? | ||
| a: | | ||
| Configure [`config.upstream.auth`](#schema-aigateway-mcpserver-config-upstream) with `type: aws`. {{site.ai_gateway}} |
Contributor
There was a problem hiding this comment.
I'm not seeing upstream.auth in the schema, maybe the schema in the docs hasn't been updated yet? Just wanted to flag this.
Contributor
There was a problem hiding this comment.
Actually, that applies to all the schema links in this FAQ, I can't find any of them in the schema in the docs.
Comment on lines
+436
to
+438
| * Static IAM user credentials, `access_key_id` and `secret_access_key`, optionally paired with a `session_token` for temporary credentials. | ||
| * Environment auto-detection when you omit `access_key_id` and `secret_access_key`, for example, an EC2 instance profile or environment variables. | ||
| * Role assumption through `assume_role_arn` and `role_session_name`, layered on top of either credential source. Recommended for production use and cross-account access. |
Contributor
There was a problem hiding this comment.
Suggested change
| * Static IAM user credentials, `access_key_id` and `secret_access_key`, optionally paired with a `session_token` for temporary credentials. | |
| * Environment auto-detection when you omit `access_key_id` and `secret_access_key`, for example, an EC2 instance profile or environment variables. | |
| * Role assumption through `assume_role_arn` and `role_session_name`, layered on top of either credential source. Recommended for production use and cross-account access. | |
| * Static IAM user credentials, `access_key_id` and `secret_access_key`, optionally paired with a `session_token` for temporary credentials | |
| * Environment auto-detection when you omit `access_key_id` and `secret_access_key`, for example, an EC2 instance profile or environment variables | |
| * Role assumption through `assume_role_arn` and `role_session_name`, layered on top of either credential source. Recommended for production use and cross-account access. |
| Create an AI Policy when you want to add governance, security, transformation, or observability to {{site.ai_gateway}} traffic. For example: | ||
| - Redact sensitive data with [AI PII Sanitizer](/ai-gateway/policies/ai-sanitizer/) | ||
| - Manage request volume with [AI Rate Limiting Advanced](/ai-gateway/policies/ai-rate-limiting-advanced/) | ||
| - Validate prompts with [AI Prompt Guard](/ai-gateway/policies/ai-prompt-guard/) or [other guardrail Policies](/ai-gateway/#guardrails-and-content-safety) |
Contributor
There was a problem hiding this comment.
Suggested change
| - Validate prompts with [AI Prompt Guard](/ai-gateway/policies/ai-prompt-guard/) or [other guardrail Policies](/ai-gateway/#guardrails-and-content-safety) | |
| - Validate prompts with [AI Prompt Guard](/ai-gateway/policies/ai-prompt-guard/) or [other guardrail Policies](/ai-gateway/policies/?terms=guardrail) |
The original link didn't go anywhere
| - Validate prompts with [AI Prompt Guard](/ai-gateway/policies/ai-prompt-guard/) or [other guardrail Policies](/ai-gateway/#guardrails-and-content-safety) | ||
| - Track requests and responses for observability with [logging Policies](/ai-gateway/policies/?category=logging) | ||
|
|
||
| To control access and verify identity, assign an [AI Identity Provider](/ai-gateway/entities/ai-identity-provider/) instead of an AI Policy. |
Contributor
There was a problem hiding this comment.
Suggested change
| To control access and verify identity, assign an [AI Identity Provider](/ai-gateway/entities/ai-identity-provider/) instead of an AI Policy. | |
| To control access and verify identity, assign an [AI Auth Strategy](/ai-gateway/entities/ai-auth-strategy/) instead of an AI Policy. |
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
2 participants
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
Fixes #issue
Preview Links
Checklist
descriptionentry in frontmatter.