Skip to main content
All CollectionsAWS MarketplaceCo-sell
Connect to AWS Partner Central
Connect to AWS Partner Central

Set up your APN (Amazon Partner Network) Customer Engagements (ACE) program to start co-selling with your AWS Cloud Partner.

Leslie avatar
Written by Leslie
Updated over 2 weeks ago

This connection allows Tackle to access and push records to ACE on your behalf. Ensure you have the appropriate permissions and complete the required setup and steps to get started.

Required setup

Permissions

You must have the required permission to set up ACE and related features and connections. Permissions include:

  • AWS admin

  • Alliances lead

  • SFDC admin (if you're using the Tackle for Salesforce integration)

Tip: If you need to work with others who have permissions, you can add collaborators in Tackle > Account Settings > Co-Sell.

Complete setup in Tackle

In Tackle, you'll find a guided setup page. To access and start setting up a connection:

  1. In Tackle, go to the left menu and click Account Settings > Co-Sell tab.

  2. In the AWS section, click the tile labeled “Connect Tackle to ACE to co-sell with AWS” to reach the AWS co-sell setup page.

  3. Complete the guided setup steps and workflows below (starting with Step 1).

  4. When you're done completing the steps, test your AWS account's connection with Tackle.

Note

If you are migrating to Tackle from a different co-sell solution, set up the Salesforce integration first so that you can continue using your previous solution until you are ready to switch. When you are, set up co-sell with AWS using the steps above. Otherwise, follow this guide first to set up co-sell on AWS before setting up your Salesforce integration.


​Step 1: Prepare you AWS account

  1. Create an AWS account (console). This account will be used when publishing your listings and managing disbursement of sales. It is easiest to create a brand new AWS account that is linked to your master account. By creating or linking a new account🔗 you are isolating your production and development accounts from your Tackle managed listings. Log in to this account to complete the following steps.
    Important: If you have already set up a listing with AWS, you have completed this step.

  2. Ensure that the account has access to create roles, stacks, enroll in Commerce Analytics Service, and configure financial services.

  3. Accept the AWS Terms and Services🔗.

  4. Complete the Tax Information Interview🔗.

  5. Complete the Banking Information🔗.

  6. Complete the Company Public Profile🔗.

Step 2: Create a sandbox user

Set up a sandbox user as part of the AWS requirements to use the APN interface. This IAM user is not used by Tackle for any other purpose. Reference AWS documentation for more information about creating an IAM user🔗 for your Sandbox environment.

Required permissions: AWS admin

  1. Sign in to the AWS Management Console🔗 and click IAM to see the IAM dashboard.

  2. Click Users > Add users.

  3. Enter the following information below for the new user and then click Next:


    User name: apn-ace-{partnerName}-AccessUser-beta

    Replace partnerName with your company name

  4. You can skip adding permissions. Review and click Create user.

  5. You are then directed back to the dashboard. Find the user you just created and click to open.

  6. Under Summary, copy the ARN.

  7. In a separate browser tab, open the Tackle platform, and go to Account settings > Co-sell > Create sandbox user.

  8. In the AWS Management Console browser tab, open the user you just created, and copy and paste the Sandbox ARN from AWS Management Console to Tackle.


Step 3: Create a production role

For Tackle to support you in the AWS marketplace, allow Tackle to manage your listings and provide support for transactions.

AWS uses a Cloud Formation Template (CFT) for their resource provisioning.

  1. In Tackle, go to Account settings > Marketplace > AWS > Grant Tackle Access🔗 (for marketplace) or to Account settings > Co-sell > AWS🔗 (for Co-Sell only).

  2. Click the link (under Grant Tackle Access for marketplace, or under Connect Tackle and AWS Marketplace for co-sell) to initiate the Cloud Formation Template (CFT) that creates a Tackle role. (You only need to do this once, either for co-sell or marketplace.)

  3. Finish the process in the AWS Marketplace Management Portal. Review the template URL, stack name and parameters, then check the box to acknowledge creation and click Create stack.

  4. In the AWS Marketplace Management Portal, go to AWS Account Roles🔗 and search for Tackle.

  5. Click on the Role Name for the role you just created. In the page that opens, under Summary, copy the Tackle Role ARN.

  6. In Tackle, in the same page you used above, paste the ARN you just copied in the Tackle Role ARN field and click Save. You only need to do this once, either for co-sell or marketplace.

Step 4: Connect Tackle to ACE

Required permissions: Alliance Lead🔗

These tasks should be completed by someone who has Alliance Lead access to the AWS Partner Network (APN) portal. The AWS account and roles must be created before you can complete this section.

  1. Set up the S3 Sandbox bucket environment. Sign in to Partner Central🔗, scroll to the bottom of the page and click Initiate onboarding request.

  2. Complete the form with the following information and click Next:

    Partner CRM system: Salesforce
    What solution would you be using to integrate your CRM with APN: Third Party Solution
    Name of third party solution provider: Tackle
    Estimated integration start date: Today +1

  3. Add third-party contact as [email protected] and click Next.

  4. Copy and paste the Sandbox ARN and Production ARN collected when setting up the AWS account and creating roles. Mark No to backfill in AWS Partner Central.

    Note: If you want to backfill, you should still mark No in Partner Central. Failure to do this may cause delays. You can reach out to your Tackle Onboarding team at [email protected] to backfill opportunities from the past year.

  5. Click Submit to create the Sandbox bucket. You will see confirmation that your request was submitted. If the details are accurate, the Sandbox will be provisioned in less than 5 minutes. Refresh the page to confirm it was completed.

  6. In Partner Central under Next Steps, click Mark Implementation Complete and then Mark Testing Complete.

    Note: As a third-party vendor, Tackle has already completed UAT testing, so it does not need to be completed for individual vendors.

  7. In Partner Central, under Next Steps, click Update ARN for Prod to confirm role details. Review and click Submit to create the Production bucket. You will see confirmation that your request was submitted. If the details are accurate, the Product environment will be provisioned in less than 5 minutes. Refresh the page to confirm it was completed.

  8. Once launched, under Next Steps, click Activate integration.

  9. In a separate browser tab, open the Tackle platform, and go to Account settings > Co-sell > AWS > Set up ACE environment🔗.

  10. In the Partner Central browser tab, on the same Integrationdetails page under IAM policy, copy the Production - IAM policy and paste it into the Tackle platform next to Production IAM policy.

  11. Respond to the last question about any previous co-sell solutions you were using, by marking Yes or No.

Note

If you were previously using a different co-sell solution, Tackle maintains existing links between your Salesforce Opportunity and Co-sell records as long as our ACE CRM IDs match your Salesforce Opportunity IDs (for example, both IDs start with 006). If you were previously using a co-sell solution with matching IDs, and would like to backfill the data from the past year, reach out to your Tackle Onboarding team at [email protected].

Step 5: Link Partner Central to the marketplace

Important

If you use AWS IAM Identity Center (formerly AWS Single Sign-On) to sign in to your AWS Marketplace account, you must sign in to your AWS Marketplace account with administrator privileges first, before performing the rest of these instructions. Then, open a new browser tab and proceed with the steps below.

  1. Sign in to AWS Partner Central🔗 with an Alliance Lead or Cloud Admin role.

  2. In the Account Linking section on the homepage, click Link Account.

  3. Go to Account Linking and then select Link Accountagain.
    Note: This is separate from the similar action you took in step 2.

  4. Select IAM user, and then enter the AWS Account ID for your AWS Marketplace account.

  5. Click Next, and then sign in to the AWS account.

  6. Click Allow to authorize the connection between your AWS Partner Central and AWS Marketplace accounts.

For more information, see AWS documentation🔗 in Partner Central.

Step 6: Solutions offered

Required permissions: Alliance Lead🔗, Tackle Admin

Solutions are similar to offerings — a group of one or more AWS Marketplace listings that you include for co-sell, which are required by AWS of all partners. This section will help you create solutions in your ACE portal, then connect them to your Tackle account.

  1. Return to your Tackle AWS Co-Sell setup guide in Tackle and click Step 6: Solutions Offered.

  2. If your co-sell closing process requires additional fields for special programs to show, click the Yes radio button In the section titled “Do you complete the SaaS documentation tab when launching a deal?” Otherwise, or if you don’t know what this question means, click No.

  3. Next, you’ll need to add details for each ACE solution you want to add to Tackle. If you only have a few solutions to add, you can input each manually. Otherwise, you can export all your solutions from ACE and import them into Tackle automatically.

    • Importing solutions manually:

      1. Enter the Solution Name, as well as the corresponding Solution ID, for each solution you want to add to Tackle, into the fields in your Tackle AWS co-sell setup guide.

    • Importing solutions in bulk:

      1. Sign in to your AWS Partner Central account and navigate to View Opportunities.

      2. Under the Opportunities Bulk Actions drop down, click Import Opportunities. Then, scroll down and click Start import.

      3. Under the Products and Offering section, click the link titled “Your offered solutions and AWS products can be viewed here”. This will download a file containing every solution in your account.

      4. Return to your Tackle account in the AWS co-sell setup guide. In step 6, click Bulk Upload, then select and upload the file you just downloaded from your AWS Partner Central account.

      5. Once Tackle processes your upload, you’ll see all the solutions listed below.

  4. Now that all of your solutions are listed in your Tackle account, click the trash icon to remove a solution or the disk icon to save your current solutions and add another.

  5. Use the Default checkbox to select one or more solutions as your default offering. You must choose at least one default solution.

  6. When you’re finished, click Continue.

Step 7: Give Tackle access to your S3 bucket

Tackle needs access to your S3 bucket in order to manage your co-sell actions.

Note

ACE uses an S3 Bucket in their own AWS account (not your AWS Account) to share Lead/Opportunity events with you. This S3 bucket is limited just to you, and is leveraged for both creating and reading events. You grant access to this S3 Bucket with an IAM User or Role. In order for Tackle co-sell to work on your behalf, we use the IAM Role that you own to access the ACE S3 Bucket. This gives you control over access as well as access monitoring if needed.

The required permissions for this individual bucket are:

- s3:DeleteObject

- s3:DeleteObjectTagging

- s3:GetObject

- s3:GetObjectTagging

- s3:PutObject

- s3:PutObjectAcl

- s3:PutObjectTagging

  1. In Tackle, go to the left menu and click Account settings > Co-Sell > Give access to your S3 bucket🔗.

  2. Click Grant access. The AWS Management Console will open in a new tab.

  3. In the AWS Management Console, click Create stack to finish granting access.

  4. Click the Refresh icon until your connection is validated.

  5. Test the connection in Tackle.

Step 8: Enable role permissions

Required permissions: Alliance Lead🔗

  1. Return to your Tackle AWS co-sell setup guide and click Step 8: Enable Role permissions.

  2. Click Launch Stack to open your AWS Management Console in a new tab. Click Grant Access if prompted.

  3. In your AWS Management Console, click Create Stack to finish granting access. Your CFT will get to work in your AWS account setting up your Tackle role parameters.

  4. Click the Refresh icon until your connection is validated.

  5. That’s it! You’ve finished all 8 steps to set up your Tackle account to co-sell on AWS. All that’s left to do is test your connection and set up your Salesforce integration, if you haven’t already.

Before you launch: Test your connection in Tackle

Before we can go live with co-selling, we need to use Tackle's test tools to make sure everything is in working order.

  1. In the Tackle platform, go to Account settings > Co-sell🔗 and click AWS.

  2. Click Step 8: Enable Role permissions to expand the step. Complete the steps shown if you have not already, then click Test connection.

  3. If your test is successful, you will see confirmation that you have successfully set up co-sell in Tackle.

    Note: If your test was not successful, you'll see an error message. Check to be sure all the steps are complete and then repeat giving Tackle access to your S3 bucket, and clicking Test connection. If the issue persists, contact Tackle Support.

  4. You're done! Your Tackle account is fully connected to AWS and ready to co-sell. You can now follow our guide to create new co-sell opportunities in Tackle. See next steps to integrate your Tackle account with Salesforce.

Next steps: Integrate with Salesforce

Now that you've set up in Tackle, you will see a status that shows if your organization has the Salesforce integration set up or not. Click the Email setup steps to share this with your Salesforce admin.

Tip: If you don't have Salesforce, you can still co-sell, but the integration can improve your workflow by allowing you to make changes directly in Salesforce.

Did this answer your question?