Weave Code
Async Aws Bundle Laravel Package
async-aws/async-aws-bundle
A small Symfony bundle for AsyncAws that handles client configuration and autowiring. It registers AsyncAws clients as Symfony services, loads credentials and endpoint settings from config or environment variables, and lets you inject any AWS client directly into your services.
[READ ONLY] AsyncAws + Symfony = <3
Frequently asked questions about Async Aws Bundle
- Can I use async-aws/async-aws-bundle in a Laravel application?
- The package is a Symfony HttpKernel bundle, and its configuration tree and DI extension only run through Symfony's Kernel::registerBundles and ContainerBuilder lifecycle. Laravel has no equivalent bundle auto-discovery or config-tree compilation, so the bundle is effectively inert unless you manually boot Symfony's DI container inside a service provider. That is not recommended because it adds Symfony runtime dependencies for code Laravel never calls. Use the framework-agnostic AsyncAws client packages with a Laravel service provider instead.
- How do I install AsyncAws in Laravel without the Symfony bundle?
- Install only the granular client packages you need, such as async-aws/s3, async-aws/sqs, or async-aws/dynamo-db, via Composer. Create a config/async_aws.php file for region, credentials, and endpoint settings, then register a singleton service provider that constructs each client and binds its interface. Laravel's container autowiring will then resolve those clients in controllers, jobs, and listeners.
- What does the AsyncAws Symfony bundle actually configure?
- It registers AsyncAws clients as Symfony services and handles autowiring so you can inject interfaces such as S3ClientInterface directly. It also centralizes client options, credentials, endpoint settings, credential providers and caching, and SSM parameter loading from config or environment variables. Most of the AWS client substance lives in async-aws/core and the per-service packages, not in the bundle.
- Does async-aws/async-aws-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Symfony and does not ship a Laravel service provider, facade, or package discovery metadata. For Laravel 10 or 11, install the AsyncAws client packages directly and wire them through your own provider. The Symfony bundle's Laravel version support is therefore not applicable.
- Which AsyncAws clients can I inject into Laravel services?
- You can bind any AsyncAws client package you install, including S3, SQS, SES, and DynamoDB clients, as singletons in Laravel's container. Register the concrete client or its interface, such as S3ClientInterface or SqsClientInterface, in a service provider. Controllers, jobs, and event listeners can then type-hint those interfaces and receive the configured client automatically.
- How should I manage AWS credentials in Laravel with AsyncAws?
- Read credentials, region, and endpoint values from Laravel's config and environment, then pass them into each AsyncAws client constructor. If you need the bundle's credential_provider, credential_provider_cache, SSM parameter loading, or Secrets Manager behavior, plan to reimplement that logic in your provider. A cache-backed credential provider is the largest piece of free work you give up by skipping the Symfony bundle, and a solid version is roughly a one-to-two-day task.
- Can I test AsyncAws clients in Laravel without LocalStack?
- Yes. AsyncAws ships a MockClient that lets you replace the real client in unit or feature tests and assert the requests and responses without running LocalStack. This is a practical advantage over the mocking story in aws-sdk-php. Bind the MockClient in Laravel's test container or swap it inside the test case.
- What are the alternatives to async-aws/async-aws-bundle for Laravel?
- The realistic options are the official AWS SDK for PHP or the framework-agnostic AsyncAws client packages wired through your own Laravel service provider. The Symfony bundle itself is not a Laravel alternative because Laravel never invokes its bundle lifecycle. AsyncAws is also not a drop-in replacement for AWS SDK v3, so verify S3 multipart and transfer-manager behavior, SQS FIFO and partial-batch handling, DynamoDB paginators and waiters, presigned URL expiry, and observability hooks before choosing it.
- How does AsyncAws async behavior work under Laravel PHP-FPM or Octane?
- AsyncAws returns promises that are resolved through Symfony HttpClient's curl multiplexing. Under PHP-FPM with Laravel's synchronous request lifecycle, the concurrency benefit is real but bounded and mostly helps batch or concurrent AWS calls inside a job or command. Under Octane the picture can improve, but long-lived container state and connection reuse need explicit verification.
- Is async-aws/async-aws-bundle actively maintained and safe for production?
- The repository shows CI and backward-compatibility checks, so the bundle is maintained as a small integration layer. However, it is a roughly 26-star bundle with no listed dependents and no Laravel presence, so its production risk for Laravel teams is high. Upstream AsyncAws is a small-maintainer community MIT project without a vendor SLA, so assess bus factor, roadmap responsiveness, and supply-chain hygiene before relying on it.
Weaver
How can I help you explore Laravel packages today?