Connect your AWS account
CoSell calls the AWS Partner Central API as an IAM role that you create in your AWS account: the one linked to your Partner Central organisation. You can see and remove that role at any time.
Deploy the access role
- Sign in to the AWS console of the account linked to your Partner Central organisation, as someone who may create IAM roles.
- In CoSell, go to Settings → AWS accounts and choose Launch stack in AWS (step 1). CloudFormation opens in a new tab, in us-east-1 (N. Virginia), with the template made for your workspace already filled in. It carries your workspace's external ID, so there is nothing to copy into it.
- Tick I acknowledge that AWS CloudFormation might create IAM resources with custom names and choose Create
stack. The stack, named
CoSell-<workspace>, is complete in about a minute. - Open the stack's Outputs tab and copy the value of RoleArn.
- Back in CoSell, under Step 2 · Paste the role ARN, paste it, choose the catalog and choose Link and verify.
CoSell reads the AWS account from the role ARN.
- AWS: real opportunities.
- Sandbox: test opportunities that AWS never reviews.
The link from Launch stack in AWS works for an hour; the page keeps it fresh while it is open. CloudFormation reads the template through that link, from a private file only your workspace's admins can have a link to.
To deploy the template some other way (StackSets, infrastructure as code), open Create the stack from the template yourself under step 1: Download template gives the same template as a file.
CoSell verifies the link straight away by listing your Partner Central solutions. The link shows verified, or the exact error AWS returned. CoSell always assumes the role with your workspace's own external ID, which the console never shows to members and never takes from a form. A role made for another workspace therefore cannot be linked: AWS refuses it, and CoSell refuses a role whose name says it belongs to another workspace. The account ID must be the account in the role ARN. Partner Central events from the account reach CoSell only once the link is verified.
What the role allows
The template creates two things:
- The access role
CoSellPlatformAccess-us-east-1-<workspace>, named after your workspace. Workspaces created before November 2026, and any workspace linked to a role with the old name, keepCoSellPlatformAccess-us-east-1, so updating an existing stack never replaces its role. Only HabileLabs' platform role can assume it, and only with your external ID. It allows the Partner Central Selling actions CoSell needs: create, update, submit and read opportunities; list solutions; answer engagement invitations; and the engagement tasks those actions run. It also has read-onlyGet*/List*access to Partner Central and read access to your AWS Marketplace agreements and entities, used by Ask Partner Central. Since October 2026 it may also create and update benefit (funding) applications. The Partner Central agent uses that only for a change a person approved in CoSell, and only in workspaces that allow agent changes. - Multi-partner opportunities (October 2026): the role may set your organisation's snapshot job role, and pass only
the one this template creates (
CoSellResourceSnapshotJob-us-east-1, with AWS's managed policy for snapshot jobs). See Partners on an opportunity. - Private offers (October 2026): the role may draft a private offer (the Catalog API's
CreateOffer,UpdateInformationandUpdateTargetingchanges only), never release one. It may also read change sets and agreements. See Private offers. - An EventBridge rule that forwards Partner Central events (opportunity changes, new invitations) from your account's default event bus to CoSell, so updates arrive in seconds instead of on the 15-minute reconciliation.
The role gets no other AWS permissions. See Security and data.
Keep the role up to date
When CoSell adds a capability that needs a new permission, update the existing stack with the current template: same
stack, same external ID. A link that needs it shows Update stack under Settings → AWS accounts, which opens the
stack's update in CloudFormation with the current template filled in; review the change and choose Submit. If your
stack has another name than CoSell-<workspace> (stacks created before November 2026 were named by hand), download the
template and update the stack with it, choosing Replace existing template. If a page says AWS refused … the IAM role created by your onboarding
template does not allow it, that is the fix.
CoSell checks for this itself each time a link is verified (when you link an account, when you choose Verify, and when HabileLabs re-verifies accounts), and once a week for every linked account. It asks AWS, about an engagement that cannot exist, whether the role may take each newer action; nothing changes in your account, though your CloudTrail shows the refused call. When the role is missing one, the link reads Update the stack under Settings → AWS accounts and your admins get a notification saying what it cannot do. Today that is converting AWS leads into opportunities (added on 29 October 2026): stacks created or updated before then can accept a lead but not convert it. After you update the stack, choose Verify and the notice goes.
If a link shows This link does not use this workspace's external ID, it was registered with an ID that is not your workspace's. Update the stack with the template from Settings → AWS accounts, remove the link, and link the role again.
CoSell in your own AWS account
When CoSell is installed in your own AWS account, install it in the account linked to your Partner Central, in us-east-1: that is where the Partner Central API and its events are. There is nothing to deploy and no external ID. The stack's own role holds the same permissions as the access role above, and only the CoSell stack can use it. Partner Central events arrive from the account's default event bus.
When the stack is created, and again on every upgrade, CoSell checks Partner Central by listing your solutions. Settings → AWS accounts (and step 2 of onboarding) shows the result under Partner Central in this AWS account. If AWS refuses, nothing syncs. The card shows AWS's answer and what to do:
- In AWS Partner Central, an alliance lead links the AWS account CoSell runs in to your Partner Central account (Settings → Account linking).
- If your Partner Central is linked to another AWS account, install CoSell there instead. To keep this install, link that account with the onboarding template, as above.
- Check that no service control policy or permissions boundary denies
partnercentral:*to the CoSell stack's roles. - Choose Check again.
The production install slot works with the live (AWS) catalog. A nonprod install works with the Sandbox catalog only: it hears only Sandbox events, refuses links to the live catalog, and AWS refuses the live catalog to its role.
Several AWS accounts
Organisations with more than one Partner Central account (SPMS) can link each of them. One link is the default. To send different deals to different accounts, give each its own rule under Settings → Rules. An AWS account cannot be removed while a rule or a live opportunity still uses it.