Overview

On July 21 2022 Amazon published a Quick Start guide that lets developers run the Selling Partner Reports API entirely on AWS. The reference architecture builds an event‑driven pipeline that creates, fetches, and stores marketplace reports without manual intervention, a capability that matters to sellers who need up‑to‑the‑minute inventory, pricing, or order information.

Key Points

• Publication date — The Quick Start was released on July 21 2022, providing an out‑of‑the‑box CloudFormation blueprint for SP‑API reporting.
• Event‑driven core — AWS EventBridge, Lambda, and SQS work together to trigger report requests and process asynchronous responses, eliminating the need for scheduled scripts.
• One‑click provisioning — A single CloudFormation template creates IAM roles, S3 buckets, SNS topics, DynamoDB tables, and all required Lambda functions, allowing a team to stand up the solution in under ten minutes.
• Multi‑report support — The deployment includes sample configurations for inventory, order, and settlement reports; swapping the report type is as simple as changing a parameter value in the stack.
• Full automation — From the moment a scheduled rule fires to the point the report file lands in S3, every step is orchestrated automatically, shrinking processing time from several hours to a few minutes.
• Built‑in security — Least‑privilege IAM policies and Secrets Manager storage for SP‑API credentials keep access tightly controlled and meet Amazon’s data‑protection requirements.

How the Selling Partner Reports API Quick Start Works

1. Deploy the CloudFormation stack — Users launch the supplied template, which provisions an S3 bucket for report files, an SNS topic for notifications, an SQS queue for message buffering, and a suite of Lambda functions that drive the workflow. For instance, a seller clicks “Create stack” in the AWS console, supplies their SP‑API client ID and secret, and the entire environment is ready in roughly nine minutes.
2. Store SP‑API secrets securely — The stack writes the client ID, client secret, and refresh token to AWS Secrets Manager. A dedicated Lambda reads these secrets at runtime to request an access token, guaranteeing that no credential appears in code or environment variables. In a test deployment, the Lambda exchanged the refresh token for a bearer token in less than two seconds.