- Can I use seferov/aws-bundle in a Laravel application?
- No, seferov/aws-bundle is a Symfony bundle, not a Laravel package. It registers AWS SDK clients into a Symfony dependency injection container via bundle extension and compiler passes, and it has no service provider, facade, publishable config, or package discovery support. For Laravel, require aws/aws-sdk-php v3 and bind Aws\Sdk as a singleton in a service provider driven by config/services.php and .env. You can reproduce the bundle's declarative multi-client config in a plain PHP array in about fifteen lines.
- How do I install seferov/aws-bundle?
- In a legacy Symfony 2, 3, or 4 app you would run composer require seferov/aws-bundle, register the bundle in AppKernel, and add an aws section to config.yml. Be aware the repository is archived and the last release was July 2018. On modern PHP or Symfony versions Composer will likely fail on platform constraints or force a dependency downgrade cascade. Freeze the lockfile if you must keep it running.
- Which Symfony versions does seferov/aws-bundle support?
- Support is scoped to Symfony 2, 3, and 4 only. There is no Symfony 5, 6, or 7 compatibility work, and the project is archived so none is planned. For current Symfony applications, use explicit service definitions for Aws\Sdk in services.yaml or adopt the actively maintained async-aws bundles instead.
- Does seferov/aws-bundle support PHP 8?
- No. The last release predates PHP 7.4 and PHP 8.x, and the archived repository has no dependency bumps or compatibility patches. Composer constraints from 2018 will typically block installation on PHP 8 or pull in conflicting Symfony components. Treat it as a legacy artifact and plan migration rather than patching it in place.
- How do I configure AWS credentials with seferov/aws-bundle?
- Credentials are declared in the bundle's YAML configuration, typically key, secret, and region under the aws key, and Symfony's %env()% syntax can pull them from environment variables. This was convenient in 2018 but lacks newer credential providers such as web identity, SSO, and ECS or EKS task roles. In Laravel, pass region and credentials from config/services.php and .env into the Aws\Sdk constructor instead.
- Which AWS services can I inject with seferov/aws-bundle?
- The bundle registers AWS SDK clients such as S3, SQS, and DynamoDB as container services so you can type-hint or fetch them from the Symfony container. It is essentially a thin configuration layer over aws/aws-sdk-php. Because the SDK versions it pins are old, expect missing modern regional endpoints, credential providers, and retry strategies.
- Is seferov/aws-bundle still maintained?
- No, the repository is archived with effectively zero issue-triage activity and a bus factor of one. There are no security patches, dependency bumps, or PHP 8 compatibility work, and the last release was July 2018. Do not adopt it for new projects, and treat any existing usage as technical debt to retire.
- What should Laravel developers use instead of seferov/aws-bundle?
- Use the official aws/aws-sdk-php v3 and bind Aws\Sdk as a singleton in a service provider, injecting narrow wrappers like S3Storage or SesMailer rather than the whole SDK. For plain object storage, Laravel's filesystem abstraction with the S3 driver needs no custom code at all. AsyncAws is a lighter, actively maintained alternative if you want smaller per-service clients.
- How do I test AWS integrations in Laravel without this bundle?
- Inject purpose-built client wrappers that depend on small interfaces so business code can be tested with mocks or fakes, and bind the real Aws\Sdk singleton only in production and staging. Point the SDK at LocalStack via an endpoint override in config for integration tests. This mirrors what the bundle tried to provide, minus the Symfony container coupling, and keeps tests fast and provider-agnostic.
- Is seferov/aws-bundle safe to run in production?
- It carries high technical risk because the archived bundle pins aws/aws-sdk-php v2 or early v3 and transitive HTTP layers such as Guzzle that may hold unpatched CVEs. It also lacks modern credential providers and retry and backoff behavior expected in current AWS environments. If a legacy Symfony app must keep it, freeze the lockfile, avoid version drift, and budget a migration to aws/aws-sdk-php v3 or async-aws.