Vogels did not mention the fact that the CNBC article — which was quoted by iTWire among other publications — had actually said that the problem had to do with the process of migration from Oracle's database to PostgreSQL, an open-source database sold to Amazon by a provider named Aurora.
In a tweet, to which he had appended a statement, Vogels said the company's fulfilment centres had migrated 92% of its databases from Oracle to PostgreSQL "with better availability, less bugs and patches, less troubleshooting and less cost".
CNBC said 13 warehouses had moved from Oracle to PostgreSQL before Prime Day. It made no mention of AWS in its report.
The CNBC report was based on internal Amazon documents running to 25 pages which showed that the retail giant's technical staff struggled to find out the root cause of the issues on Prime Day.
Vogels said the website issues had resulted from a problem in the Amazon retail software stack. He did not specify which part of the stack was affected.
The internal documents that CNBC cited were said to have been "apparently obtained" and, according to Vogels, detailed "a completely unrelated issue in a single fulfilment centre (out of more than 185 worldwide)".
This had "led to the slowing of processing in the fulfilment operations and a slight delay in shipping of products from that facility alone", Vogels claimed, not giving the location of the facility in question. CNBC had said the Prime Day issues had arisen at a time when Amazon had an issue at one of its bigger warehouses in Ohio.
Vogels said: "There was never an outage at the facility, and the issue only resulted in delaying shipping of about 1% of packages for a short period of time (unnoticeable to customers)."
CNBC had said that 15,000 packages had been delayed as per the internal Amazon report and about US$90,000 in labour costs wasted.
It did not claim that there was an outage at the Ohio facility in the story, though the headline did make this claim. But the Amazon website did go down as per a report in the The Verge which said it had crashed. Such a failure is commonly referred to as an outage.
Vogels said the application in question — which he did not name — "accidentally created an excessive number of savepoints, despite the team knowing that Aurora and Oracle handle savepoints differently".
This appears to tally with the CNBC report which had said that the Prime Day issue was connected to the fact that Oracle and PostgreSQL handle savepoints differently.
"This created a temporary situation where the database was very slow and the application experienced intermittent timeouts," Vogels wrote.
The internal Amazon documents said the "degradation resulted in lags and complete outages".
Said Vogels: "The problem was quickly diagnosed and completely resolved by simply removing the unnecessary savepoints that had been inadvertently left in the retail application. No changes were required in Aurora."
CNBC said Amazon had failed to come up with a contingency plan in the event of any error in its replacement database. Vogels made no mention of this in his statement.