Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Bedrock Laravel Package

prism-php/bedrock

Amazon Bedrock driver for Prism, bringing AWS-hosted foundation models like Claude, Llama, Titan, and Mistral into Laravel AI workflows. Configure credentials and use Prism’s unified API for text generation and embeddings.

View on GitHub
Deep Wiki
Context7

AWS Bedrock provider for Prism

Frequently asked questions about Bedrock
What is prism-php/bedrock used for?
It is the AWS Bedrock provider for Prism, the Laravel/PHP LLM package. It lets Laravel applications call Bedrock-hosted foundation models such as Anthropic Claude, Amazon Titan, Meta Llama, and Mistral through Prism's unified API. Use it when you want Bedrock models without writing provider-specific integration code.
How do I install prism-php/bedrock in a Laravel app?
Install it with Composer in a Laravel project that already uses Prism or is adding Prism, for example by requiring prism-php/bedrock and the compatible Prism package. Then configure AWS credentials and region and select Bedrock as the Prism provider. Because v1.8.0 updates the Prism dependency, verify that your installed Prism version satisfies the package constraint.
Which AWS Bedrock models can I use with this package?
The package exposes Bedrock-hosted models including Anthropic Claude, Amazon Titan, Meta Llama, and Mistral. Exact model availability depends on your AWS region and the models enabled in your Bedrock account. Select the Bedrock model ID you have access to through Prism's provider configuration.
How do I configure AWS credentials and region for Bedrock in Laravel?
Configure your AWS access key, secret key, and region in your Laravel environment or configuration, then point Prism at the Bedrock provider. Keep credentials out of source control and use IAM permissions scoped to the Bedrock models you invoke. Confirm the exact configuration keys in the package README because they follow Prism's provider configuration.
Does prism-php/bedrock support streaming and tool calling?
Yes, it supports streaming and tool calling where the selected Bedrock model allows those features. Support is model-dependent, so verify that the specific Claude, Llama, Titan, or Mistral model you choose supports the capability you need. Prism's unified API lets you use these features without provider-specific application code.
Which Laravel and PHP versions does prism-php/bedrock support?
The package is built for Laravel/PHP applications using Prism, but the exact Laravel and PHP support matrix should be confirmed from composer.json for the version you install. v1.8.0 updates the Prism dependency, so also verify that your locked Prism version is compatible. Test the upgrade in a branch before changing production.
How do I switch from another Prism provider to Bedrock?
Keep your Prism calls and change the configured provider to Bedrock, then supply AWS credentials, region, and a Bedrock model ID. Prism's unified API is designed to avoid rewriting application code, but you should still validate prompts, tool schemas, and model-specific behavior. Run regression tests for streaming and tool calling after switching providers.
What changed in prism-php/bedrock v1.8.0 and could it break existing tool calling?
v1.8.0 aligns the Prism dependency and includes parameterless tool improvements. No breaking changes or deprecations are called out in the release notes provided, but the Prism version update can create transitive dependency risk. Review Composer constraints and regression-test both parameterless and parameterized tool flows.
How should I test Bedrock tool calling and parameterless tools before production?
Test in a non-production branch with your locked Prism version and valid AWS Bedrock credentials. Cover parameterless and parameterized tool flows, streaming, model selection, credential errors, provider API failures, and malformed tool schemas. Add observability around tool selection, invocation inputs and outputs, latency, and failure rates before production rollout.
Is prism-php/bedrock production-ready, and what alternatives exist?
It appears suitable for Laravel applications already using or adopting Prism, with active upstream maintenance indicated by the v1.8.0 release. Treat it as production-capable after verifying Composer constraints, AWS credentials, model access, and tool-calling tests in staging. Alternatives include calling AWS Bedrock directly through the AWS SDK or using another Bedrock integration, but prism-php/bedrock is the natural choice when you want Prism's unified Laravel API.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections