Overview
InferenceOps JEV-27B Decision Engine runs the JEV-27B decision model (Apache-2.0 base, decision LoRA head) behind an OpenAI-compatible HTTP API on a single NVIDIA L40S instance in your own AWS account. The AMI already contains the 54 GB model weights and the vLLM engine image, so the instance is ready a few minutes after launch without downloading anything from the internet.
Endpoints: /v1/models, /v1/chat/completions (streaming, thinking on/off), /v1/completions and /v1/decide, which returns a calibrated binary decision with probability instead of free text. Any OpenAI SDK, LangChain or plain curl works.
Deploy either as a plain AMI (EC2 launch wizard; the API key is generated on first boot and read with SSM Session Manager) or with the included CloudFormation template, which creates the instance, a least-privilege role, a security group limited to your client CIDR, a CloudWatch log group and stores the API key in AWS Secrets Manager. The stack reports CREATE_COMPLETE only after the instance has verified its own API. Data never leaves your account.
Highlights
- Model weights and engine image baked into the AMI: no first-boot download, ready in minutes on g6e.2xlarge (1x L40S).
- OpenAI-compatible API plus /v1/decide for calibrated yes/no decisions; works with the OpenAI SDK, LangChain and curl.
- CloudFormation delivery stores the API key in Secrets Manager, restricts the security group to your CIDR and signals the stack only after a self-test.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
g6e.2xlarge Recommended | $0.02 |
g6e.4xlarge | $0.02 |
g6e.12xlarge | $0.02 |
Vendor refund policy
Not support
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release of the single-instance JEV-27B product. Ubuntu 24.04, NVIDIA driver 580, Docker + vLLM 0.29 (Ray 2.60 nightly image), model jev-27b baked in. Delivery options: AMI and CloudFormation (single instance, Secrets Manager key).
Additional details
Usage instructions
WHAT YOU GET: one Ubuntu 24.04 GPU instance with the JEV-27B weights (54 GB) and the vLLM engine already on the root volume. Nothing is downloaded at first boot. API: OpenAI-compatible routes plus POST /v1/decide on port 8080, protected by a bearer key.
LAUNCH (EC2 console or CLI)
- Instance type: g6e.2xlarge (recommended, 1x L40S 48 GB). g6e.4xlarge/8xlarge = same GPU, more CPU/RAM. g6e.12xlarge = 4 GPUs (tensor parallel 4).
- Key pair: not required. Port 22 is closed; use AWS Systems Manager Session Manager.
- Network: a subnet with a route to AWS APIs (public subnet, or private subnet with NAT / VPC endpoints for ssm, ssmmessages, ec2messages). Required only for Session Manager and OS updates.
- Security group: allow TCP 8080 (API) and 8081 (readiness) ONLY from your client IP range. Replace the suggested 0.0.0.0/0 rule. Do not open 22 or 8000.
- Storage: root volume >= 300 GiB gp3 (the AMI default is 300 GiB at 1000 MB/s; keep it).
- IAM instance profile: a role with the AmazonSSMManagedInstanceCore policy (needed to read the key).
- User data (optional, JSON): {"api_key":"YOUR-KEY-32-TO-128-CHARS","max_model_len":32768}. Leave empty to have a key generated on first boot. User data is read on the first boot only.
FIRST BOOT (about 10-15 minutes) The service verifies the weights, starts the engine and self-tests the API. Readiness: curl -s -o /dev/null -w '%{http_code}\n' http://INSTANCE_IP:8081/readyz -> 200 when ready. Progress/logs: aws ssm start-session --target INSTANCE_ID ; then sudo journalctl -u inferenceops-standalone -f
GET THE API KEY (root-only file, never printed in logs) aws ssm start-session --target INSTANCE_ID sudo cat /etc/inferenceops/api-key -> {"api_key": "..."}
CALL THE API API=http://INSTANCE_IP:8080/v1 ; KEY=... curl -s $API/models -H "Authorization: Bearer $KEY" curl -s $API/chat/completions -H "Authorization: Bearer $KEY" -H 'content-type: application/json' -d '{"model":"jev-27b","messages":[{"role":"user","content":"hello"}],"max_tokens":64,"chat_template_kwargs":{"enable_thinking":false}}' curl -s $API/decide -H "Authorization: Bearer $KEY" -H 'content-type: application/json' -d '{"model":"jev-27b","kind":"choice","state":"Customer charged twice, wants a refund.","question":"Which team handles it?","options":["Billing","Technical","Account","General"]}' Any OpenAI SDK works with base_url=$API and api_key=$KEY. Wrong key -> 401. The full contract is in /opt/inferenceops/gateway/openapi.yaml on the instance.
SECURITY: the API is plain HTTP. For internet clients put an Application Load Balancer with an ACM certificate in front (target 8080, health check 8081 /readyz). Engine port 8000 is bound to localhost only. IMDSv2 is enforced. STOP CHARGES: stop or terminate the instance. Model and key are on the root volume; a stopped instance resumes with the same key.
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.