Skip to main content
All CollectionsAWS MarketplaceTroubleshooting
AWS connection errors
AWS connection errors

Diagnose and solve any errors in your connection between Tackle and Amazon Web Services

Steve Stormoen avatar
Written by Steve Stormoen
Updated over 2 weeks ago

Resolve AWS errors

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

  1. Click See detailed error report on the banner in the Tackle Platform.

  2. 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:

  1. 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}.

  2. 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.

    1. If a matching role does exist, its permissions may need to be updated. Follow this guide to update your Tackle Role permissions.

    2. 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.

  3. This issue should resolve as soon as the process is completed.

CAS errors

CAS errors will disrupt reporting on your AWS Marketplace transactions and can impact accurate billing for your Tackle service.

Common CAS errors include:

The role with name MarketplaceCommerceAnalyticsRole cannot be found

This error means that the MarketplaceCommerceAnalyticsRole does not exist in your AWS environment or is not visible to the Tackle Role.

This error will look something like:

Unable to list attached role policies for MarketplaceCommerceAnalyticsRole. Error: An error occurred (NoSuchEntity) when calling the ListAttachedRolePolicies operation: The role with name MarketplaceCommerceAnalyticsRole cannot be found.

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:

  1. Log in to the AWS console and visit Identity and Access Management (IAM) → Roles🔗. Search for “MarketplaceCommerceAnalyticsRole”.

    1. If the role “MarketplaceCommerceAnalyticsRole” exists:

      1. Click on the box to the left of the role “MarketplaceCommerceAnalyticsRole”.

      2. Click Delete.

      3. Follow the steps in Step 4 in AWS Marketplace settings🔗, which involves submitting the “Enroll into Marketplace Commerce Analytics Service” form in the AWS Marketplace Management Portal. In the enrollment form, choose Create and use a new IAM role.

      4. Paste the “SNS Topic ARN” and “S3 Bucket Name” from the Tackle Platform into the form fields in AMMP and click Enroll.
        ​

    2. If the role “MarketplaceCommerceAnalyticsRole” does not exist:

      1. Follow the steps in Step 4 in AWS Marketplace settings🔗, which involves submitting the “Enroll into Marketplace Commerce Analytics Service” form in the AWS Marketplace Management Portal. In the enrollment form, choose Create and use a new IAM role.

      2. Paste the “SNS Topic ARN” and “S3 Bucket Name” from the Tackle Platform into the form fields in AMMP and click Enroll.
        ​

  2. Allow 24 hours for any errors to clear from the Tackle Platform.

Unable to list attached role policies for MarketplaceCommerceAnalyticsRole

This error means that the Tackle Role in your AWS account does not have sufficient permissions to inspect policies attached to the MarketplaceCommerceAnalyticsRole.

This error will look something like:

Unable to list attached role policies for MarketplaceCommerceAnalyticsRole. Error: An error occurred (AccessDenied) when calling the ListAttachedRolePolicies operation: User: {TACKLE_ROLE_ARN} is not authorized to perform: iam:ListAttachedRolePolicies on resource: role MarketplaceCommerceAnalyticsRole because no identity-based policy allows the iam:ListAttachedRolePolicies action

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:

  1. Log into the AWS console and visit CloudFormation → Stacks🔗. Search for a stack named “cas-custom-iam-policy”.

    1. If the stack “cas-custom-iam-policy” exists:

      1. Click the circle next to the stack named “cas-custom-iam-policy”.

      2. Click Delete to remove the stack and its resources.

      3. Visit Step 7 in AWS Marketplace settings🔗 in Tackle to launch and execute the stack.

    2. If the stack “cas-custom-iam-policy” does not exist, visit Step 7 in AWS Marketplace settings🔗 in Tackle to launch and execute the stack.

  2. Allow 24 hours for any errors to clear from the Tackle Platform.

An error occurred (ValidationException) when calling the GenerateDataSet operation: An error occurred while processing request

This error means that the MarketplaceCommerceAnalyticsRole can not access your reporting data.

This error will look something like:

Encountered an error when attempting to run GenerateDataSet operation for {VENDOR ID}. Error message: An error occurred (ValidationException) when calling the GenerateDataSet operation: An error occurred while processing request.

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:

  1. Log in to the AWS console and visit Identity and Access Management (IAM) → Roles🔗. Search for “MarketplaceCommerceAnalyticsRole”.

  2. Click on the box to the left of the role “MarketplaceCommerceAnalyticsRole”.

  3. Click Delete.

  4. Follow the steps in Step 4 in AWS Marketplace settings🔗, which involves submitting the “Enroll into Marketplace Commerce Analytics Service” form in the AWS Marketplace Management Portal. In the enrollment form, choose Create and use a new IAM role.

  5. Paste the “SNS Topic ARN” and “S3 Bucket Name” from the Tackle Platform into the form fields in AMMP and click Enroll.

  6. Allow 24 hours for any errors to clear from the Tackle Platform.

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:

  1. Check AWS Marketplace settings in Tackle🔗 to see if SDDS setup is completed.

    1. 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🔗.

    2. If the steps are completed (the circle in the Tackle Platform is green), proceed to step 2.
      ​

  2. Navigate to CloudFormation → Stacks🔗. Search for "sdds-resources".

    1. If the stack is not present, fully complete steps 5 and 6 in Tackle🔗.

    2. If the stack is present, proceed to step 3.
      ​

  3. Navigate to S3 buckets in AWS Console. Search for "tackle-marketplace-sdds-<company name>".

    1. If the bucket is not present, contact Tackle Support🔗.

    2. If the bucket is present:

      1. Click the circle to the left of the bucket.

      2. Click Copy ARN. Save this information someplace accessible.

      3. Compare this to the "S3 ARN" listed in Tackle AWS Marketplace settings🔗. Note the ARN listed in Tackle, if they differ.

      4. Contact Tackle Support🔗 with the above information.
        ​

  4. 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

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.

Reconnect Tackle to AWS

Reconnecting Tackle to AWS Marketplace requires an AWS Admin to remove existing resources and 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 and resources

  • Tackle Admin to access Tackle Platform setup section

These should be the same person. You can easily invite your AWS Admin as a Tackle Admin user and remove the user account after by using the Tackle Platform's user management feature🔗.

Remove S3 buckets

  1. Go to the S3 section🔗 of your AWS Management Console.

  2. Search for the following buckets:
    ​

    • tackle-marketplace-sdds-<company name>

    • marketplace-data-<company name>
      ​

  3. Click the circle next to the S3 bucket to select it.
    ​

  4. Click Delete on the top right to delete the S3 bucket.
    ​

  5. Repeat for both buckets.

Remove AWS generated role

  1. Go to the IAM section🔗 of your AWS Management Console.

  2. Click on the Roles tab.

  3. Search for MarketplaceCommerceAnalyticsRole.
    ​

  4. Click the box to the left of MarketplaceCommerceAnalyticsRole to select the role.
    ​

  5. Click the Delete button in the top right of the tab.
    ​

Remove stacks

  1. Go to Cloud Formation > Stacks🔗 section in your AWS Management Console. The stacks should be located in US-EAST-1 but may be located in another region.

  2. Search for these stacks:
    ​

    • tackle-role

    • cas-resources

    • sdds-resources

    • cas-custom-iam-policy
      ​

  3. Click the circle to the left of the stack to select it.
    ​

  4. Click the Delete button near the top-center of the tab to initiate the removal of the stack.
    ​

  5. When complete, repeat for all stacks in step 2.

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.

  1. Sign in to Tackle and go to Account Settings > Marketplace🔗.

  2. Select AWS and go to Step 2: Grant Tackle Access🔗.

  3. Click Launch Stack and follow the instructions.

  4. Complete steps 3 through 7.


    ​Important: Remember to re-enroll in Commerce Analytics Service and Seller Data Feeds Delivery Service with the new values provided.
    ​

  5. Allow 24 hours for any errors to be cleared from your Tackle Dashboard.

Related Articles
Connect to AWS Marketplace
Connect to AWS Partner Central
Set up Co-Sell
Google connection errors
AWS permissions errors
Did this answer your question?