AWS Bedrock
Connect AWS Bedrock to your company operations. Review required fields, credential setup and how this connector works in Zild.
Connect AWS Bedrock to your company operations.
Where to configure
Open Zild Admin → Integrations → Connectors, find the provider and use Configure or Edit. Enter the data from this guide, enable the connector for the workflow and save.
Your company credentials
Customers must obtain and configure their own API keys or the authentication method required by this connector. The Zild subscription is based on company size; external service usage is billed separately by the respective provider. You do not need to configure connectors your operation does not use.
Required fields
These requirements are the data needed by the workflow using the connector. Generic saving may accept empty fields that are only required when an operation runs. Saving does not confirm that the provider accepts the credential.
| Field | Workflow requirement |
|---|---|
CredentialsJson | JSON with region, accessKeyId, secretAccessKey and sessionToken for temporary credentials. |
How to obtain credentials
- Ask the AWS administrator for an IAM identity with access to required Bedrock models and operations in the selected region.
- Obtain temporary credentials through an authorized IAM/STS session, or an access key from a dedicated IAM user if that is company policy. Do not use root credentials.
- Copy region, accessKeyId, secretAccessKey and, for temporary sessions, sessionToken into CredentialsJson. Update credentials before they expire.
- Check model access in Bedrock and select the available model or inference profile in Zild.
How it works in Zild
This connector signs requests using AWS SigV4. A Bedrock Bearer API key does not replace the IAM JSON required by this implementation.
How to verify the configuration
After saving, use the matching workflow (query, agent, call or processing) to verify access. If it fails, check the credential, permissions and selected provider resource. For limited or legacy types, confirm availability with your administrator before use.
When editing, Zild displays protected credentials as asterisks. Preserve the masked value to keep the current credential or paste a new credential to replace it.
Agent execution and cost management
Permission to invoke a model does not prove access to financial reports. Keep SigV4-compatible IAM JSON in the execution connector. Temporary credentials expire: define who refreshes the session without assuming automatic renewal by Zild.
Configure and validate financial access separately in AI Providers. A conversation test does not prove access to reports.
Configure FinOps: credentials, coverage and limits by provider
A separate test for each access
- Run a short request with synthetic data and the chosen model. Record status, time and connection without copying the secret into logs or messages.
- If enabling FinOps, check period, currency, scope and latest synchronization. Compare the report with the provider account; missing data does not mean zero cost.
- When replacing a credential, retest dependent workflows and coordinate revocation of the old one with its owner. Saving does not confirm authentication or permissions.
Official authentication reference — checked October 28, 2026