Laravel Hunt Laravel Package

Product Decisions This Supports

• Managed search infrastructure vs. self-hosted: Release 0.5.5 adds the option to sign all Amazon Elasticsearch requests. This removes the single biggest friction point for teams running Elasticsearch/OpenSearch on AWS, since IAM-based authentication normally requires custom AWS Signature Version 4 signing logic. It enables a "buy managed" decision without bespoke security code.
• Build vs. buy for search plumbing: Instead of building and maintaining SigV4 request signing in-house, the package now covers the AWS path. This is a build-vs-buy lever: use the package for integration and signing, spend engineering effort on search relevance and product features instead.
• Security / compliance roadmap: Signing requests means credentials flow through IAM roles and the standard AWS credential chain rather than static keys embedded in Elasticsearch config. That aligns with existing AWS security posture and audit expectations.
• Feature and use-case enablement: Catalog/product search, faceted filtering, autocomplete, and log/analytics search in a Laravel app. The signing option makes these viable on AWS-managed clusters, not just self-managed nodes.
• Roadmap risk flag: The package is at 0.5.x (pre-1.0). Pin versions and plan upgrade validation; treat minor releases as potential breaking-change candidates until 1.0.

When to Consider This Package

Adopt when:

• You are building on Laravel/PHP and want a native Elasticsearch integration rather than hand-rolling a client layer.
• Your search cluster will run on AWS Elasticsearch/OpenSearch with IAM authentication — 0.5.5 is directly aimed at this and eliminates custom signing work.
• Your team is small and prefers to keep search integration inside the PHP codebase rather than adding a separate service or language runtime.
• You need full-text search, faceting, or analytics-style queries and are comfortable operating at a 0.x maturity level with version pinning.

Look elsewhere when:

• You are not on AWS or use static auth/TLS — the signing feature adds no value, and you should evaluate the underlying Elasticsearch client directly.
• Laravel Scout with a supported driver already meets your needs; adding another integration layer increases surface area.
• You require a stable 1.0 API contract or long-term support guarantees — pre-1.0 releases may introduce breaking changes.
• You need deep, non-trivial query construction or OpenSearch-specific features that the package may not expose; a direct client may be less constraining.
• The project is not Laravel/PHP — the value is the framework integration, which does not transfer.

How to Pitch It (Stakeholders)

Executive summary: The package integrates Elasticsearch into Laravel and, as of 0.5.5, can sign requests for Amazon Elasticsearch using AWS IAM credentials. This unlocks managed AWS search without writing or maintaining custom cryptographic signing code, keeps credentials in the standard AWS security model, and lets the team focus on search features rather than infrastructure plumbing.

For engineering: Version 0.5.5 adds an opt-in setting to sign all Amazon Elasticsearch requests, so clusters secured by IAM policies work through the existing AWS credential chain instead of ad-hoc keys. It reduces bespoke SigV4 maintenance and keeps auth consistent with the rest of the AWS stack. Note the pre-1.0 version line: pin the dependency, review upgrades, and validate signing behavior in staging before rollout.

Decision ask: Approve adoption for the search feature on AWS-managed Elasticsearch, with the caveat that we pin to a known version and budget a small validation step for future upgrades.