airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
https://airbyte.com
Other
15.55k stars 4.01k forks source link

[source-amazon-sellerpartner] Access to requested resource is denied #38212

Open andreyAtBB opened 4 months ago

andreyAtBB commented 4 months ago

Connector Name

amazon-seller-partner

Connector Version

4.2.3

What step the error happened?

During the sync

Relevant information

When doing historical data sync which includes Orders, OrderItems, ListFinanicalEvents stream we are receiving error "Access to requested resource is denied." on Orders.

Airbyte support team looked into this and confirmed missing roles in their Amazon App. Quote:

It looks like is is possible to add the roles to our app, but it requires Amazon's approval and it looks like this is a fairly rigorous process from comments in this issue. So unfortunately, at the moment our Amazon Seller Partner source connector does not support syncing regulated orders.

Judging by what’s written in this issue and this issue it looks like we have a very little chance to get our own app approved as well, so it would be great if Airbyte, as an Amazon client/partner, can reach out to them and clarify this process, requirements and timing.

Relevant log output

2024-05-15 00:10:46 replication-orchestrator > failures: [ {
  "failureOrigin" : "source",
  "failureType" : "system_error",
  "internalMessage" : "403 Client Error:  for url: https://sellingpartnerapi-na.amazon.com/orders/v0/orders?NextToken=TOKEN&MarketplaceIds=XYZ",
  "externalMessage" : "Access to requested resource is denied.",
  "metadata" : {
    "attemptNumber" : 9,
    "jobId" : 11823074,
    "from_trace_message" : true,
    "connector_command" : "read"
  },
  "timestamp" : 1715728285452,
  "streamDescriptor" : {
    "name" : "Orders"
  }
}

Contribute

marcosmarxm commented 4 months ago

Hello @andreyAtBB, thank you for reporting the issue. I have forwarded it to the connector team for investigation and resolution.