--- title: "AWS Multi-Partner Opportunities: Invite a Partner" url: https://www.fours.com/resources/blog/aws-multi-partner-opportunities/ canonical: https://www.fours.com/resources/blog/aws-multi-partner-opportunities/ type: Blog description: "Bring a reseller or SI into an AWS ACE opportunity: connect first, invite up to nine partners, plan for the 15-day expiry, and track invitations in Fours." --- # AWS Multi-Partner Opportunities: Invite a Partner > Canonical HTML version: https://www.fours.com/resources/blog/aws-multi-partner-opportunities/ 1. [Home](/) 2. [Resources](/resources/) 3. [Blog](/resources/blog/) 4. AWS Multi-Partner Opportunities: Invite a Partner # AWS Multi-Partner Opportunities: Invite a Partner Your reseller or SI is on the AWS deal too. Here's what must be in place before you invite them into the ACE opportunity, how many partners can join, how long each has to answer, and what their copy of the opportunity looks like. [![Sabrina Xie](/authors/sabrina-xie.jpg)](/resources/blog/author/sabrina-xie/) [Sabrina Xie](/resources/blog/author/sabrina-xie/) Oct 8, 2026 ![AWS Multi-Partner Opportunities: Invite a Partner](/images/blog/aws-multi-partner-opportunities/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-multi-partner-opportunities%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Co-Sell%2C%20AWS. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-multi-partner-opportunities%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Co-Sell%2C%20AWS. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-multi-partner-opportunities%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Co-Sell%2C%20AWS. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Faws-multi-partner-opportunities%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Co-Sell%2C%20AWS. "Summarize with Perplexity") Table of Contents - [What is an AWS multi-partner opportunity?](#what-is-an-aws-multi-partner-opportunity) - [What must be in place before you invite a partner?](#what-must-be-in-place-before-you-invite-a-partner) - [What are AWS’s rules for inviting a partner to an opportunity?](#what-are-awss-rules-for-inviting-a-partner-to-an-opportunity) - [What does the invited partner’s opportunity look like?](#what-does-the-invited-partners-opportunity-look-like) - [How do you invite a partner to an AWS opportunity in Fours?](#how-do-you-invite-a-partner-to-an-aws-opportunity-in-fours) - [Which responsibilities should you give each partner?](#which-responsibilities-should-you-give-each-partner) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _An AWS multi-partner opportunity is an ACE opportunity that several AWS Partners work together with AWS: each partner who accepts your invitation gets its own opportunity, inside one engagement that AWS owns. AWS lets you invite up to nine partners you’re connected to, and gives each fifteen days to answer. This guide sets AWS’s rules beside the Fours flow._ * * * Acme is sharing an AWS opportunity for Umbrella’s analytics migration. Initech will run the migration, and Umbrella wants to buy through Globex, its reseller. Both partners belong on the opportunity rather than in a thread of forwarded emails, so Acme’s co-sell lead has four questions: what has to be in place before inviting them, how many partners can join, how long each has to answer, and what each partner’s copy of the opportunity looks like. AWS answers all four, mostly in its Partner Central developer guide. The opportunity itself, with its statuses and AWS’s validation, works as described in [how co-sell works on AWS, Azure and Google Cloud](/resources/blog/how-co-sell-works/). AWS’s own people on the deal are a separate list, covered in [the AWS co-sell opportunity team](/resources/blog/aws-co-sell-opportunity-team/). This guide is about the partners you bring. ## What is an AWS multi-partner opportunity? **An AWS multi-partner opportunity is** a customer opportunity in ACE, AWS’s APN Customer Engagements program, that two or more AWS Partners work together with AWS, each from its own opportunity inside a shared engagement. AWS defines the engagement as “a resource owned by AWS for collaboration between multiple AWS Partner accounts and AWS on a customer opportunity.” - **You invite partners in; you don’t hand over your opportunity.** A partner joins through an engagement invitation, and “When invited partners accept, they receive their own opportunity within the same engagement.” - **Each partner keeps its own record.** “Within an engagement, partners maintain and update their opportunities independently,” and members follow each other’s progress through snapshots. - **It arrived with Partner Connections.** AWS announced general availability on January 15, 2025, built on “connections discovery and multi-partner opportunities,” for eligible partners “who have signed the ACE Terms and Conditions and have linked their AWS account to their Partner Central account.” ## What must be in place before you invite a partner? **An accepted connection with that partner in AWS Partner Central.** AWS is explicit: “You must connect with partners before you can invite them to opportunities. This connection grants mutual access to each other’s account IDs, ensuring invitations reach the intended partner account.” In AWS Partner Central: 1. **Find the partner** under **Partner Discovery** in the left navigation. You can search by partner name, keywords, industry, location, partner program, partner type (Consulting Partner, ISV, Reseller, Distributor), specialization, solution type or connection status. 2. **Send a connection request** from the results, with your full name, your contact email and a message explaining why you want to connect. 3. **Wait for the partner to accept.** The request shows Pending response until they answer. Once they accept, the partner shows as Connected under **Partner Connections**, and each of you can see the other’s AWS account ID. **Connect when the partner joins the deal, not when you need the invitation.** Three things set the pace: - **The partner has to act, and the request can lapse.** AWS emails the recipient’s Alliance Lead when a request arrives. A request left without action “within the expiration period” expires and can no longer be accepted, and AWS’s Partner Central guides don’t give that period’s length. - **The partner may be hard to find.** A partner can set its profile to Private, which keeps it out of Partner Discovery, or turn off incoming connection requests. If you can’t find or reach them, ask them to send the request to you. - **Fours picks up connections on a schedule.** Fours refreshes your partner connections from AWS every 6 hours, so a connection accepted this morning may not be in Fours’ partner picker until the next refresh. Keep the connection in place afterwards. End one, and AWS says “you won’t be able to share any new collaborative opportunities with them,” although “any opportunities that were shared while your connection was active will continue without any changes.” ## What are AWS’s rules for inviting a partner to an opportunity? **Connect first, invite no more than nine partners, and expect each to answer within fifteen days or lose the invitation.** Each rule below is AWS’s, from its Partner Central guides and API reference; the last column is how to plan around it. Rule What AWS says How to plan for it Connection ”You must connect with partners before you can invite them to opportunities” Connect as soon as the partner joins the deal, and chase a request they haven’t answered Which opportunities Partners can collaborate on opportunities “that originate from both partners and AWS” Opportunities you share and AWS referrals you’ve accepted both qualify How many ”You can invite a maximum of nine partners to an opportunity” Spend the places on partners with a defined part in the deal What you send A message of 1 to 255 characters, the customer and project details, and the receiver’s responsibilities, all required Write the message as the case for accepting: AWS tells invitees to weigh it with the project title, customer use case and customer business problem How long they have ”If you do not respond to an engagement invitation within fifteen days, it expires, and you cannot participate in the multipartner opportunity” Tell the partner it’s coming and chase before day fifteen. After that, “the sending partner must initiate a new engagement invitation” A decline The partner must give a reason, loses access to the invitation’s details, and AWS notifies you Talk to the partner before you invite them again An acceptance The partner receives “their own opportunity within the same engagement,” created “using data from the sending partner’s opportunity” Your fields seed theirs, so get them right before you invite Review status If yours is still Submitted, theirs stays Submitted until yours is Approved, then they “automatically inherit the Approved status” One AWS review covers everyone, “eliminating the need for multiple reviews” What members see Snapshots, “point in time, immutable copies of specific fields,” and “Once shared, snapshots remain permanently accessible to engagement members” Assume every member keeps what you’ve shared: a later edit adds a revision, it doesn’t withdraw the old one AWS reports each invitation’s outcome to you as an event: Engagement Invitation Accepted, with Engagement Member Added sent to every current member; Engagement Invitation Rejected; or Engagement Invitation Expired, when a partner hasn’t acted for fifteen days. ## What does the invited partner’s opportunity look like? **It’s their own opportunity, in their own account, created from yours and tied to the same engagement.** On acceptance, AWS creates “a new opportunity in your partner account using data from the sending partner’s opportunity,” as its guide puts it to the receiving partner, and adds “additional details required to identify the customer.” Its review status follows yours: - **Yours is still Submitted.** Theirs is Submitted too, and “The Submitted status remains until the sending partner’s opportunity is Approved.” When AWS approves yours, “the other partners’ opportunities will automatically inherit the Approved status.” - **Yours was already Approved when you invited them.** Theirs starts Approved, but “may not have some partner-specific details that were not copied from the sending partner’s opportunity.” AWS asks the receiving partner to add them once the opportunity reaches Qualified or a later stage: the customer use case, delivery models, solution, primary needs from AWS, target close date, expected customer spend, marketing source, and whether AWS funding was used. From then on, the opportunities go their own ways. AWS says the partner’s copy “can be managed and updated like any other opportunity within the partner’s system.” Changes reach the other members as snapshots, and nothing merges by itself: AWS’s guidance is that a partner who spots a relevant change in another member’s opportunity copies it into its own. So when Globex moves its target close date, Acme’s doesn’t move. When an opportunity changes, its owner can create a new snapshot revision, and AWS’s snapshot jobs “automatically create new revisions when the resource changes.” **If you call AWS’s API directly**, one setup step decides whether partners see your later edits. AWS says that without a `ResourceSnapshotJobRole`, “any updates you make to your opportunity will not be visible to other partners in the engagement, and they will continue to see outdated snapshots of your opportunity data.” Its developer guide gives the role’s trust and permissions policies, and the `PutSellingSystemSettings` call that sets it for your company. ## How do you invite a partner to an AWS opportunity in Fours? **From the AWS referral: in the share flow’s Partner Collaboration step, or afterwards with Share With Partners.** Fours sends each partner an AWS engagement invitation through AWS Partner Central, and you can pick only partners your Partner Central account is connected to. The full flow is in [how to invite other AWS partners in Fours](https://doc.fours.com/cosell/cosell-outbound/#invite-other-aws-partners). **While you share.** The AWS share page ends with an optional **Partner Collaboration** step: Field What to enter **Partner Connection Name** Search your connected partners by company name or AWS account ID, and pick one or more **Partner Engagement Type** One or more of seven types, covered in the next section **Comments to share with the partner** Up to 255 characters, the same ceiling AWS puts on an invitation’s message Once you pick a partner, the engagement type and comments become required. Fours sends one invitation per partner you picked, each with the same engagement types and comments, so partners who need different types or different messages are better invited one at a time afterwards. Partner names come from AWS: each connection sync asks Partner Central for the partner’s published company name. A partner whose profile isn’t published appears as **AWS Account** followed by its account ID until a later sync resolves it, so check the ID with the partner before you pick it. **After the referral exists.** Open the AWS referral and click **Share With Partners**. The dialog sends one invitation at a time: your email, which is required, and optionally your name, business title and phone number; then the partner, at least one engagement type and the comments, all required. The button waits on AWS: it stays disabled until AWS has given the referral an opportunity ID, and while an inbound referral is still **Pending Acceptance**. It’s also disabled on a **Draft**, **Create Failed** or **Deleted** referral, and on one whose stage is **Launched** or **Closed Lost**, or that has no stage yet. For Acme’s deal, an illustrative comment to Initech, in 208 characters: > Umbrella is moving its analytics platform to AWS this quarter. We’d like Initech to scope and run the migration, with Globex as reseller. Please accept by Friday; [alliances@acme.example](mailto:alliances@acme.example) will set up a kickoff. **Track the invitations.** The referral’s **Invitations** tab lists every invitation sent on it: Column Shows **Partner** The partner’s name with its AWS account ID, or the account ID alone when it matches none of your connections **Invite Time** When the invitation was sent **Status** The invitation’s status at AWS **Invitation Id** AWS’s ID for the invitation **Sender(s)** The company that sent it **Link to invitation** The invitation’s Overview, Customer Details, Project Details and Partners At AWS, an invitation is pending, accepted, rejected or expired. Fours doesn’t poll for the answer: when a partner accepts or rejects, AWS publishes a status-change event, and Fours reads it through the Amazon EventBridge rule your AWS Partner Central integration set up, then updates **Status**. Right after sending, Fours also reads every invitation on the referral back from AWS and stores the dates, sender, message, and customer and project details AWS returns. Invitations recorded before early October 2026 can show blank dates or no sender until another invitation is sent on that referral. ## Which responsibilities should you give each partner? **Receiver responsibilities are** AWS’s field for “the responsibilities or expectations of the receiver in the context of the invitation,” and every opportunity invitation carries them. Fours’ **Partner Engagement Type** offers seven of AWS’s nine values: Distributor, Reseller, Hardware Partner, Managed Service Provider, Software Partner, Services Partner and Training Partner. AWS’s other two are Co-Sell Facilitator and Facilitator. AWS lists the values without defining any of them, so this table is our guidance, not AWS’s rule: The partner’s part in the deal Responsibility to pick When to invite them Resells your product to this customer, as Globex will Reseller Once the customer has chosen to buy through them Sits behind the reseller in a two-tier deal Distributor With the reseller Implements or migrates the workload, as Initech will Services Partner At the share, if they’re already scoping the work Runs the workload for the customer after deployment Managed Service Provider When managed services are part of the proposal Contributes its own software to a joint solution Software Partner When the joint solution is part of the proposal Supplies hardware for the deployment Hardware Partner When hardware is on the bill of materials Trains the customer’s team Training Partner When training is in the scope of work Plays two parts, such as an SI that also resells Both, in one invitation When the first part begins Two timing rules apply to every row: send the connection request when the partner joins the deal, and send the invitation when they can answer within fifteen days. An invitation is a dated record of who you brought onto the deal. How much credit each partner earns for it is a separate decision, covered in [partner-sourced vs partner-influenced revenue](/resources/blog/partner-sourced-vs-partner-influenced/). ## Frequently asked questions ### How many partners can you invite to an AWS opportunity? Nine. AWS says you can invite a maximum of nine partners to an opportunity, and each must be a partner you’re already connected to in AWS Partner Central. Each partner who accepts gets its own opportunity in the same engagement. ### Do you have to connect with a partner before inviting them? Yes. AWS says you must connect with partners before you can invite them to opportunities, and the connection gives each side the other’s AWS account ID. Find the partner in Partner Discovery, send a connection request, and wait for them to accept it. ### How long does a partner have to accept an AWS engagement invitation? Fifteen days. If the invited partner doesn’t respond within fifteen days, the invitation expires, they can’t join the multi-partner opportunity, and AWS notifies you. To bring them in after that, you have to send a new invitation. ### What does a partner get when they accept your invitation? Their own opportunity, in their own account, created from your opportunity’s data and linked to the same engagement. If yours is still Submitted, theirs stays Submitted until yours is Approved, then inherits the Approved status automatically. ### Can you invite partners to an opportunity AWS referred to you? Yes. AWS says partners can collaborate on opportunities that originate from both partners and AWS. In Fours, accept the referral first: Share With Partners stays disabled while an inbound referral is still Pending Acceptance. ### How does Fours track the partner invitations you send? On the AWS referral’s Invitations tab, which shows each invitation’s partner, invite time, status at AWS, invitation ID and sender, with a link to the invitation. When a partner accepts or rejects, Fours updates the status from AWS’s event instead of polling. ## Takeaways - Connect before the deal needs it: AWS takes invitations only to partners you’re already connected to, and an unanswered connection request can expire. - AWS lets you invite up to nine partners to an opportunity, and gives each fifteen days to answer. After that, only a new invitation brings them in. - Each partner who accepts gets its own opportunity, created from yours, in the same engagement. Its review status follows yours, and what you’ve shared stays with every member. - In Fours, invite partners while you share or with Share With Partners, give each the right responsibilities, and follow the answers on the referral’s Invitations tab. Fours runs AWS, Microsoft and Google Cloud co-sell referrals in one place, including the partners you invite onto AWS opportunities. See how sharing, invitations and tracking fit together in [Fours’ co-sell automation](/platform/cosell/). ## Sources Primary sources for the platform rules cited above. Last verified October 8, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS Partner Central Developer Guide: Working with multipartner opportunities](https://docs.aws.amazon.com/partner-central/latest/developer-guide/working-with-multi-partner-opportunities.html) — The engagement as a resource owned by AWS; connect with partners before inviting them, and the connection's mutual access to account IDs; invitations on opportunities from partners and from AWS; a maximum of nine invited partners per opportunity; the message, project title, customer use case and business problem an invitee reviews; a rejection reason and lost access on rejection; expiry after fifteen days without a response, and a new invitation to try again; the invitee's own opportunity created from the sender's data, with details to identify the customer; Submitted until the sender's opportunity is Approved, then the inherited Approved status; the partner-specific fields to add at Qualified or later; independent updates, snapshots as point-in-time immutable copies that stay accessible to members, snapshot jobs and the UpdateOpportunity guidance; the ResourceSnapshotJobRole warning and PutSellingSystemSettings - [AWS Partner Central Developer Guide: Working with Partner Account Connections](https://docs.aws.amazon.com/partner-central/latest/developer-guide/working-with-account-connections.html) — A connection invitation starts Pending, reveals each side's AWS account ID once accepted, and expires automatically if no action is taken within the expiration period, after which it cannot be accepted; no length is given for that period - [AWS Partner Central Sales Guide: Discovering and managing partner connections](https://docs.aws.amazon.com/partner-central/latest/sales-guide/partner-connections.html) — Partner Discovery and Partner Connections in the left navigation of AWS Partner Central, and what each is for - [AWS Partner Central Sales Guide: Partner Discovery](https://docs.aws.amazon.com/partner-central/latest/sales-guide/partner-discovery.html) — The search criteria, including partner type (Consulting Partner, ISV, Reseller, Distributor), and sending a connection request from the search results - [AWS Partner Central Sales Guide: Partner Connections](https://docs.aws.amazon.com/partner-central/latest/sales-guide/manage-partner-connections.html) — The connection request form (full name, contact email, personalized message); the Alliance Lead email on an incoming request; Pending response and Connected; a connection required for multi-partner collaboration; ending a connection stops new collaborative opportunities while those already shared continue; Private profiles and connection request preferences - [AWS Partner Central API Reference: Invitation](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_Invitation.html) — Every engagement invitation carries a required message of 1 to 255 characters, a required receiver and a required payload that partners use to evaluate whether to accept - [AWS Partner Central API Reference: OpportunityInvitationPayload](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_OpportunityInvitationPayload.html) — ReceiverResponsibilities, the responsibilities or expectations of the receiver, required, with nine valid values (Distributor, Reseller, Hardware Partner, Managed Service Provider, Software Partner, Services Partner, Training Partner, Co-Sell Facilitator, Facilitator) and no definition of each; customer and project details required - [AWS Partner Central API Reference: GetEngagementInvitation](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_GetEngagementInvitation.html) — An engagement invitation's status is PENDING, ACCEPTED, REJECTED or EXPIRED - [AWS Partner Central Developer Guide: Notifications for the AWS Partner Central Selling API](https://docs.aws.amazon.com/partner-central/latest/developer-guide/selling-api-events.html) — The events a sender receives: Engagement Invitation Accepted and Engagement Member Added on acceptance, Engagement Invitation Rejected, and Engagement Invitation Expired when a partner does not act for 15 days; Engagement Member Added notifies all current members - [AWS What's New: Start collaborating on multi-partner opportunities with Partner Connections](https://aws.amazon.com/about-aws/whats-new/2025/01/multi-partner-opportunities-partner-connections/) — Posted January 15, 2025: general availability of Partner Connections, its two capabilities (connections discovery and multi-partner opportunities), and availability to eligible partners who have signed the ACE Terms and Conditions and linked their AWS account to their Partner Central account - [Fours docs: Outbound Referral](https://doc.fours.com/cosell/cosell-outbound/) — Fours behaviour: inviting other AWS partners on an AWS referral through AWS Partner Central, only from your connections, refreshed from AWS every 6 hours; the optional Partner Collaboration step and the Share With Partners dialog; the seven Partner Engagement Types and comments of up to 255 characters; one invitation per selected partner with the same types and comments; when Share With Partners is disabled; the Invitations tab; status read from AWS's status-change event through the EventBridge rule, without polling; partner names from AWS's published company names ## Keep reading - [AWSAWS Marketplace Engagement Score vs Quality ScoreOct 19, 2026](/resources/blog/aws-engagement-score-vs-quality-score/) - [Co-SellAWS Co-Sell Opportunity Team: Who's on Your DealOct 7, 2026](/resources/blog/aws-co-sell-opportunity-team/) - [Co-SellHow to Update an AWS Co-Sell ReferralSep 30, 2026](/resources/blog/update-an-aws-cosell-referral/) - [AWSAWS Fund Request Status, Stages and Claim DeadlineSep 28, 2026](/resources/blog/aws-fund-request-status/) [Browse every post on the Fours Blog](/resources/blog/) ### Stay Updated New posts, product updates and marketplace strategy are shared on LinkedIn as they publish. [Follow Fours on LinkedIn](https://www.linkedin.com/company/suger-inc)