132: The Cloud Pod takes a trip down MemoryDB lane

On The Cloud Pod this week, the results of the AWS Summit prediction draft are in. It was probably worth getting up early for — especially if you’re Jonathan. A big thanks to this week’s sponsors: Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. JumpCloud, which offers a complete platform for identity, access, and device management — no matter where your users and devices are located.  This week’s highlights At the Summit, AWS announces AWS Backup Audit Manager, sealing the prediction draft winner: Congratulations, Jonathan. Outside the Summit, AWS announces MemoryDB for Redis, new split charge rules, and cybersecurity updates. Former AWS leader Charlie Bell is joining Microsoft. What his role will be is unclear, but we speculate that he’ll play some part in improving Azure availability. Top Quotes   “I suspect that certificate-based access to the console is going to be more prevalent. I don’t know of this in Microsoft Azure or Amazon, but I also know that this is one of the things popping up in custom security audits or in documentation that I’ve started to see more and more, which is, how do you control access to this publicly available API?” “This could be an additional $5 billion boost in revenue for Microsoft Office 365, which is important to us because Microsoft 365 is included in the Azure number and reported as one line item. So a $5 billion increase could be a pretty big increase in revenue and growth that Azure could then tout and say, We are finally the biggest, fastest-growing cloud.” General News: Later Days GitHub is saying goodbye to password authorization, but you can still create a personal access token to log in.  Amazon Web Services: We’ve Reached the Summit Redis users in select regions can now use Amazon MemoryDB to boost their application performance with data durability, microsecond read, and single-digit millisecond writes. Unlike ElastiCache, MemoryDB does not require adding a cache from you...