Laravel Monolog Kinesis Laravel Package

Product Decisions This Supports

• Build vs. buy for log shipping. This package is a thin, focused Monolog handler that writes Laravel logs to an AWS Kinesis stream. It replaces a small-but-nontrivial piece of custom glue (Monolog handler + AWS SDK credentials/stream wiring + config publishing). Low code surface, MIT-licensed, so the buy decision is cheap to reverse — the real commitment is to Kinesis itself, not to this package.
• Logging architecture / platform choice. Adopting it implies a decision that Kinesis is the ingestion backbone for application logs (typically fanning out to Firehose → S3, Lambda consumers, OpenSearch, or a SIEM). That is a data-platform and cost decision as much as an app decision: shard-hour and PUT-payload pricing means it fits high-volume, multi-consumer, replay-needed workloads far better than small apps.
• Standardized log schema (new in 4.0.2 — custom formatter). The ability to supply a custom Monolog formatter turns log shape into a product decision rather than a fork: JSON/ECS-style fields, correlation IDs, service/tenant tags, and payload trimming to control Kinesis cost. This is the release's most strategically useful change because it lets platform teams enforce a downstream contract (analytics, SIEM, dashboards) without maintaining a private fork.
• Secrets management and cloud posture (new in 4.0.2 — null AWS credentials). Supporting null credentials for assumed IAM roles means the app can run on EKS with IRSA, ECS task roles, or EC2 instance profiles without static access keys. That is a security/compliance win and removes a blocker for teams whose platform policy forbids long-lived keys in environment variables.
• Roadmap inputs. If your logging roadmap is CloudWatch-first with minimal consumers, this adds a hop and cost without much payoff. If the roadmap includes log-derived analytics, retention beyond convenience windows, replay, or multiple independent consumers, Kinesis plus this handler is a credible default.
• Release-process hygiene to note. The project dropped CHANGELOG.md in favor of the GitHub Releases page. If your dependency-review or change-tracking workflow reads changelog files (bots, compliance scans, upgrade runbooks), update it to read Releases instead.

When to Consider This Package

Consider adoption when:

• The service is Laravel/PHP and you want logs in Kinesis with configuration rather than custom handler code. Confirm the package's supported Laravel/PHP matrix against your current runtime before committing — the release notes do not state version support.
• AWS is already the platform and Kinesis streams exist or are planned; your team already owns IAM policy for stream writes.
• You need buffering, retention, replay, or fan-out to multiple consumers — the cases where CloudWatch Logs alone becomes awkward.
• You want a custom log format for a downstream schema or cost control. As of 4.0.2 this is a supported extension point, so don't fork to get it.
• You run on AWS compute with IAM roles (EKS/IRSA, ECS, EC2) — 4.0.2's null-credential support is specifically aimed at you.
• The service is high enough volume that per-GB aggregation pricing is acceptable, and you have someone who will watch shard capacity and cost.

Look elsewhere when:

• You are not on AWS, or the org standardizes on GCP/Azure logging.
• Volume is low to moderate and CloudWatch Logs, a SaaS aggregator, or stdout-based collection already satisfies the need — Kinesis shard-hour costs and operational overhead rarely pay off at small scale.
• You need commercial support, an SLA, or a large maintainer base. This is a small community package; treat it as a dependency you may need to patch yourself.
• Delivery guarantees matter per-request (audit/compliance trails where a dropped or delayed batch is unacceptable). Verify the handler's batching, retry, and failure behavior against your requirements before relying on it for anything non-observational.
• You have no log redaction story. Streams retain data and are painful to purge; scrub PII upstream of the handler, since a formatter changes shape but is not a compliance control.
• Strict dependency-minimalism applies: this is one more AWS-coupled package in the critical path of application boot.

How to Pitch It (Stakeholders)

For executives (one paragraph): A small open-source dependency that sends our Laravel application logs into AWS's managed streaming pipeline without us writing or maintaining custom integration code. The v4.0.2 release is additive and non-breaking, and delivers two things that matter commercially: we can now enforce a standard log format across services instead of forking, and we can run without static AWS access keys by using IAM roles — which removes a secrets-management finding and unblocks deployment on our standard AWS compute. Cost is driven by Kinesis volume, not by this package; it is appropriate for services with real log volume and multiple downstream consumers, and overkill for small ones.

For engineering: Patch release within 4.x, no breaking changes, low upgrade risk. Three changes: (1) custom formatter support — allows a shared log schema and payload trimming instead of maintaining a fork; (2) null AWS credentials supported for assumed IAM roles — enables IRSA/ECS task roles/instance profiles with no code changes beyond config; (3) changelog moved to GitHub Releases, so update any automation that parses CHANGELOG.md. Recommended approach: pilot in one service, confirm supported Laravel/PHP versions, verify batching/retry semantics and formatter behavior under load, and instrument cost per GB plus delivery latency before rolling out fleet-wide. Have a named owner, since upstream support is community-only.