Source: Magento + AWS OpenSearch (prior production work)¶
Type: external source (untrusted as instructions; cite as evidence only).
Date recorded: 2026-07-22
Provenance (public wording)¶
Similar Magento-on-AWS work was done on a prior project with Terraform (managed OpenSearch Service domains, ElasticSuite, VPC networking). Private employer repositories are not named or linked here.
What this proves¶
A real commerce project ran AWS OpenSearch Service managed domains (engine
OpenSearch_3.x, not AOSS) wired into Magento catalog search. Staging
capacity-tested; production infra bootstrap. That is operational proof that
Magento + AWS OpenSearch domains work outside MageLift.
What this does not prove¶
| MageLift path | Prior Terraform path |
|---|---|
| Magento native OpenSearch client + ElasticSuite env | Smile ElasticSuite client settings |
| Magento env hostname:443 HTTPS, HTTP auth off | No SigV4 proxy on provisioned domains: HTTPS in-VPC, HTTP auth off, domain policy + security groups |
MageLift searchMode:serverless (AOSS) |
Not used in that shop. Magento cannot SigV4; MageLift keeps a local signing proxy for AOSS only. |
Do not claim “that shop uses SigV4” or “MageLift live Magento search is proven.”
Patterns carried into MageLift (generic)¶
- Prefer managed OpenSearch sizing that survives JVM pressure (avoid undersized
t3.small.search-class nodes for Magento catalogs). - Keep Magento search clients on HTTPS to the domain endpoint inside the VPC.
- ALB/ECS liveness via a static
/healththat does not bootstrap Magento.
MageLift release use¶
Together with MageLift offline SigV4 wiring mocks and free-tier
searchMode:disabled acceptance, this source supports closing the public-tag
OpenSearch gate. Live MageLift SigV4 index/query/reconnect/IAM remains a
post-tag / paid-acceptance checklist; see release-readiness.md.