SP-API no longer requires AWS IAM or AWS Signature Version 4 #3701
hudalexa
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Starting October 2, 2023, SP-API no longer requires the use of AWS Identity and Access Management (IAM) or AWS Signature Version 4, which means developers will not need to register for IAM resources or sign SP-API requests with AWS Signature Version 4.
SP-API will continue to use Login with Amazon (LWA) access tokens for each SP-API request. LWA is based on OAuth 2.0, which has been broadly adopted for user-authorized exchanges across sites.
Which marketplaces are affected?
This change applies to all regions.
Who is affected?
All developers who registered with SP-API before October 2, 2023.
What action is required?
No immediate action is required. These changes are integrated into our production environment. For requests with AWS Signature Version 4, we’ll disregard the signature and proceed with LWA authorization.
MWS developers
MWS developers who are actively migrating to SP-API can use the following guidance:
Developers using SDKs
Version 2.0 of the Java and C# Software Development Kits are available starting October 2, 2023. No immediate action is required, but we highly recommend using the updated SDKs as they save time during signing and provide more details for LWA Authorization exceptions, including information on errors returned during LWA Authorization using the new custom LWAException.
SDK versions 1.0 for Java and C#, with optional AWS signing, are still available, but will be deprecated by the end of 2023.
For more information on connecting to SP-APIs using SDKs, refer to Automate your SP-API calls using Java SDK and Automate your SP-API calls using C# SDK.
Resources
If you have questions or need assistance, contact the Selling Partner API Developer Support team via the Contact Us form.
Beta Was this translation helpful? Give feedback.
All reactions