- Is reconnect/s3bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a native Laravel package. It exposes S3 configuration through Symfony's DI extension and config/packages YAML namespace. Laravel has no equivalent bundle or container-extension concept, so it cannot be consumed as-is in a Laravel app without an adapter.
- Can I install reconnect/s3bundle in a Laravel app?
- Not directly in a framework-idiomatic way. You would need to port its config semantics into a Laravel ServiceProvider and bind your own S3 client or filesystem disk. At that point the bundle contributes little beyond a YAML schema, so most Laravel teams should use aws/aws-sdk-php or league/flysystem-aws-s3-v3 directly.
- Which Symfony and PHP versions does reconnect/s3bundle support?
- The available context does not document verified Symfony or PHP version constraints, and there is no evidence of CI testing those constraints. Treat compatibility as unverified until you check composer.json and run a spike in a throwaway Symfony skeleton. Pin exact versions before relying on it.
- Does reconnect/s3bundle support presigned URLs, multipart uploads, and streaming?
- This is not documented in the provided context. Whether you get presigned URLs, multipart thresholds, streaming uploads, and StreamInterface semantics depends on whether the bundle wraps the raw AWS SDK or Flysystem. Verify those features against a MinIO or localstack round-trip before adopting it.
- Does reconnect/s3bundle use the AWS SDK directly or Flysystem?
- The context does not confirm whether it is a raw aws/aws-sdk-php wrapper or Flysystem-backed. That distinction matters because it determines presigned URL behavior, multipart handling, streaming semantics, and credential configuration. Inspect the source or run a spike before assuming either implementation.
- How do I configure multiple S3 buckets with reconnect/s3bundle?
- Multiple buckets or clients are not confirmed in the available documentation. The Symfony config namespace suggests configuration is possible, but there is no documented evidence that multiple clients are supported or that a default bucket is avoided. Test this explicitly if your app needs more than one bucket.
- Does reconnect/s3bundle support IAM roles, ECS task roles, or only static credentials?
- The package documentation does not state which credential providers are exposed. The underlying AWS SDK supports IAM roles, ECS task roles, SSO, and profiles, but the bundle may only expose static key and secret configuration. Verify credential-chain support before deploying to role-based infrastructure.
- Is reconnect/s3bundle maintained and tested?
- The project has very low adoption, with 4 stars and zero dependents, and there is no evidence of a CI pipeline or test suite. It is owned by a single small agency, so treat it as effectively unmaintained and plan for a fork if you adopt it. The MIT license removes legal friction but not stewardship risk.
- What are alternatives to reconnect/s3bundle for Laravel S3 uploads?
- For Laravel, use the built-in S3 filesystem driver with league/flysystem-aws-s3-v3, or use aws/aws-sdk-php directly for lower-level control. Laravel's Storage facade already provides uploads, downloads, temporary URLs, and file management against S3-compatible storage. Reimplementing this bundle's thin wrapper is typically half a day to a day of work.
- How do I handle uploads, downloads, and file management in Laravel without this bundle?
- Configure an s3 disk in config/filesystems.php, install league/flysystem-aws-s3-v3, and use Laravel's Storage facade for put, get, delete, and temporaryUrl operations. Add endpoint and path-style options for MinIO or localstack, and keep credential handling in the AWS SDK provider chain. Run your storage test suite against the new disk before touching production buckets.