Old Elam: Awan, Shimashki and the Sukkalmahs

Four world-regions

formationDrafted from Cameron, History of Early Iran (1936)

Eleven kings of Awan had already ruled at Susa, most of them barely more than names on a king list, before Puzur-Inshushinak, the twelfth and last of that line, gave the dynasty a real place in recorded history. He served, for a time, as a nominal subject of the Akkadian kings to the west - the same empire that ruled Sumer and Akkad from Agade - but he waited. Only after his overlord Naram-Sin died and gave way to a weaker successor, Sharkalisharri, did Puzur-Inshushinak make his move.

An invasion that reached the enemy's own heartland

Allied with the neighboring land of Zahara, Puzur-Inshushinak invaded Babylonia early in the new king's reign, and his troops were driven back only after penetrating as far as the territory of Opis, deep in the Akkadian heartland. For an Elamite army to reach that far and return home intact was itself remarkable - a genuine military achievement, not a raid that happened to go unpunished. On the strength of it, he was crowned king of Awan and began styling himself, on his own monuments, "King of the Four World-Regions" - a title of universal kingship no earlier Elamite ruler had claimed.

A revival of language alongside a revival of power

Puzur-Inshushinak's own inscriptions show him working on two fronts at once. Some of his dedications are in Akkadian, the diplomatic language of the age, but others carry a parallel text in a still-undeciphered script scholars call proto-Elamite - a deliberate attempt, it appears, to revive a specifically Elamite written tradition alongside Elamite political independence. He rebuilt the temple of the god Inshushinak at Susa with real ceremony, sacrificing daily and stationing musicians at its gate. It was the record of a ruler building a state's identity in more than one register simultaneously - the last king of a fading line who briefly made himself the most powerful sovereign Elam had yet produced.

Musée du Louvre, Paris (Sb 6 / Sb 177) · Cameron, History of Early Iran (1936) · Photograph: Zunkir · CC BY-SA 4.0

The king who took Ur captive

peakDrafted from Cameron, History of Early Iran (1936)

Power passed from Awan to a rival dynasty at Shimashki, and the transition was not gentle. As the Third Dynasty of Ur weakened, two young and vigorous states attacked it from opposite directions at once - Mari from the northwest, Shimashki from the east. An early Shimashki king, Enbiluhhan, pushed down into the Elamite lowlands and briefly occupied Susa itself, only to be met and defeated by Ur's own king, Ibi-Sin, who boasted of overwhelming the land of Awan and the cities of Adamdun and Susa in a single day and capturing Enbiluhhan outright.

Musée du Louvre, Paris · Cameron, History of Early Iran (1936) · Darafsh · CC BY-SA 3.0

A defeat answered by a second, decisive attack

Shimashki was not finished. Enbiluhhan's successor, Kindattu, occupied Susa a second time, and this time his hold was absolute rather than temporary. Where his predecessor had rushed to battle, Kindattu moved carefully - restoring the temple of Inshushinak first, winning over territories that had once answered to Ur, and only then turning his full attention to Ibi-Sin himself. Ur's own king, meanwhile, was fighting a second enemy simultaneously: Ishbi-Erra, a former officer who had broken away in the north and was pressing toward Ur from that direction. Ibi-Sin assured a frightened subordinate that the gods and the Elamites themselves - whom he still, fatally, believed were marching to his own aid - would guarantee his victory.

A captured king, and an empire that did not survive him

The confidence was misplaced. Kindattu's own forces, not allies of Ur's cause, took the city of Ur itself and carried Ibi-Sin off in captivity - the event that ended the Third Dynasty of Ur outright. Ishbi-Erra, denied the prize of Ur's own throne by Kindattu's more decisive strike, instead built an entirely new kingdom of his own at Isin. Kindattu, ruling from Anshan, held both Elam and the recently-conquered Mesopotamian territories in a way no earlier ruler of either Awan or Shimashki ever had - the single most consequential act any king in this long Elamite sequence would accomplish.

The triarchy at Susa

peakDrafted from Cameron, History of Early Iran (1936)

Power in Elam eventually reorganized itself into a system unlike anything the Awan or early Shimashki kings had used: a triarchy of sorts, with a Grand Regent, or sukkalmah, ruling from Susa alongside two subordinate viceroys - one over Elam and Shimashki jointly, one over Susa itself. It was a durable answer to a problem Kindattu's own generation had never had to solve, since Kindattu had simply held Elam and his Mesopotamian conquests together in one hand; the sukkalmah system was built instead for a state that expected to govern itself as three linked offices indefinitely, not as one man's personal holding.

Musée du Louvre, Paris · Cameron, History of Early Iran (1936) · ALFGRN · CC BY-SA 2.0

A succession that ran sideways before it ran down

Succession among the three offices did not run simply from father to son. The pattern that emerges from the sources is collateral, passing between brothers before descending, eventually, to a sister's son - an arrangement that kept the three highest offices in Elam within one extended family across generations without ever depending on any single ruler producing a son who outlived him. Whatever its origins, the system produced real continuity: a line of sukkalmahs governed Elam through this triarchic arrangement for roughly two centuries, a span of stable, documented government longer than either the Awan or the Shimashki line had managed to sustain on its own.

A government legible enough to be named individually

The system's durability is itself the reason a sukkalmah's own reign can be narrated in more than outline at all: unlike the Awan king list that reduces eleven rulers to little more than names, the sukkalmah period produced enough correspondence and enough inscriptions that at least one grand regent, Siwepalarhuppak, is well enough attested to be treated as an individual figure rather than a line in a succession list - a change in the kind of evidence Elam's own government was generating, not merely in how long it lasted.

The overlord both kings called father

peakDrafted from Potts, Cambridge World Archaeology (2016)

Siwepalarhuppak did not merely hold the office of sukkalmah - for a stretch of years in the middle of his reign, he was the most powerful individual ruler in the whole of the Near East, and the evidence for it does not come from Elam's own archive at all. It survives in the diplomatic correspondence of a Mesopotamian kingdom four hundred miles to the west: the royal archive of Mari, on the Euphrates, whose kings maintained a running correspondence with every significant power of their day and, in doing so, incidentally preserved a record of Siwepalarhuppak's own standing that no Elamite source could match.

A kinship vocabulary that was really a hierarchy

Mesopotamian diplomatic correspondence of the period used family terms to encode rank: a king addressed an equal as "brother," a weaker counterpart as "son," and a superior as "father." In the letters that survive from Mari, both Zimri-Lim of Mari and Hammurabi of Babylon address Siwepalarhuppak as father - the position ordinarily reserved for an acknowledged overlord. It is the clearest evidence available that an Elamite sukkalmah, for a time, outranked in practice the two kings who would otherwise be remembered as the leading powers of their own generation in Mesopotamia.

The coalition Siwepalarhuppak built, and the one he lost

Siwepalarhuppak used that standing directly: he brought Mari and Babylon together in an alliance against Eshnunna, a rival Mesopotamian power, and the coalition succeeded - Eshnunna fell within Elam's sphere of influence not long afterward. But an overlord's position built on other kings' cooperation rather than on direct conquest does not survive a shift in what those kings judge to be in their own interest. Hammurabi, who spent decades absorbing his Mesopotamian rivals one at a time including the old kingdom of Larsa itself, did not remain a junior partner for long: within a few years of the Eshnunna campaign he turned against the Elamite coalition that had helped install him as the region's rising power, and Siwepalarhuppak's own moment as the acknowledged senior figure of the whole Mesopotamian and Elamite world passed with it.

What the correspondence actually proves

None of this is visible in Elam's own inscriptions, which is itself worth noting: the clearest evidence of a sukkalmah's real power comes from a foreign archive that happened to survive, in exactly the same way a Kassite king's own reputation survives only through his son's letters to Egypt. Siwepalarhuppak's reign is also the clearest point of contact between Elam's own triarchic government and the Isin-Larsa-Babylon rivalry playing out at the same time in southern Mesopotamia - a reminder that the sukkalmahs governing Elam through these two centuries were not a power operating in isolation, but active participants in exactly the same contest for the region that Gungunum's own secession from Isin had opened generations earlier, and that a chief with an Elamite name would go on to found the dynasty that eventually gave Larsa its own last king.

Claims to greatness from rulers the record barely knows

contractionDrafted from Cameron, History of Early Iran (1936)

The system that had produced a sukkalmah powerful enough to be addressed as an elder by the kings of Babylon and Mari did not stay that strong. Toward the later part of the sukkalmah period the sources grow thin, and the claims made in what does survive grow correspondingly grand. A number of later rulers style themselves descendants of the great sukkalmah Shilhaha, but the scribes who copied their inscriptions, working centuries afterward, knew one such king only as "a son of Lanku" - an otherwise unknown figure whose actual place in the succession is impossible to establish.

Musée du Louvre, Paris · Cameron, History of Early Iran (1936) · Francesco Bini · CC BY-SA 4.0

Reaching for a name when the specifics run out

Reaching for a famous ancestor's name while the documented specifics grow vaguer is, historically, often exactly what a weakening state does - a government that had once produced enough correspondence to survive independently in a foreign archive at Mari was, within a generation or two of Siwepalarhuppak's own reign, no longer generating the kind of record that lets a modern history narrate individual kings at all. The triarchic system itself may well have persisted in some form; what did not persist was the documentary richness that had made the earlier sukkalmahs legible as individuals rather than as names in a genealogical claim nobody could any longer verify.

A history that fades rather than ends

endDrafted from Cameron, History of Early Iran (1936)

There is no recorded battle that ends this long Elamite sequence, no named conqueror, no captured king. The sources themselves simply stop providing usable information at a certain point - by around 1750 BC, in the words of the record consulted here, Elam "fades almost entirely from our view."

What the silence does and does not mean

The fade is not evidence that Elamite kingship itself stopped, only that the documentation of it did. Nothing in the record describes a foreign conquest, an internal collapse, or even a disputed succession of the kind that ends other Elamite dynasties in this account; the triarchic system built around Susa, Elam-and-Shimashki, and a collateral sukkalmah succession may well have continued to function for some time after the last inscription this source can date. What changed was the world outside Elam's own borders rather than anything demonstrably internal to it: the Babylonian correspondents who had once addressed a sukkalmah as an elder stopped writing letters that survived, and without that outside archive to supplement Elam's own thin epigraphic record, the individual kings of the kingdom's final decades simply stopped being visible to history at all.

A gap, not an ending

What filled the two and a half centuries between that silence and the next clearly attested Elamite kingdom is not recoverable from this source; only that the identity persisted long enough, in some form, for a later dynasty to pick up the old traditions of Susa and Anshan as though they had never fully stopped.