Legacy version
This feature is an older experience in Tackle that will soon be retired or no longer supported. If you have questions or want to upgrade to the latest experience, contact [email protected].
To figure out whether your Tackle account uses this legacy version or the latest experience in to your Tackle account and click Integrations in the left menu. If you see separate integration cards for AWS Marketplace and AWS co-sell, follow the steps in this article. If you see a single integration card for AWS, contact our support team at [email protected] instead to troubleshoot any connection errors between Tackle and AWS.
Resolve AWS errors (legacy)
The Tackle marketplace integration for AWS uses a service role in your AWS account to connect to marketplace-related resources such as S3 buckets, SQS queues, and KMS keys. Occasionally, permissions associated with these roles or resources are changed, or the resources are deleted. These changes might be accidental or intentional. If and when Tackle becomes disconnected from your marketplace activity due to these changes, Tackle may be unable to perform critical services such as registering orders or tracking disbursed revenue.
In many cases with AWS connectivity errors, Tackle will display a banner in the user interface. This banner includes a link to view a detailed error report. You can use the information from the detailed error report with this document to resolve the issue.
Important
This is not a comprehensive list of all AWS errors. If you have errors not included on this list, complete the steps to resolve any that are documented here. In many cases, this will resolve the errors that are not documented. If you resolve all the errors documented on this page and are still receiving AWS errors in the Tackle Platform, contact Tackle Support🔗.
Identify the error
Click See detailed error report on the banner in the Tackle Platform.
The detailed error report should display in a pane on the bottom of the banner. In the example below, the service is "AWS Role" and the error title is "Failed to assume vendor's role." Note the service and error titles you see on your error, and refer below.
Understand and resolve the error
Each error is associated with a service integrated with AWS:
AWS Role errors
AWS role errors will disrupt most Tackle features, particularly private offer creation and processing as well as listing updates.
Common AWS Role errors include:
Failed to assume vendor's role
This error indicates that Tackle is not able to assume the service role (aka the “Tackle Role”), either because the role does not exist or because the role’s permissions have been changed.
This error will look something like:
Failed to assume vendor's role. Error: An error occurred (AccessDenied) when calling the AssumeRole operation: User: arn:aws:iam::003526222725:user/tackle-marketplace-AR is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::{AWS_ACCOUNT_NUMBER}:role/Tackle-Role-Tackle-{UNIQUE-ID}
To resolve this error, you will need the following resources:
AWS Admin with permission to add/remove CloudFormation Templates and resources
Tackle Admin to access Tackle Platform setup section
Steps to resolve this error:
Locate the Amazon Resource Name (ARN) of the Tackle Role in the error. This is located at the end of the error message and is formatted like: arn:aws:iam::{AWS_ACCOUNT_NUMBER}:role/Tackle-Role-Tackle-{UNIQUE-ID}.
Log in to the AWS console and visit Identity and Access Management (IAM) → Roles🔗. Search for “Tackle”. Verify whether or not a role exists that matches the ARN shown in the error message.
If a matching role does exist, its permissions may need to be updated. Follow this guide to update your Tackle Role permissions.
If a matching role does not exist, visit Step 2 in AWS Marketplace Settings in Tackle🔗 and complete all actions, including launching and executing the CloudFormation stack to create the role, and paste the role ARN back into the Tackle Platform.
This issue should resolve as soon as the process is completed.
SDDS errors
SDDS errors will disrupt reporting on your AWS Marketplace transactions and can impact accurate billing for your Tackle service.
Generally, SDDS errors indicate that SDDS setup was not fully completed. If SDDS setup was fully completed and there are still errors, further investigation by Tackle will be required.
Verify that SDDS setup is complete
To resolve this error, you will need the following resources:
AWS Admin with permission to add/remove CloudFormation Templates and resources
Tackle Admin to access Tackle Platform setup section
Steps to resolve this issue:
Check AWS Marketplace settings in Tackle🔗 to see if SDDS setup is completed.
If steps 5 and 6 are not completed (any portion of the circle in the Tackle Platform is grey), fully complete steps 5 and 6 in Tackle🔗.
If the steps are completed (the circle in the Tackle Platform is green), proceed to step 2.
Navigate to CloudFormation → Stacks🔗. Search for "sdds-resources".
If the stack is not present, fully complete steps 5 and 6 in Tackle🔗.
If the stack is present, proceed to step 3.
Navigate to S3 buckets in AWS Console. Search for "tackle-marketplace-sdds-<company name>".
If the bucket is not present, contact Tackle Support🔗.
If the bucket is present:
Click the circle to the left of the bucket.
Click Copy ARN. Save this information someplace accessible.
Compare this to the "S3 ARN" listed in Tackle AWS Marketplace settings🔗. Note the ARN listed in Tackle, if they differ.
Contact Tackle Support🔗 with the above information.
If you completed the setup as part of this process, allow 24 hours for any errors to clear in the Tackle Platform.
Reconnect to AWS (legacy)
If your Tackle account is disconnected from AWS Marketplace or needs reconfiguration, you can fix this by reconnecting to avoid service or data disruption in your account. These marketplace connections ensure that you can access reporting data and your Tackle account billing is correct. After you’ve reconnected Tackle with the cloud marketplaces, you can access metrics and details as you transact in Tackle.
Connecting to the cloud for the first time? See Connect to AWS (legacy).
Reconnect Tackle to AWS (legacy)
Reconnecting Tackle to AWS Marketplace requires an AWS Admin to remove existing CloudFormation Templates (also referred to as "stacks") in AWS prior to re-completing the steps in the Tackle Platform.
You will need the following resources:
AWS Admin with permission to add/remove CloudFormation Templates
Tackle Admin to access Tackle Platform setup section
These permissions should belong to the same person. You can easily invite your AWS Admin as a Tackle Admin user by using the Tackle Platform's user management feature🔗.
Remove CloudFormation Templates
Go to Cloud Formation > Stacks🔗 section in your AWS Management Console. In most cases, the stacks should be located in
us-east-1, but they may be located in another region instead.Search for any of the following stacks:
cas-resourcesorder-notifications-resourcessdds-resourcescustom-iam-policycas-custom-iam-policy
Note: Your account likely won’t have every one of the above stacks listed, but you should plan on removing each of these stacks that is present.
Click the circle to the left of the stack to select it.
Click the Delete button near the top-center of the tab to initiate the removal of the stack.
When the stack has finished deleting, repeat this step for each stack listed in step 2 that you found in your account.
Rerun the stacks
Note
The Tackle Platform UI may still contain values from deleted resources above and may still indicate they are available. Please ignore this and regenerate the new values.
Sign in to Tackle and go to Integrations > AWS Marketplace🔗.
Complete steps 3 through 6.
Important: Remember to re-enroll in Seller Data Feeds Delivery Service with the new values provided.
Allow 24 hours for any errors to be cleared from your Tackle Dashboard.