> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Deploy through AWS Marketplace
> Purchase the current Entelligence AWS Marketplace offer, launch the seller-provided CloudFormation deployment, and verify and operate the resulting AWS resources.
Entelligence's current deployment guide describes an AWS Marketplace offer delivered with container images and a seller-provided CloudFormation template. The exact product version, parameters, resource names, and delivery options can change; use the values shown by the current Marketplace listing and template.
## Current documented components
The Entelligence deployment guide currently describes:
* `entelligence-api`: backend container image
* `entelligence-app`: frontend container image
* A CloudFormation template for the ECS environment and RDS database
* Application Load Balancers for the frontend and backend
* AWS Secrets Manager for generated database credentials
Confirm the current architecture and responsibility split with Entelligence before purchase. Do not infer that a future template provisions the same resources or that every operational control is managed by Entelligence.
## 1. Purchase through AWS Marketplace
1. Sign in to the approved AWS account.
2. Open the [Entelligence AWS Marketplace listing](https://aws.amazon.com/marketplace/pp/prodview-wd6mzxdke72we).
3. Review the seller, legal terms, pricing dimensions, contract duration, user quantity, and refund or cancellation terms.
4. Complete the organization's procurement and AWS Marketplace approval process.
5. Select **View purchase options** or the equivalent current action.
6. Create the contract only after the terms and total commercial commitment are approved.
7. Continue to configuration and select the current product version and delivery option.
The listing URL currently responds, but Marketplace purchase and launch screens can vary by account, region, agreement state, and offer type.
## 2. Obtain and review the deployment template
Use the CloudFormation template supplied by the current Entelligence Marketplace fulfillment flow or account team.
Before launching:
* Review the template in source form.
* Inventory IAM roles and policies it creates.
* Confirm supported AWS regions and availability-zone requirements.
* Review VPC, subnet, security-group, load-balancer, ECS, RDS, and Secrets Manager parameters.
* Confirm database engine, sizing, encryption, backup, and deletion policy.
* Confirm container image sources and update ownership.
* Estimate AWS infrastructure cost separately from Marketplace charges.
Do not upload a template copied from another environment without confirming its version and integrity.
## 3. Create the CloudFormation stack
1. Open **AWS CloudFormation** in the approved region.
2. Select **Create stack → With new resources (standard)**.
3. Use the seller-provided template.
4. Enter a descriptive stack name.
5. Complete every required parameter using the deployment plan.
6. Review tags, stack permissions, failure behavior, and termination protection.
7. Acknowledge IAM resource creation only after reviewing the template.
8. Submit the stack.
9. Monitor **Events** until the stack reaches a successful completion state.
## 4. Verify the deployment
Use the actual CloudFormation **Outputs**, load balancer listeners, and DNS configuration rather than guessed hostnames.
### Backend
1. Locate the backend endpoint from the stack outputs.
2. Use the configured `http` or `https` scheme.
3. Request the documented health path: `/healthCheck/`.
4. Confirm the expected healthy response and target-group status.
5. Verify the endpoint is reachable only from approved networks.
### Frontend
1. Locate the frontend endpoint from the stack outputs.
2. Open it from an approved client.
3. Confirm it calls the intended backend endpoint.
4. Verify authentication, session handling, and logout.
5. Confirm no default administrative credential remains.
### AWS resources
Verify:
* ECS services are stable and tasks use the intended image version.
* Load-balancer target groups are healthy.
* RDS is encrypted, reachable only from approved security groups, and protected by the intended backup policy.
* Database credentials are stored in Secrets Manager and not exposed in stack outputs or logs.
* CloudWatch logs and alarms receive expected data.
* CloudFormation drift is understood before manual resource changes.
## 5. TLS, DNS, and network controls
* Issue or import certificates through [AWS Certificate Manager](https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html).
* Configure [HTTPS listeners for the Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html).
* Create approved [Route 53 records](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) or the organization's DNS equivalent.
* Redirect HTTP to HTTPS where required.
* Restrict inbound security-group rules to approved sources.
* Keep ECS tasks and RDS in the intended private subnets unless the reviewed architecture requires otherwise.
* Document proxy, egress, webhook, and allowlist requirements.
## 6. Operate the deployment
### Monitoring and scaling
* Configure CloudWatch logs, metrics, dashboards, and alarms.
* Establish CPU, memory, latency, error-rate, and target-health baselines.
* Configure ECS service scaling only after load testing and capacity planning.
* Test alert routing.
### Backup and recovery
* Configure RDS automated backups and the approved retention period.
* Test snapshot restore and application recovery.
* Record recovery-time and recovery-point objectives.
* Confirm CloudFormation deletion and database-retention behavior.
### Updates
* Obtain supported image versions and release instructions from Entelligence.
* Review task-definition and schema changes.
* Test updates in a non-production environment.
* Use a controlled ECS deployment strategy.
* Keep a documented rollback path.
### Cost management
* Track Marketplace charges separately from ECS, RDS, load balancer, NAT, storage, logging, and data-transfer costs.
* Configure AWS Budgets and cost-allocation tags.
* Review idle and overprovisioned resources.
## Troubleshooting
| Symptom | Check |
| ----------------------------- | ----------------------------------------------------------------------------------------------- |
| Stack creation fails | CloudFormation Events, IAM permissions, quotas, parameters, region, and resource availability |
| ECS tasks restart | Container logs, task definition, secrets, health checks, CPU, memory, and database connectivity |
| Load balancer is unhealthy | Listener, target group, security groups, health path, port, and container status |
| Database connection fails | RDS status, secret value, security groups, subnet route, DNS, and TLS |
| Frontend cannot reach backend | Stack outputs, frontend configuration, DNS, listener, CORS, and security groups |
| Certificate or DNS fails | ACM validation, certificate region, listener certificate, record target, and propagation |
| Update fails | Image availability, task-definition change, database migration, deployment events, and rollback |
For product-specific failures, contact [support@entelligence.ai](mailto:support@entelligence.ai) with the Marketplace offer, region, stack ID, template version, redacted error, and timestamp. Do not send secrets.