Every AWS IAM action string has the form service:ActionName — the part before the colon is a literal service prefix, not an abbreviation you have to guess at. IAM Action-to-Service Mapper takes one or more action strings and tells you which AWS service each prefix belongs to, using a curated reference table of common service prefixes and their plain-English names.
The logic is intentionally simple and fully deterministic: split the action string at its first colon, take the substring before it, and look that substring up in a table of known prefixes. There is no fuzzy matching, no guessing, and no AI involved — either the prefix is in the table and you get the service name, or it is not and the tool tells you plainly that the prefix was not found in this reference table.
This is useful when you are staring at a policy statement with an unfamiliar action and want to quickly confirm which service it targets before looking up the action itself in AWS documentation, or when auditing a policy that lists actions from several services and you want a quick per-line breakdown of what each one touches.
The reference table covers roughly 60 of the most commonly seen prefixes across compute, storage, database, networking, security, and developer-tooling services. AWS has well over 300 services in total, so a prefix not appearing in this table is not necessarily invalid — it simply is not part of this curated subset. Consult the AWS Service Authorization Reference for the complete, authoritative list of every service prefix AWS defines.