- Newest
- Most votes
- Most comments
The issue you're experiencing is related to how certain AWS services are represented in the IAM console. Some AWS services, including the Amazon Selling Partner API (SP-API), may not appear as standalone services in the IAM policy editor.
This doesn't mean you can't create policies for these services - it just means they might not be directly visible in the service selection dropdown. This is because not all AWS services have full support for IAM policy summaries and the visual editor.
To create a policy for Amazon SP-API, you have a few options:
-
Use the JSON editor instead of the visual editor to manually create the policy with the appropriate actions and resources for SP-API.
-
Look for the service under a different name or category. Some APIs are grouped under their parent services.
-
Create a custom policy with specific actions needed for SP-API access. You'll need to know the exact action names (like "sellingpartnerapi:action").
If you're certain about the exact permissions needed, creating a custom JSON policy is often the most direct approach when dealing with services that aren't explicitly listed in the visual editor.
Remember that even as a root user, you're still limited by the services that are exposed in the IAM console interface. This isn't a permissions issue but rather relates to how certain services are represented in the IAM policy tools.
Sources
Troubleshoot IAM policies - AWS Identity and Access Management
AWS Identity and Access Management (IAM) - Manage Permissions
answered a year ago
Amazon SP-API isn't available by default in IAM permission policy list since it's not part of an AWS Service.
To use this api and set the correct permission policies, you need to follow the below steps:
- Integrating Selling Partner API: https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-gen-ai-selling-partner-api/integrating-sp-api.html
- Selling Partner API role configuration: https://developer-docs.amazon.com/sp-api/docs/roles-in-the-selling-partner-api
answered a year ago
