Active Data Exchange subscription not visible in Marketplace; API calls failing

Based on the information available, there appears to be a discrepancy between your Data Exchange subscription status and Marketplace visibility. Here are some key points to understand about AWS Data Exchange subscriptions:

When you subscribe to a product in AWS Data Exchange, the subscription should appear on your AWS bill according to the payment schedule as part of your AWS Marketplace charges. Active subscriptions grant you access to view and export all of the product's data sets during the subscription duration.

You can view all of your active product subscriptions and their auto-renewal status on the Subscriptions page of the AWS Data Exchange console. This is separate from the AWS Marketplace Management Portal view.

For subscription verification requirements (effective April 8, 2025), providers must review and approve subscribers for their products. If a subscription request hasn't been approved yet, this could potentially cause access issues.

If your subscription shows as active in Data Exchange but isn't visible in Marketplace, and your API calls are failing, this suggests a synchronization issue between the two services. I recommend:

1. Verifying that the subscription has been fully processed and approved by the provider
2. Checking if there are any pending subscription verification requirements
3. Contacting AWS Support directly, as this appears to be a technical issue requiring investigation into your specific account and subscription status

The mismatch between the two interfaces preventing API access is not a standard behavior and would require AWS Support to investigate the underlying cause.
Sources
Product subscriptions in AWS Data Exchange - AWS Data Exchange User Guide
Subscription verification for providers in AWS Data Exchange - AWS Data Exchange User Guide

This mismatch between AWS Data Exchange showing an active subscription and AWS Marketplace not displaying it — with API calls failing as a result — is not standard behavior and typically indicates a synchronization or permissions issue. Here are the steps I'd recommend:

1. Check IAM Permissions

Ensure the IAM user/role you're using has the necessary permissions for both services. You need:

• AWS Data Exchange: Permissions from the AWSDataExchangeSubscriberFullAccess managed policy (or equivalent custom policies covering dataexchange:* actions)
• AWS Marketplace: The aws-marketplace:ViewSubscriptions permission to see subscriptions in the Marketplace console

If your account has SCPs (Service Control Policies) at the organization level restricting aws-marketplace:* actions, this could cause the subscription to be invisible in the Marketplace UI even though Data Exchange shows it as active.

2. Verify Subscription Status in the Data Exchange Console

Go to AWS Data Exchange Console → Subscriptions and confirm:

• The subscription is listed as Active (not pending provider approval)
• The subscription hasn't expired (check the end date)
• Subscription verification has been completed (as of April 2025, providers must approve subscribers)

3. Check the Region

While the AWS Data Exchange catalog is global, the underlying resources (data sets, revisions, assets) are regional. Ensure your API calls target the same region where your subscription's data sets reside.

4. Contact AWS Support

Since this appears to be a backend synchronization issue between Data Exchange and Marketplace, I'd recommend opening an AWS Support case with the following details:

• Your AWS Account ID
• The subscription ID(s) that show as active in Data Exchange
• The specific API error messages you're receiving
• Screenshots showing the active status in Data Exchange and the absence in Marketplace

The Marketplace/Data Exchange team can investigate the internal state of your subscription entitlements and resolve any sync discrepancies.

5. Workaround: Use the Data Exchange API Directly

While waiting for resolution, you can try accessing your entitled data sets using the AWS Data Exchange API (ListDataSets, GetDataSet, etc.) rather than relying on the Marketplace entitlement path, if your active subscription is indeed valid on the Data Exchange side.