CoSell docs Open CoSell

Running CoSell in your AWS account

When CoSell is installed in your own AWS account, HabileLabs cannot see into it. This page is the guide to running it: what you need, installing, sizing, backups, upgrades, the Install page, the support bundle, alarm emails, the monthly AWS cost and how to remove CoSell. To link Partner Central, see Connect your AWS account.

Before you install

  • The AWS account linked to your Partner Central, in US East (N. Virginia), us-east-1. Partner Central's API and its events are there, so CoSell runs nowhere else.
  • Permission to create the stack. The IAM policy shown beside the template on AWS Marketplace is enough. The stack needs no CDK bootstrap, no VPC and no root user.
  • Amazon Bedrock: Amazon Nova 2 Lite available in us-east-1 (Bedrock console, Model access). The AI features use it.
  • Your licence key, which starts with COS-. The HabileLabs Marketplace portal shows it after you choose In my AWS account at sign-up.
  • Lambda concurrency, on CoSell 1.1.0 and earlier: those versions reserve 113 concurrent executions, and AWS keeps 100 unreserved, so the account's quota (Service Quotas → AWS Lambda → Concurrent executions) must be at least 213. A new AWS account may start lower: request an increase first. CoSell 1.2.0 and later reserve none.
  • Optional: your own hostname with an ACM certificate in us-east-1, and a sender address verified in Amazon SES for notification email. Without a sender, CoSell offers Slack. Sign-in invitations always work, through Amazon Cognito's own email.

Install and sign in

Launch the stack from the CoSell listing on AWS Marketplace (Quick Launch) or from the portal's launch link. Enter the licence key, the install slot, your company name and the first admin's email. The stack takes 15 to 20 minutes to create.

  • production is the install slot for your live Partner Central pipeline.
  • nonprod is a test install that works with the Partner Central Sandbox only. Give it another stack name, such as cosell-nonprod. Both can run in one account.

When the stack is created, the first admin is emailed an invitation with a temporary password. Open ConsoleUrl from the stack's outputs, sign in, and set up an authenticator app. Then connect your CRM, or use CoSell CRM.

Checking the template first

Each version's release notes in the portal give its template's SHA-256. To check that the template you launch is the one HabileLabs released, compare that value with what this prints for the version's template URL:

curl -s https://cosell-releases-us-east-1.s3.us-east-1.amazonaws.com/<version>/cosell-marketplace.yaml | shasum -a 256

The same folder's SHA256SUMS lists every file the template installs, function code included.

Sizing

There is nothing to size. CoSell is serverless: it has no instances, no clusters and no capacity settings, and the database is billed by request. The same stack serves a pipeline of 50 deals and one of several thousand. At most 10 sync jobs and 3 AI jobs run at once, which keeps CoSell inside Partner Central's rate limits. What grows with your pipeline is the cost of CoSell's work, shown under What AWS bills you each month.

Backups and restoring

  • The database has point-in-time recovery, switched on by the stack: AWS keeps 35 days of continuous backups, so the table can be restored to any second in that time. Deletion protection is on.
  • Sign-in accounts are in the Cognito user pool, which AWS does not back up. Deletion protection is on. If the pool is ever lost, an admin invites people again.
  • CRM and Slack credentials are in AWS Secrets Manager. They are not backed up: reconnect to replace them.
  • Deals themselves stay in your CRM and in Partner Central. CoSell rebuilds its sync state from both: it compares them every 15 minutes.

To restore, create a new table from the backup, in the DynamoDB console (Backups → Point-in-time recovery → Restore) or with the AWS CLI:

aws dynamodb restore-table-to-point-in-time --region us-east-1 \
  --source-table-name <TableName from the stack's outputs> \
  --target-table-name cosell-restored --restore-date-time 2026-11-13T06:00:00Z

The restored table is a copy beside the live one, and the stack keeps using the live one. Check the copy, then email support@habilelabs.io with the support bundle: HabileLabs guides you through putting records back. A restore of a small table takes about half an hour. Delete the copy when you are done, as AWS bills its storage.

Upgrades

The Install page and the portal show when a new version is out, with what changed. To upgrade:

  1. In the CloudFormation console, choose the CoSell stack, then Update, then Replace existing template.
  2. Paste the new version's template URL from the portal. You can check it first, as in "Checking the template first".
  3. Keep every parameter as it is, acknowledge the IAM notice and update.

Your data, settings, people and connections are kept, and CoSell makes any data changes itself during the update. Each release can be upgraded to from the two before it. An install older than that shows a red banner and emails its admins weekly; nothing is blocked.

The Install page

The workspace's admins open Install in the menu. It shows:

  • the CoSell version;
  • the licence's state and the last daily check-in with HabileLabs;
  • the support bundle;
  • the incentive figures the install reports.

The support bundle

When you raise a support request, choose Download support bundle on the Install page and attach the file. It is a JSON file you can open and read before you send it. It holds:

  • Versions: CoSell's, and the newest and oldest the licence reports.
  • Settings, without secrets: sync and retention settings, how many people are in each role, and the state of each connection: Zoho, Slack and every AWS account.
  • The last 7 days of sync errors, by kind: the error code, how often it happened, for how many deals, and which ACE fields AWS named.
  • Queue and dead-letter queue depths, and the state of each alarm.
  • Daily figures from the last 7 days, and the licence's state and usage.

It holds no deal content, contacts, email addresses, error messages or credentials. CoSell builds the bundle from a list of fields it is allowed to include. Then it replaces any text that is not shaped like a code with [redacted]. Each download is recorded in the audit log.

Alarm emails

The stack's alarms email the address given as AdminEmail when the stack was created. They cover dead-lettered messages, function errors, slow or failing syncs, and Partner Central throttling. AWS first emails that address to confirm the subscription: choose Confirm subscription in that email, or no alarm reaches you. To send alarms somewhere else, update the stack with another AdminEmail. The new address gets its own confirmation email.

What AWS bills you each month

AWS bills your account for what the CoSell stack uses. These are list prices in US East (N. Virginia), before any free tier:

Deals tracked What the stack keeps running CoSell's work A month
50 $12.10 $0.26 about $12.40
250 $12.10 $0.57 about $12.70
1,000 $12.10 $1.73 about $13.80

Most of it is fixed:

  • the alarms and the dashboard;
  • the custom metrics;
  • the alarm topic's KMS key;
  • two secrets (the sign-in email key and the Zoho credentials);
  • Cognito's threat protection, for ten people signing in.

CoSell's work is measured from CoSell's own daily cost rollups. It covers the functions, the API, the queues, the database, AI and email. A busier pipeline changes the total little. An account that does not already use AWS's always-free allowances (alarms, dashboards, custom metrics and Lambda) pays less: as little as about $5.10 a month for the fixed part.

Logs, traces, storage and the console's hosting add a few cents a month at these volumes.

Removing CoSell

Delete the CloudFormation stack in your AWS account. Deleting the stack:

  • keeps your data. The DynamoDB table, the Cognito user pool and the stack's S3 buckets stay in your account. The table and the user pool also keep their deletion protection.
  • retires the install with HabileLabs, which frees its licence slot.

To remove the data as well, delete what the stack kept once the stack is gone. Turn off the deletion protection on the table and on the user pool first. Export the data before that if you need a copy. Until you delete them, AWS bills the table's storage and backups, and the buckets' files.

The workspace itself can't be deleted from Settings → Data & privacy in an install. It is the install's only workspace, made with its stack, so it goes when the stack goes. You can still export everything it holds from that page.