Connecting AWS Partner Central lets you share opportunities with AWS from the Wyra CRM. You link the AWS account your Partner Central uses, deploy a small CloudFormation stack that Wyra prepares for you, test the connection, map your stages, and choose which AWS opportunities Wyra brings in. The connection itself takes about ten minutes once the right person is at the keyboard.
Before you start
- The AWS account linked to your Partner Central. You need its 12-digit account ID. In the AWS Console, open the account menu at the top right and choose Account.
- Someone who can create IAM roles in that account. The stack creates IAM roles, so the person deploying it needs permission to create CloudFormation stacks and IAM roles. This is usually your AWS administrator.
- An Org Admin or Settings Manager in Wyra to start the setup and run the test.
- A pipeline for your AWS opportunities. Create it under Settings → CRM → Pipelines first. Each workspace attaches one pipeline to AWS Partner Central, and it shows the label Attached to AWS Partner Central. Your other pipelines stay in Wyra only.
One AWS account can be connected to one Wyra workspace. Wyra prepares everything and gives you a template that's already filled in for your workspace.
Connect in five steps
Go to Settings → Integrations → AWS Partner Central. The setup has five steps: AWS account, Deploy & test, Connected, Map stages and Review & import. Your progress is saved, so you can leave and come back later, for example while your AWS administrator deploys the stack.
1. Link your AWS account
Enter the 12-digit AWS account ID and click Generate connection details. Wyra creates a secret for your workspace, called an ExternalId, and builds your personal CloudFormation template. Only Wyra, presenting that secret, can use the access the stack grants.
2. Deploy the CloudFormation stack
Sign in to the AWS account you entered, then:
- In Wyra, download the template (wyra-ace-setup.yaml). You can also open the full template to read it first.
- In the AWS Console, switch to the US East (N. Virginia) region. Partner Central sends its change notices only from there. A stack in another region still connects, but changes made at AWS then reach Wyra only once a day.
- Go to CloudFormation → Create stack → With new resources (standard) → Upload a template file, and choose the file.
- Leave every parameter as it is. They're already filled in for your workspace.
- Tick the acknowledgement that the stack creates IAM resources, and create the stack.
- Wait until the stack shows CREATE_COMPLETE. This usually takes about two minutes.
The stack's Outputs tab shows a role ARN. Wyra already knows the role from your account ID, so you can leave it.
3. Test the connection
Back in Wyra, click Test connection. Wyra signs in to your account using the role and checks that it can reach Partner Central. When it works, you see Connection verified, the setup moves to Connected, and your Org Admins get an email saying AWS Partner Central is connected.
The Connected screen shows the AWS account and when Wyra last connected.
4. Map your stages
Pick the AWS stage that matches each stage of your attached pipeline. The mapping decides where AWS opportunities land when you import them, which AWS stage Wyra suggests when you move an opportunity, and which Wyra stage it suggests when AWS moves one. The mapping itself moves nothing. See Mapping stages to AWS.
5. Review and import
Wyra lists every opportunity in your Partner Central account and suggests what to do with each one. You decide, and nothing is imported until you confirm. See Choosing what to import below.
Choosing what to import
Each opportunity in the review gets one of three results:
| Result | What it means |
|---|---|
| Import and track (tick) | Imported into your attached pipeline at its mapped stage, and kept in step with AWS from then on. |
| Ignore (empty) | Left out of Wyra, and left out for good, even when AWS changes it later. |
| Needs a decision (dash) | Wyra can't place it on its own, so it waits for a person. |
How Wyra pre-selects
Wyra applies these checks in order, and the first that fits decides. Any choice you make wins over Wyra's pick.
- It matches an opportunity already in Wyra: needs a decision. Attach it to the Wyra opportunity, or create a new one.
- AWS rejected it: ignore.
- The customer is your own company, or blank: needs a decision.
- It's a test record: ignore.
- It's a draft in AWS (Pending Submission or Action Required): needs a decision.
- It's won (Launched): imported as history, if Wins to bring in includes it.
- It's lost (Closed Lost): imported as history, if Losses to bring in includes it.
- Its AWS stage has no Wyra stage: needs a decision, so you pick the stage.
- It's open and well past its target close date: ignore, as stale.
- It's open and a little past its target close date: needs a decision.
- It's open and its target close date is ahead: import.
Three settings shape the picks. Wins to bring in (All, This year or None) is All by default. Losses to bring in (All, This year or None) is This year by default. Stale after sets how many days past target close count as stale, 90 by default. Changing a setting updates every row you haven't touched yourself.
Working through the list
- Summary tiles show Import and track, Needs a decision, Ignore and All. They always add up to the total.
- Filters narrow the list by company or opportunity ID, target close date, AWS stage or result.
- Tick all, Untick all and Reset to Wyra's picks act on the rows in view.
- Attach to a Wyra opportunity links a row to an opportunity already in Wyra that isn't linked to AWS. The row then shows Attached with the opportunity's name, and Undo.
- A row whose AWS stage has no Wyra stage asks you to choose one before you tick it. A row that matches an existing opportunity asks you to pick Attach or Create new.
Confirming
The summary shows how many opportunities will be imported and tracked, ignored, and still need a decision. When you confirm:
- Ticked rows are imported into your attached pipeline.
- Attached rows link to their Wyra opportunity, which keeps its stage.
- Rows that still need a decision move to New from AWS.
- Your Org Admins and AI SDRs are notified.
New from AWS
New from AWS is where every AWS opportunity Wyra hasn't seen before waits for a person. Find it under Settings → Integrations → AWS Partner Central, beside the import review, with a count of what's waiting. When something is waiting, a banner on the opportunities board links to it.
- Opportunities your team creates directly in Partner Central arrive here.
- So do rows from the first import that still needed a decision.
- Opportunities you chose to ignore at the first import stay ignored.
A person decides on every one, because only your team knows whether a new AWS opportunity is new or one you already have in Wyra under another name. Your Org Admins and AI SDRs get a notification and an email for each arrival. Each one shows why it's waiting, such as New in Partner Central: attach or create, Possible duplicate of a company in Wyra, No Wyra stage for its AWS stage, a draft still in AWS, or rejected by AWS.
| Action | What happens |
|---|---|
| Attach to a Wyra opportunity | Links it to an opportunity already in Wyra that has no AWS link, with the same company listed first. The Wyra opportunity keeps its stage, and nothing is sent to AWS. It's tagged Attached to AWS. |
| Create new | Adds it to your attached pipeline at its mapped stage, or at the stage you pick. It's tagged New from AWS. |
| Ignore | Leaves it out of Wyra for good. |
Opportunities AWS rejected
A rejected opportunity is closed at AWS, and AWS keeps it read-only. It still appears in New from AWS with AWS's reason and comments, so you can act on them:
- Start a new opportunity from this copies the customer, project and spend into a new Wyra opportunity, tagged Copy of a rejected opportunity. Fix what AWS flagged, then share it with AWS as a new opportunity. Wyra links the copy to the one it replaces.
- Attach keeps its history with an opportunity already in Wyra.
- Ignore leaves it out.
Opportunities AWS sends back (Action Required)
When AWS asks for changes, the opportunity's AWS tab opens just the fields AWS lets you edit, with AWS's comments beside them: the address, website, target close date, expected spend, the customer's business problem and your partner opportunity identifier. Send the update and AWS reviews it again, until it approves or rejects it.
What the connection gives Wyra
This section is for whoever reviews the access in your AWS account. Everything is created by the stack, in your account, and you can read the full template before deploying it.
| Created in your account | What it does |
|---|---|
| IAM role PartnerCentralRoleForWyra | The role Wyra uses. Only Wyra's AWS account can use it, and only when it presents your workspace's ExternalId. It carries AWS's managed policy for co-sell opportunity management. |
| Read-only additions on that role | Read access to your Partner Central funding and revenue-attribution data, and to your AWS Marketplace listings so you can pick products when you share an opportunity. |
| EventBridge rule and forwarding role | Forward Partner Central opportunity events to Wyra, so changes made at AWS reach Wyra within seconds. |
- No stored keys. Wyra keeps no AWS access keys. It signs in to the role for short sessions of up to an hour.
- Opportunities only. With the managed policy, Wyra can list, read, create, update and submit co-sell opportunities and read your solutions. It uses AWS's narrower opportunity-management policy.
- Read-only everywhere else. Wyra can't apply for funding, change revenue records, or change your Marketplace listings.
- Revoke at any time by deleting the stack in CloudFormation. The access ends at once.
If something goes wrong
When a test fails, Wyra shows the error exactly as AWS returned it, under the Test connection button.
| What you see | What to do |
|---|---|
| Not authorized to perform sts:AssumeRole | Wyra couldn't sign in to the role. Check that the stack shows CREATE_COMPLETE, in the same account ID you entered in Wyra. Download the template again from this workspace's setup, update the stack with it, keeping the parameters as they are, and test again. |
| Not authorized to perform partnercentral:ListOpportunities | The role exists but its permissions were changed. Update the stack with a fresh template from Wyra. |
| A message asking you to register as an AWS Partner | The account you entered differs from the one linked to your Partner Central. Check the account in Partner Central, then use Change AWS account to enter the right one. |
| The stack fails to create | Usually the IAM acknowledgement was left unticked, the person deploying lacks IAM permissions, or a stack from an earlier setup already exists. Update the existing stack. |
If Wyra loses its connection to AWS, for example because the stack was deleted, the opportunities board shows a banner saying AWS Partner Central is disconnected, and your Org Admins are alerted. Stage changes stay in Wyra in the meantime. Redeploy the stack from a fresh template and test again.
Disconnecting and reconnecting
On the Connected screen, click Disconnect AWS account and type the account ID to confirm. Wyra stops syncing with Partner Central and forgets the role and its secret. Opportunities and companies already in Wyra stay. Opportunities you shared stay in Partner Central, because AWS keeps what it's been sent.
- Disconnecting changes Wyra only. To remove Wyra's access completely, also delete the stack in CloudFormation.
- To reconnect, run the setup again. Wyra creates a new secret, so update your existing stack with the new template, or delete it and create a new one, then test.
- To use a different AWS account, click Change AWS account and deploy the stack in the new account.