- Does skydiablo/aws-bundle work with Laravel out of the box?
- No. The package is a Symfony bundle, so it ships container configuration and service wiring for the Symfony kernel rather than a Laravel service provider, facade, or publishable config. Laravel does not read Symfony bundle extension classes, so you would have to manually register and wire the services yourself. Unless a Laravel service provider is present in the source, treat Laravel compatibility as unproven and prefer the official AWS SDK for PHP.
- How do I install skydiablo/aws-bundle?
- You would install it with composer require skydiablo/aws-bundle and then register the bundle in your Symfony kernel or bundles.php file. Before installing, read composer.json to confirm the PHP, Symfony, and AWS SDK version constraints, since the package has zero stars and zero dependents and may not have been updated recently. In a Laravel project, installation alone will not wire anything up.
- Which AWS services does skydiablo/aws-bundle actually wrap?
- The package blurb mentions S3, SES, and SQS, but the README excerpt is empty, so the documented surface area is unclear. Because there is no published documentation or usage examples, you should read the source to confirm exactly which clients and helpers exist. Do not assume coverage for other services such as DynamoDB, SNS, or CloudWatch.
- Does this bundle use AWS SDK for PHP v3?
- That is not documented and must be verified by inspecting the composer.json require block and the source imports. A stale SDK major version can block PHP or framework upgrades and may miss security fixes, so this is a critical check. If the constraint pins an old SDK line, adopting the bundle means owning a dependency upgrade path yourself.
- Is skydiablo/aws-bundle safe to use in production?
- Treat it as high risk. The package has no stars, no dependents, no visible test suite or CI, and no community validation, which means failure modes are largely undocumented. Pulling an unmaintained package also adds supply-chain exposure. If you must use it, isolate it behind an internal adapter, pin the version, and add your own integration tests.
- What should Laravel developers use instead for AWS integration?
- Use the official aws/aws-sdk-php directly, combined with Laravel's filesystem disks and the Flysystem S3 adapter for file storage. For queues, Laravel's native SQS queue driver covers most use cases, and mail can go through SES via the built-in mail transport. These options are first-party or widely adopted, documented, and actively maintained.
- How are credentials, regions, and retries handled by this bundle?
- Credential and region handling is not documented, so you cannot assume it supports modern providers such as IAM roles, ECS or EKS container credentials, or the SDK's default credential chain. Retry and timeout behavior is likewise unclear, which can cause reliability surprises under load. Verify the source, and prefer configuring the AWS SDK directly so you control these settings explicitly.
- Which PHP and Symfony versions does skydiablo/aws-bundle support?
- Check the composer.json constraints for php, symfony/framework-bundle, and aws/aws-sdk-php before attempting an install. There is no published compatibility matrix and no CI evidence, so support for current PHP or Symfony releases is unlikely to be guaranteed. If your project runs a modern stack, expect to test, patch, or fork the package.
- Is skydiablo/aws-bundle still maintained?
- There is no evidence of an active maintainer, issue triage, or recent releases, and zero dependents means no ecosystem pressure to keep it compatible. If you adopt it, plan to vendor or fork it and own SDK, PHP, and framework upgrades internally. Realistically, your team becomes the support team.
- How do I migrate away from or isolate skydiablo/aws-bundle later?
- Wrap every call behind your own interface or adapter rather than injecting bundle services directly into business logic. That way you can swap the implementation for the official AWS SDK without rewriting application code. Start with a time-boxed spike in a non-production branch, scan the dependency tree and license, and only adopt the bundle if it clearly beats direct SDK usage.