docs correction
This commit is contained in:
parent
b06d48e1f8
commit
c8182cea17
|
@ -25,7 +25,7 @@ Unless your credentials belong to the root account, the principal will need to b
|
|||
|
||||
- `bedrock:InvokeModel`
|
||||
- `bedrock:InvokeModelWithResponseStream`
|
||||
- `bedrock:GetModelInvocationLogging`
|
||||
- `bedrock:GetModelInvocationLoggingConfiguration`
|
||||
- The proxy needs this to determine whether prompt/response logging is enabled. By default, the proxy won't use credentials unless it can conclusively determine that logging is disabled, for privacy reasons.
|
||||
|
||||
Use the IAM console or the AWS CLI to attach these policies to the principal associated with the credentials.
|
||||
|
@ -45,4 +45,4 @@ The account must have access to _all_ of the following models or the proxy can't
|
|||
|
||||
By default, the proxy will refuse to use keys if it finds that logging is enabled, or if it doesn't have permission to check logging status.
|
||||
|
||||
If you can't attach the `bedrock:GetModelInvocationLogging` policy to the principal, you can set the `AWS_ASSUME_LOGGING_DISABLED` environment variable to `true` to force the proxy to use the keys anyway. A warning will appear on the info page when this is enabled.
|
||||
If you can't attach the `bedrock:GetModelInvocationLoggingConfiguration` policy to the principal, you can set the `AWS_ASSUME_LOGGING_DISABLED` environment variable to `true` to force the proxy to use the keys anyway. A warning will appear on the info page when this is enabled.
|
||||
|
|
Loading…
Reference in New Issue