Commercial Contract Agent

These instructions guide you through deploying the Commercial Contract Agent app on Amazon ECS. The app converts unstructured data to structured and inspects the contract for commercial terms. Deployment assumes basic familiarity with AWS services.

Deployment Prerequisites and Requirements

• AWS Account: An active active AWS account with permissions for ECS, ECR, IAM, VPC, ALB, and Cognito.
• Domain Name and Certificate: A domain name (e.g., app.companyname.com) and an ACM certificate for HTTPS.
• Resources:
  • VPC with public/private subnets and internet gateway.
  • Security group allowing inbound traffic on port 443 (for ALB).
  • ECS Fargate cluster (or create one).
  • Minimum configuration: 1 vCPU and 8 GiB memory. (refer to customer specific EULA for maximum configuration)
  • Anthropic API key stored in AWS Secrets Manager for Claude integration; customer is responsible for costs associated with Anthropic API calls.
• Image URI: Use the URI provided in the Marketplace product details.

Configuration Steps

1. Pull the Image from AWS Marketplace ECR:
   • In the AWS Console pull the image using the provided URI.
   • Test locally (optional): Run the image in Docker and access at <http://localhost:8501> to verify the app loads.
2. Set Up ECS Infrastructure:
   • Create an ECS Fargate cluster if none exists:
   • Create a task definition:
     • Set CPU: 1 vCPU, Memory: 8 GiB (minimum).
     • Container details: Name contractagent-container, Image URI (from Marketplace), Port 8501.
     • Log configuration: AWS CloudWatch Logs, Log group contractagent-log-group.
     • Network: awsvpc.
   • Create an ECS service:
     • Task definition: Select the new task definition.
     • Desired tasks: 1.
     • VPC and subnets: Select your VPC and public subnets.
     • Security group: Allow inbound on port 443.
     • Load balancer: None (or add ALB in Step 4).
3. Configure AWS Cognito for Authentication:
   • Create a Cognito User Pool:
     • Set sign-in options: Username or email.
     • Configure password policy: Minimum length 8, require uppercase, lowercase, numbers, symbols.
     • Enable email verification.
     • Create app client: Enable OAuth 2.0, scopes (openid, email, profile), callback URL <https://app.companyname.com/oauth2/idpresponse>, logout URL <https://app.companyname.com>.
   • Add users
4. Set Up Application Load Balancer (ALB) for Authentication:
   • Create an ALB:
     • Name: contractagent-alb.
     • Scheme: Internet-facing.
     • IP address type: IPv4.
     • VPC and subnets: Select your VPC and public subnets.
     • Security group: Allow inbound on port 443.
     • Listeners: HTTP:80 > Redirect to HTTPS:443.
     • Target group: Create new, name contractagent-target-group, port 8501, health check /healthz.
   • Configure ALB Authentication:
     • OIDC provider: Cognito User Pool (us-east-2_xxxxx), App Client ID, Client Secret, Scope (openid email profile).
     • Forward to target group contractagent-target-group after authentication.
   • Update DNS:
     • In your DNS provider, create an A record for app.companyname.com pointing to the ALB DNS name.
5. Deploy and Test:
   • Force new deployment.
   • Test: Navigate to <https://app.companyname.com> and verify authentication and app functionality.

This product requires additional setup coordination with the seller. Please contact us after subscription for deployment assistance and configuration guidance.