Conferences, tours and summits across AWS, Microsoft Azure and Google Cloud. Every entry links to the cloud’s own page — nothing here is second-hand — and every link is re-read from that page each morning.
Where a cloud has announced an event but not its dates, it is listed without them. A date nobody published is worse than no date: people book flights around these.
Where a cloud has announced an event but not its dates, it is listed without them. A date nobody published is worse than no date: people book flights around these.
Where this comes from
Every event on this page is read from one of these and links back to the cloud’s own page for it. Nothing is taken from a news site, a newsletter or a summary, and no date is inferred.
How it stays current. Two scheduled jobs run every morning, and neither needs anybody to remember them. At 05:40 UTC the clouds’ directories are re-imported, so an event they add or move appears here the same day. At 06:20 UTC every link on this page is opened in a real browser and has to still be the page it claims to be — a dead or redirected link fails the run rather than sitting here looking fine — and the list is reconciled against what the clouds are advertising, so an event that exists and is missing here fails too. That second question is the one a valid-looking page cannot answer about itself.
34 of the 37 entries come from a machine-readable directory and update without anyone touching them. The other 3 are the big announcements — re:Invent, Ignite, Next — which the clouds publish as prose rather than as data; those are read by hand, carry a note saying where the wording came from, and are never given a date the cloud has not published.