Podcasts about aws summit

Arthur Goldstuck, CEO of Worldwide Worx and Editor-in-Chief of Gadget.co.za. joins John Maytham to report back from the AWS Summit in Sandton, where South Africa’s major banks and the JSE revealed how they are using cloud computing to drive innovation and stay globally competitive. He also spotlights the Huawei Pura80 Pro, a flagship smartphone with a 1-inch Ultra Lighting sensor and variable aperture for professional-level photography. And Arthur also shares details about Zoho, India’s answer to Microsoft Office, which is expanding its South African footprint, and gives crucial advice on preparing for Microsoft’s end of support for Windows 10 in October 2025, warning of the looming “Win10apocalypse.” Good Morning Cape Town with Lester Kiewit is a podcast of the CapeTalk breakfast show. This programme is your authentic Cape Town wake-up call. Good Morning Cape Town with Lester Kiewit is informative, enlightening and accessible. The team’s ability to spot & share relevant and unusual stories make the programme inclusive and thought-provoking. Don’t miss the popular World View feature at 7:45am daily. Listen out for #LesterInYourLounge which is an outside broadcast – from the home of a listener in a different part of Cape Town - on the first Wednesday of every month. This show introduces you to interesting Capetonians as well as their favourite communities, habits, local personalities and neighbourhood news. Thank you for listening to a podcast from Good Morning Cape Town with Lester Kiewit. Listen live on Primedia+ weekdays between 06:00 and 09:00 (SA Time) to Good Morning CapeTalk with Lester Kiewit broadcast on CapeTalk https://buff.ly/NnFM3Nk For more from the show go to https://buff.ly/xGkqLbT or find all the catch-up podcasts here https://buff.ly/f9Eeb7i Subscribe to the CapeTalk Daily and Weekly Newsletters https://buff.ly/sbvVZD5 Follow us on social media CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/CapeTalk CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

Arthur Goldstuck speaks to Lester Kiewit about the latest in tech. This week, he connects with Sukhiba founder and CEO Ananth Gudipati, virtually from Nairobi, and new SA country manager Andrew Pillay in Sandton, to explore how WhatsApp Commerce is transforming the way we buy and sell. In Gadget of the Week, Arthur argues it’s time South Africa updates its decade-old drone laws to unlock new possibilities for logistics and mobility (read more here). He also highlights the AWS Summit in Sandton, where the future of cloud computing will be defined, and shares safety tips for parents whose kids want to start blogging (read here). Good Morning Cape Town with Lester Kiewit is a podcast of the CapeTalk breakfast show. This programme is your authentic Cape Town wake-up call. Good Morning Cape Town with Lester Kiewit is informative, enlightening and accessible. The team’s ability to spot & share relevant and unusual stories make the programme inclusive and thought-provoking. Don’t miss the popular World View feature at 7:45am daily. Listen out for #LesterInYourLounge which is an outside broadcast – from the home of a listener in a different part of Cape Town - on the first Wednesday of every month. This show introduces you to interesting Capetonians as well as their favourite communities, habits, local personalities and neighbourhood news. Thank you for listening to a podcast from Good Morning Cape Town with Lester Kiewit. Listen live on Primedia+ weekdays between 06:00 and 09:00 (SA Time) to Good Morning CapeTalk with Lester Kiewit broadcast on CapeTalk https://buff.ly/NnFM3Nk For more from the show go to https://buff.ly/xGkqLbT or find all the catch-up podcasts here https://buff.ly/f9Eeb7i Subscribe to the CapeTalk Daily and Weekly Newsletters https://buff.ly/sbvVZD5 Follow us on social media CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/CapeTalk CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

In dieser Episode tauchen wir ein in die Welt der Frauen im Cloud und Techbereich: darüber wie AWS Women's User Groups, die Tech-Landschaft bereichern, die Bedeutung der Women of the Cloud Stage auf dem AWS Summit, und auch wieso Mentoren und Sponsoren für Frauen im Techbereich so wichtig sind.  AWS Cloud Horizonte Host Michelle Mei-Li Pfister, Solutions Architect bei AWS, spricht mit drei inspirierenden Gästen: Linda Mohamed, AWS Hero und Organisatorin der AWS Women User Group Wien, Anariina Komljenovic, Executive Vice President bei valantic, und Rebekka Mossal, Organisatorin der Women of the Cloud Stage beim AWS Summit Hamburg. Wir sprechen darüber wieso es wichtig ist solche Räume für Frauen zu schaffen, teilen inspirierende Erfolgsgeschichten und geben praktische Tipps, wie Interessierte Teil dieser wachsenden Bewegung werden können.  Kernthemen der Episode: Die Rolle von AWS Women's User Groups und anderen Women Communities für den Karriereeinstieg Wie wichtig Mentoring und Sponsoring sind  Praktische Tipps für den Karrierestart in Tech Allyship und wie man als Unterstützer*in aktiv werden kann Key Learnings: Communities bieten sicheren Raum zum Experimentieren und Wachsen Erfolgreiche Karrieren brauchen sowohl Mentoren als auch Sponsoren Progress over Perfection: Mut zum Imperfekten ist wichtiger als Perfektion Netzwerke frühzeitig aufbauen und pflegen Die Tech-Branche bietet vielfältige Karrierewege jenseits des Codings Über die Gäste: Linda Mohamed: AWS Hero und Organisatorin der AWS Women User Group Wien Annariina Komljenovic: Executive Vice President bei valantic Rebekka Mossal: Organisatorin der Women of the Cloud Stage und Sales Managerin bei AWS Links: AWS Women's User Group Vienna AWS Women's User Group Munich AWS Women's User Group Berlin Women of the Cloud Stage beim AWS Summit Hamburg  #86: Allyship und Vielfalt bei AWS  AWS Cloud Horizonte ist der offizielle deutschsprachige AWS Podcast.

How are companies really using AI? And is it truly working? AWS Vice President Francessca Vasquez joins the GeekWire Podcast to talk about what companies are actually doing with AI today, and what's holding them back. We discuss real-world deployments, lessons from AWS customers across industries, and the challenges and opportunities in scaling generative and agentic AI. Related Stories and Links: Amazon gives $100M boost to AWS Generative AI Innovation Center, betting on agentic AI Gartner: Over 40% of Agentic AI Projects Will Be Canceled by End of 2027 AWS News Blog: Top announcements of the AWS Summit in New York, 2025 Amazon cuts hundreds of AWS cloud jobs after strategic review, says AI wasn’t the main factor Meta snags Seattle startup co-founder for Zuckerberg’s elite superintelligence team With GeekWire co-founder Todd Bishop. Edited by Curt Milton.See omnystudio.com/listener for privacy information.

Shannon Ayers from Lawrence Livermore National Lab unveiled a groundbreaking generative AI tool to boost operational efficiency at the National Ignition Facility. The tool leverages 22 years of institutional data, analyzing over 98,000 problem logs, to provide instant troubleshooting guidance for operators. By creating a decision-tree system, the lab addresses critical challenges of aging infrastructure and knowledge transfer between retiring and emerging scientific workforces. The AI-powered platform represents a strategic approach to accelerating scientific research, enabling operators to quickly resolve complex technical issues and maintain continuous data production. The tool aims to empower the next generation of scientists by providing rapid access to decades of accumulated institutional knowledge. This approach not only improves immediate operational capabilities but also supports the broader national security and fusion energy research objectives of the laboratory. By transforming how technical knowledge is captured, shared and applied, Lawrence Livermore National Lab is positioning itself at the forefront of technological innovation, demonstrating how AI can revolutionize scientific research and national technological capabilities.

Technology and software development can take years to field capabilities that may no longer meet mission needs once they reach the finish line. Some department compliance practices can add 12-18 months for authorization. At the AWS Summit in Washington, D.C., Marine Corps Community Services Digital Program Manager David Raley said that his office is accelerating the development and approval processes for mission capability. Raley highlighted solutions like AWS GovCloud and a certified DevSecOps platform that help reduce authorization times from a year to 15 minutes. Raley also talked about the ways DOD is advancing zero trust implementation and security in cloud-native environments.

The Idaho National Laboratory is working on a suite of artificial intelligence capabilities to enhance nuclear energy research. During an interview at AWS Summit in Washington, D.C., the lab's Scientific Computing Division Director Chris Ritter discussed how the organization is using generative AI to address complex scientific challenges across domains like reactor design and operations. The lab successfully created a digital twin of an aging reactor, streaming real-time data to the cloud and using multiple machine-learning models to predict operational parameters. Ritter emphasized the broader implications of AI integration in these areas, like how “AI jams” engage scientists and lab directors to explore it. The approach represents a comprehensive strategy to not only advance scientific research, but also prepare the workforce for an AI-driven future.

High-performance computing (HPC) systems provide fundamental computing infrastructure for government and industry. Security is critical for these systems that play a pivotal role in economic competitiveness and scientific discovery. At the AWS Summit in Washington, D.C., National Institute of Standards and Technology (NIST) Computer Scientist Yang Guo said that efficient encryption and zone-based reference architectures can enhance HPC security without impacting performance. Guo, who leads the NIST HPC Security Working Group, said that collaboration and knowledge sharing can help buttress HPC security, even in cloud environments. Guo also discussed HPC focus areas like confidential computing, zero trust, supply chain security and integrating AI for early detection of anomalies.

Quest'anno l'AWS Summit di Milano si terrà il 18 giugno a Fiera Milano Rho. In questo episodio Massimiliano Galli (Head of Marketing AWS Italia) ci racconterà come funziona il Summit, quali sono i contenuti, le attività in programma, le tracce e tutte le cose interessanti che potrete trovare. Ci vediamo al Summit!Link utili:- AWS Summit Milano

Send us a textIn this episode, we dive deep into the world of digital transformation and cloud-native architecture with Madoc Batters, Head of Cloud, Network and IT Security at Warner Hotels. Madoc shares his remarkable journey from washing 100 cars at age 11 to buy his first ZX81 computer to leading enterprise-scale cloud migrations. We explore the challenges of organizational culture change, the bold decision to migrate their most complex system first, and the importance of shifting left with security and FinOps practices. Madoc also shares insights on modern networking solutions like Alkira, the role of AI in transformation, and how his ultra-marathon mindset (including a 105-mile run) applies to pushing through digital transformation challenges. Whether you're starting your cloud journey or looking to accelerate your transformation efforts, this episode is packed with practical wisdom and inspiring leadership insights.Where to Find MadocLinkedIn: https://www.linkedin.com/in/madoc-batters-aws-machinelearning/Sessionize: https://sessionize.com/madoc-batters/Show LinksWarner Hotels: https://www.warnerhotels.co.uk/Alkira: https://www.alkira.com/AWS Bedrock: https://aws.amazon.com/bedrock/HashiCorp: https://www.hashicorp.com/AWS Summit: https://aws.amazon.com/events/summits/FinOpsX: https://www.finops.org/community/finopsx/ZX81 Computer: https://en.wikipedia.org/wiki/ZX81Follow, Like, and Subscribe!Podcast: https://www.thecloudgambit.com/YouTube: https://www.youtube.com/@TheCloudGambitLinkedIn: https://www.linkedin.com/company/thecloudgambitTwitter: https://twitter.com/TheCloudGambitTikTok: https://www.tiktok.com/@thecloudgambit

What does it take to turn a moment of frustration into a global mission to tackle waste? At the AWS Summit in London, I sat down with Tessa Clarke, co-founder and CEO of Olio, to explore how a single idea born on a snowy Swiss street evolved into a powerful tech platform reshaping how communities think about consumption, sharing, and sustainability. Tessa shared her personal journey, from growing up on a farm where food waste was unthinkable to climbing the corporate ladder before walking away to co-found Olio. That decision came after she was told to throw away perfectly good food while moving house, a moment that sparked an idea and a deeper calling. What followed was years of research, a grassroots WhatsApp experiment, and ultimately, the creation of an app that now connects millions of users worldwide. In our conversation, we explored how Olio uses technology to drive real-world change. Tessa explained how AWS has been a foundational partner since day one, helping Olio scale sustainably without compromising its values. She also gave an inside look at how AI is integrated thoughtfully across their operations, from assisting users in listing items faster to detecting potentially unsafe or inappropriate listings before they go live. What stood out is how intentional Tessa and her team have been in making AI serve the mission, not distract from it. Whether it's reducing friction within communities or using automation to offset operational challenges, every tech choice is aligned with their goal: to build a waste-free world. We also discussed how AI is helping them break the traditional link between headcount and impact, paving the way toward profitability while staying people-focused. As Olio aims to reach a billion users by 2030, this episode is a reminder of what happens when purpose and technology meet. Tessa's story offers a compelling blueprint for founders, technologists, and anyone looking to use digital tools to solve human problems. How can a simple act of sharing create ripple effects across the world, and what role will technology play in scaling that vision responsibly?

In dieser Episode sprechen wir mit zwei AWS Heroes über den AWS Summit Hamburg am 5. Juni 2025. Markus Ostertag und Thorsten Höger geben als langjährige Summit-Veteranen einen exklusiven Einblick in das, was Besucher erwartet und teilen ihre persönlichen Highlights und Networking-Tipps. Kernthemen der Episode: - Warum der Summit 2025 in Hamburg stattfindet - Content-Highlights: Über 100 Sessions zu Gen AI, Cloud Transformation und mehr - Die AWS Community Lounge als wichtiger Treffpunkt - Das neue AWS for Software and Technology Loft - Women of the Cloud Stage mit erweitertem Programm - AWS HouseWarming am Vortag mit über 60 Hands-on Workshops - Networking-Möglichkeiten und Festival-Atmosphäre Summit-Tipps für Neulinge: - Vorab die Agenda durchgehen und interessante Sessions markieren - Flexibel bleiben und nicht zu strikt planen - auch spontane Entdeckungen zulassen - Die Community Lounge als erste Anlaufstelle nutzen - hier gibt es praxisnahe Erfahrungsberichte - Aktiv das Gespräch suchen, z.B. beim Mittagessen oder an den Expo-Ständen - AWS Announcements der letzten Wochen als Gesprächseinstieg nutzen - "Walk the Summit" Format für Frauen in Tech nutzen, um gemeinsam die Veranstaltung zu erkunden - Balance zwischen Sessions, Expo und Networking finden - Genug Zeit für spontane Gespräche einplanen Die AWS Community Lounge - Highlights: - Eigene Stage mit Community-kuratiertem Programm "von der Community für die Community" - Praxisnahe Sessions mit ehrlichen Einblicken in Herausforderungen und Lösungen  - Hands-on Erfahrungsberichte von AWS-Anwendern - Offener Networking-Bereich zum Austausch mit erfahrenen Community-Mitgliedern - Tiefgehende technische Diskussionen im "Maschinenraum" - Idealer Startpunkt für Summit-Neulinge zum Kontakte knüpfen - Direkte Gespräche mit Vortragenden und Community-Experten - 7 Slots mit ausgewählten Community-Speakern Besondere Highlights: - Keynote mit Stefan Höchbauer (AWS), Dr. Steffen Merkel (DFL) und Donja Florence-Aimer (Hapag Lloyd) - Kundenvorträge von BMW, Mercedes-Benz, Trade Republic, E.ON u.v.v.v.m. - Interaktive Bereiche wie AI Escape Room und SaaS Builders' Showdown - Riesenrad, DJs und Networking Reception mit Live-Musik Links: - ‼️ AWS Summit Hamburg Registrierung ‼️ - AWS Summit Hamburg Agenda - AWS Housewarming Anmeldung - AWS for Software and Technology Stage Programm - AWS x OMR Reviews SaaS Leaders Breakfast - AWS Community DACH Über die Gäste: - Markus Ostertag ist Chief AWS Technologist bei ADESO und seit 2016 AWS Hero - Thorsten Höger ist selbstständiger Cloud-Berater für regulierte Kunden und seit 2017 AWS Hero Hosts: - Jana Kupfer (AWS) - Michelle Mei-Li Pfister (AWS) AWS Cloud Horizonte ist der offizielle deutschsprachige AWS Podcast.

What happens when access to advanced AI models is no longer the real differentiator, and the true advantage lies in how businesses leverage their own data? At the AWS Summit in London, I sat down with Rahul Pathak, Vice President of Data and AI Go-to-Market at AWS, to unpack this question and explore how organisations are moving beyond experimentation and into large-scale generative AI adoption. Recorded live on the show floor, this conversation explores how AWS is supporting customers at every layer of their AI journey. From custom silicon innovations like Trainium and Inferentia to scalable services like Bedrock, Q Developer, and SageMaker, AWS is giving businesses the infrastructure, tools, and flexibility to innovate with confidence. Rahul shared how leading organisations such as BT Group, SAP, and Lonely Planet are already applying these tools to reduce costs, speed up development cycles, and deliver tailored experiences that would have been unthinkable just a few years ago. A key theme that emerged in our discussion is that data, not just models, is the true foundation of effective AI. Rahul explained why unifying data across silos is critical and how AWS is helping companies create more intelligent applications by connecting what they uniquely know about their business to powerful AI capabilities. We also addressed the operational realities of AI deployment. From moving proof-of-concept projects into production to meeting the growing demand for responsible AI, the challenges are shifting. Organisations are now focused on trust, security, transparency, and measurable value. If you're leading digital transformation and wondering how to scale AI solutions that deliver on business outcomes, this episode provides practical insight from someone at the center of the industry. How will your business stand out in a world where every company has access to AI models, but only a few know how to apply them with purpose?

Amid the buzz of the AWS Summit in London, I sat down with Eiso Kant, the CTO and Co-Founder of Poolside, to explore how his team is reshaping the future of software development through AI. This conversation was recorded right on the show floor inside a surprisingly sleek podcast booth at the ExCel, where Eiso unpacked what sets Poolside apart in a space many claim to be in but few truly build for. Poolside is not just another AI company. It's one of a handful globally that is actually training foundation models from the ground up. While most firms are chasing general-purpose AI, Poolside has chosen a different path. They focus solely on empowering software developers inside high-consequence environments, such as banking, defense, and major global retailers. These are systems where precision and security matter, and where AI can drive measurable gains in productivity and reliability. What struck me during this discussion is how deliberately Poolside has been built for enterprise use from the start. Their model doesn't just live in the cloud. It is designed to live within the customer's own infrastructure, whether that's in their private AWS environment or even on-prem. This focus on data privacy, security, and customizability is helping Poolside win trust where it counts most. And the partnership with AWS takes this a step further, making it easier for enterprises to deploy Poolside's AI within existing cloud frameworks while meeting strict governance requirements. Eiso explained that Poolside doesn't just throw larger models at problems. Instead, they use reinforcement learning from code execution, training on millions of real codebases and test suites. This approach helps the model go beyond autocomplete and simple bug fixes. It's now stepping into longer, more complex tasks, nudging us closer to a future where AI could serve as a true teammate for software engineers. We also tackled one of the most important discussions in AI today: whether this is a cost-cutting tool or a productivity multiplier. Eiso didn't dodge the nuance. While some may use AI to reduce headcount, Poolside's focus is on enabling companies to build more, ship faster, and innovate with greater speed. That shift is not about replacing people. It's about creating leverage for development teams under pressure to deliver more in less time. If you're a CTO, CIO, or engineering leader, this episode is packed with practical insights. Whether it's understanding the ROI of AI-assisted development, the importance of retaining control of your own models, or how to think about enterprise-grade security in the age of LLMs, there's a lot here to digest. So how should we really be thinking about AI in the enterprise? Is it a partner, a tool, or the beginning of an entirely new workforce paradigm? Tune in to find out.

In dieser Episode von Cloud Horizonte sprechen Oliver und Pavel auf dem AWS Summit in Berlin mit Frank Alsmann (VHV Versicherung) und Philipp Richter (Public Cloud Group) über die Cloud-Transformation der VHV. Die VHV migriert Anwendungen von On-Premise in die AWS Cloud – mit Fokus auf Serverless-Technologien wie AWS Lambda. Wir diskutieren die Herausforderungen einer solchen Migration, von Sicherheit und Kostenoptimierung bis hin zur Modernisierung des einer konkreten Anwendung, des Tarifrechners. Es geht nicht nur um Technik: Die Cloud-Reise ist auch eine kulturelle Veränderung. Wie nimmt man Mitarbeitende mit? Welche Rolle spielen Schulungen, Compliance und FinOps? Erfahren Sie, warum Cloud nicht nur Effizienz bringt, sondern auch neue Denkweisen in Unternehmen etabliert. Wir sprechen über Lessons Learned, den langfristigen Wandel in der IT und wie Unternehmen wie die VHV sich für die Zukunft aufstellen.

In der neuesten Episode des AWS Cloud Horizonte Podcasts erleben Sie ein faszinierendes Gespräch zwischen Host Heinrich Nikonow und Siggi Schallenmüller, Head of Digital Innovation EMEA bei Amazon, live vom AWS Summit in Berlin. Tauchen Sie ein in die Geheimnisse, die Amazon zu einem Vorreiter in der Innovationswelt gemacht haben. Erfahren Sie, wie die einzigartige „Day 1 Culture“ von Amazon nicht nur den Innovationsgeist des Unternehmens befeuert, sondern auch als Vorbild für die gesamte Branche dient. Siggi Schallenmüller erläutert, wie das Prinzip „Working Backwards“ den Entwicklungsprozess bei Amazon revolutioniert hat und warum diese Methoden für Unternehmen auf der ganzen Welt von unschätzbarem Wert sind. Highlights dieser Episode:

In der aktuellen Episode des AWS Cloud Horizonte Podcasts begrüßt unser Host Heinrich Nikonow den CTO und Mitbegründer von Sereact, Marc Tuscher, live vom AWS Summit in Berlin. Gemeinsam tauchen sie tief in die Welt der Logistik ein und diskutieren die neuesten Entwicklungen in den Bereichen Digitalisierung und Robotik. Erfahren Sie, wie Sereact, eine Ausgründung des Instituts für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) der Universität Stuttgart, die Logistikbranche revolutioniert. Sereact entwickelt KI-gestützte Software für intelligente Robotik, die den Pick-and-Pack-Prozess in Warenlagern und Produktionsstätten optimiert.  Marc Tuscher erläutert, wie Sereacts innovative Lösungen in Zusammenarbeit mit AWS umgesetzt werden und wie die Integration der KI-Robotik-Lösung innerhalb eines einzigen Tages zu sofortigen Kosteneinsparungen von bis zu 77 % pro Kommissionierung führt. Ein weiteres Highlight: Die Pick-Software von Sereact ist flexibel und bewältigt mühelos wechselnde Produktsortimente. Hören Sie rein, um zu erfahren, wie Sereact und AWS gemeinsam die Zukunft der Logistik gestalten und welche Herausforderungen und Chancen die Digitalisierung und Robotik in diesem Bereich mit sich bringen.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 29/06 a 12/07.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 29/06 a 12/07.

We are live for episode 29 of the Hot Desk Podcast with Melody Brue and Robert Kramer.   IBM at Wimbledon  https://www.linkedin.com/posts/melodybrue_ibm-serves-new-generative-ai-features-at-activity-7215655729595080704-QxN7?utm_source=share&utm_medium=member_desktop https://www.ibm.com/sports/wimbledon   AWS Summit 2024 NYC AWS Democratizing Data and AI https://aws.amazon.com/blogs/aws/top-announcements-of-the-aws-summit-in-new-york-2024-2/ https://aws.amazon.com/blogs/machine-learning/empowering-everyone-with-genai-to-rapidly-build-customize-and-deploy-apps-securely-highlights-from-the-aws-new-york-summit https://www2.deloitte.com/us/en/pages/about-deloitte/articles/press-releases/deloitte-launches-gen-ai-accelerator-program-with-aws.html#   Avaya CEO Transition  https://www.avaya.com/en/about-avaya/newsroom/pr-us-240710/    Zoho Apptics https://www.zoho.com/blog/apptics/introducing-zoho-apptics-application-analytics-solution.html    What's coming up?  Robert Mel   Disclaimer: This show is for information and entertainment purposes only. While we will discuss publicly traded companies on this show. The contents of this show should not be taken as investment advice.

***Please note this episode contains background noise and distortion from the AWS Summit *** Mark Tate and Luther King are reporting live from day two of the AWS Summit in Washington, DC, sharing the excitement and opportunities of the event, including sessions on cloud security and serverless computing. They highlight the evolution of cloud technology and its impact, emphasizing the importance of adapting to innovations like generative AI. The hosts also discuss the ongoing Olympic track and field events, celebrating athletes like Corey Richardson and Noah Lyles. They shift gears to address mental health awareness and PTSD, stressing the importance of support and resources for veterans. They encourage those struggling to seek help, highlighting the significance of addressing mental health stigma in the military. Luther and Mark also cover health and wellness, discussing the benefits of fitness and nutrition in coping with stress.

***Please note this episode contains some background noise and distortion from the AWS Summit in the background*** In this episode, hosts Luther King and Mark Tate report live from the AWS Summit in Washington, DC. They kick off the podcast by discussing AWS's commitment to providing free AI skills training for millions globally and the excitement surrounding the summit. Both hosts share their experiences from various sessions, highlighting the keynote speech on generative AI and a surprising presentation by a representative from the Central Intelligence Agency on the long-term use of AI in their operations. They emphasize the importance of adapting and learning about new technologies to stay relevant. The hosts delve into Mark Tate's recently published book, "Sprint to the Mountaintop," discussing its core themes and offering listeners a deeper look into its contents, exploring key chapters. The book can be found on Amazon at https://a.co/d/076xyJz3

Willkommen zur neuesten Episode von Cloud Horizonte, dem offiziellen deutschen AWS Podcast! In dieser spannenden Folge tauchen wir tief in die Welt der IT-Talente ein und beleuchten, welche Fähigkeiten und Profile in der Zukunft gefragt sein werden. Unsere Gastgeber sind Heinrich Nikonow von AWS und Basti Meissner, CEO von Nijodex. Themen dieser Folge: - Zukunft der IT-Talente: Welche Fähigkeiten und Qualifikationen werden zukünftig in der IT-Branche besonders gefragt sein? - Team Staffing: Wie stellt man das ideale Team für IT-Projekte zusammen? Welche Rollen und Kompetenzen sind unerlässlich? - Amazon's Hiring-Prozess: Ein exklusiver Einblick in den Einstellungsprozess bei Amazon – von der Bewerbung bis zum Interview. - Mitarbeiterbindung: Strategien und Best Practices, um sicherzustellen, dass die besten Talente langfristig im Team bleiben. Diese Episode wurde live auf dem AWS Summit in Berlin aufgenommen und bietet wertvolle Einblicke sowohl für Führungskräfte als auch für IT-Profis, die sich für effektives Teammanagement und die zukünftigen Anforderungen der Branche interessieren. Hören Sie jetzt rein und erfahren Sie, wie Sie Ihr Team optimal aufstellen und die besten Talente der IT-Branche für sich gewinnen und halten können!

In an interview at the AWS Summit, Pacific Northwest National Laboratory (PNNL) Chief Scientist for AI Court Corley and Director of the Center for Cloud Computing Scott Godwin discussed their efforts to enhance research through AI and cloud computing. They emphasized providing foundational compute capabilities and access to cloud services for Energy Department researchers addressing critical issues like sustainable energy and national security. They also highlighted the rapid evolution of AI tools and the importance of data management across different domains. Both stressed the need for cultural adaptation within the scientific community to embrace new technologies while also ensuring they enable reliable and validated results.

At AWS Summit in Washington DC, Nutanix Senior Director of US Federal Greg O'Connell discussed how agencies can ensure seamless data migration and app mobility, leverage generative AI and incorporate security. He equated today's rapid growth in modern applications to the impact of the browser, as the “killer app” of the internet era of the 1990s. With projections of 750 million new apps by 2026, he said agencies face challenges to incorporate more cloud and edge computing that would handle increased data processing and to develop more sophisticated security measures. Additionally, he addressed the impact of industry acquisitions on vendor dependency, stressing the importance of flexibility and freedom of choice in IT infrastructure to adapt to changing needs and avoid lock-in with a single provider.

The Air Force Sustainment Center is modernizing supply chain and logistics operations with cloud. Having an efficiently running supply chain and manufacturing operations for supplies and weapons systems is critical to national security. Leaders from the center, John York and Josh Thompson, highlight at AWS Summit some of their priorities around cloud and hybrid cloud. They also detail how developments in the Technology Hosting Environment for NextGen Automation (ATHENA) program is driving cost savings and improving insight into disparate sensors and data hubs for the service.

Amazon Web Services (AWS) announced the AWS Public Sector Generative Artificial Intelligence (AI) Impact Initiative. The two-year, $50 million investment is designed to help public sector organisations - and those that directly support their technology needs - to accelerate innovation in support of critical missions using AWS generative AI services and infrastructure, such as Amazon Bedrock, Amazon Q, Amazon SageMaker, AWS HealthScribe, AWS Trainium, and AWS Inferentia. As part of this initiative, AWS is committing up to $50 million in AWS Promotional Credits, training, and technical expertise across generative AI projects. Credit issuance determinations will be based on a variety of factors, including but not limited to the customer's experience developing new technology solutions, the maturity of the project idea, evidence of future solution adoption, and the customer's breadth of generative AI skills. The Impact Initiative is open to new or existing AWS Worldwide Public Sector customers and partners from enterprises worldwide who are building generative AI solutions to help solve society's most pressing challenges. Across the public sector, leaders are seeking to leverage generative AI to become more efficient and agile. However, public sector organisations face several challenges such as optimising resources, adapting to changing needs, improving patient care, personalising the education experience, and strengthening security. To respond to these challenges, AWS is committed to helping public sector organisations unlock the potential of generative AI and other cloud-based technologies to positively impact society. This global initiative is open from June 26, 2024 through June 30, 2026. Benefits and resources will include: Tailored training: Check out the latest trainings to help you achieve your go-to-market goals and business needs. Generative AI Innovation Center expertise: Ideate, identify, and implement generative AI solutions securely with guidance from the Generative AI Innovation Center. Technical support: Learn from AWS technical experts and tutorials to optimize your generative AI build with Well-Architected Framework. Networking and free builder sessions: Access to registration for no-cost AWS Summit events around the world. Global thought leadership opportunities: Showcase your AWS Generative AI Impact Initiative success stories with AWS marketing efforts. The AWS Public Sector Generative AI Impact Initiative builds on our ongoing commitment to the safe, secure, and responsible development of AI technology. For example, AWS is a contributing partner to the National Science Foundation's National Artificial Intelligence Research Resource (NAIRR), which provides U.S.-based researchers and educators access to advanced computing, datasets, models, software, training, and user support for AI research. Additionally, Amazon is a member of the U.S. Artificial Intelligence Safety Institute Consortium, established by the National Institute of Standards and Technology, and is contributing $5 million to enable the development of tools and methodologies that organisations can use to evaluate the safety of their foundation models. AWS is also committed to supporting initiatives like the AI for Changemakers Accelerator program, led by Tech To The Rescue, which includes AWS Chief Technology Officer Werner Vogels' Now Go Build CTO Fellowship program. To learn more about the Impact Initiative, visit https://aws.amazon.com/generative-ai-impact-initiative. See more stories here.

The U.S. Army is prioritizing digital transformation and new software development policies when it historically took the service months, even years, to deploy new technology. At AWS Summit, Army Principal Deputy Assistant Secretary for Acquisition, Logistics and Technology Young Bang highlights the Army's efforts to modernize its acquisition and technology processes to field new tech more quickly. He also discusses the cybersecurity implications of new technology for a priority he said is to reduce the U.S.'s electronic footprint in the battlefield. He also emphasizes how partnerships with industry are key to this plan and the importance of data management and cybersecurity. This includes its data mesh to help it manage data more efficiently across tactical and enterprise environments.

In an interview at the AWS Summit, Department of Health and Human Services Chief Medical Officer Dr. Leith States discussed the significant impact of AI on health care. He also highlighted the critical priorities of ensuring continuity through the upcoming election cycle and managing resources effectively amid unpredictable funding scenarios. Plus, he shared his vision for health equity by design. States stressed the importance of ethical data practices, including patient empowerment, transparency and interoperability, facilitated by generative AI and machine learning. For technology providers, he advised engaging with and understanding the communities they serve to create effective solutions.

The Food and Drug Administration recently released a new acquisition strategy that aims to transform how the agency buys technology to impact multiple mission areas. In an interview with FDA Office of Enterprise Portfolio Management Director Joseph Montgomery at AWS Summit, he highlights the importance of this strategy to create a “one FDA” ecosystem that prioritizes advanced technology and keeping pace with IT innovation. Montgomery also highlights how he's thinking about artificial intelligence, cybersecurity and cloud to impact financial operations (FinOps) and ultimately support FDA's modernization goals.

Join us as we dive into an inspiring conversation from the AWS Summit in Stockholm with Matt Houghton, an AWS Ambassador and Community Builder. Matt shares insights on his team at CDL and their monumental achievement of migrating 600 Oracle databases to RDS Postgres.

Julien Lepine, directeur des Architectes Solutions AWS France, était l'invité de François Sorel dans Tech & Co, la quotidienne, ce lundi 25 mars. Il s'est penché sur l'événement AWS Summit, une édition qui sera sous le signe de l'intelligence artificielle, sur BFM Business. Retrouvez l'émission du lundi au jeudi et réécoutez la en podcast.

If you have an interest in exploring Machine Learning (who doesn't?) but have no Data Science experience, you can check this course out. We attended the AWS Summit recently, and learned a bit about ML related AWS Services, and we'll share our knowledge with you. As programmers, a lot of us lack Data Science experience. Given that, how do we leverage our existing skills to build ML systems? Purchase course in one of 2 ways: 1. Go to https://getsnowpal.com, and purchase it on the Web 2. On your phone:     (i) If you are an iPhone user, go to http://ios.snowpal.com, and watch the course on the go.     (ii). If you are an Android user, go to http://android.snowpal.com.

Welcome episode 221 of The Cloud Pod podcast - where the forecast is always cloudy! This week your hosts, Justin, Jonathan, Ryan, and Matthew look at some of the announcements from AWS Summit, as well as try to predict the future - probably incorrectly - about what's in store at Next 2023. Plus, we talk more about the storm attack, SFTP connectors (and no, that isn't how you get to the Moscone Center for Next) Llama 2, Google Cloud Deploy and more!  Titles we almost went with this week: Now You Too Can Get Ignored by Google Support via Mobile App The Tech Sector Apparently Believes Multi-Cloud is Great… We Hate You All.  The cloud pod now wants all your HIPAA Data The Meta Llama is Spreading Everywhere The Cloud Pod Recursively Deploys Deploy A big thanks to this week's sponsor: Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

This week, we discuss New Relic going private, Dell buying Moogsoft and digital transformation comes to Border Control. Plus, ideas for a last minute family vacation. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=6M31eD5nVy0) 426 (https://www.youtube.com/watch?v=6M31eD5nVy0) Runner-up Titles The Paris economy is all croissants. The Euphoria of the Buffet All that firing people gave us a soft landing. Is it going to be New Logic, or SumoRelic? You drive a hard bargain, now we're billionaires The tinfoil hat of complexity Just buy more backpacks Here in the United States, we have a lot of banks. Can Americans use it? Bigger numbers are smaller numbers. It's pretty easy to quarantine with Internet. Rundown More Monitoring, More Money Dell Technologies Announces Intent to Acquire Moogsoft (https://www.prnewswire.com/news-releases/dell-technologies-announces-intent-to-acquire-moogsoft-301881557.html) What the New Relic Sale Means for SaaS by @ttunguz (https://www.tomtunguz.com/newr_acquisition/) Exclusive: Francisco Partners, TPG end talks to buy New Relic (https://www.reuters.com/markets/deals/francisco-partners-tpg-end-talks-buy-new-relic-sources-2023-05-26/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axiosprorata&stream=top) Francisco Partners & TPG to take New Relic private in $6 billion all-cash deal (https://www.cnbc.com/2023/07/31/francisco-partners-tpg-to-take-new-relic-private-in-6-billion-deal.html) Inside the $6.5 billion buyout of New Relic (https://www.axios.com/2023/08/01/inside-the-65-billion-buyout-of-new-relic) Government IT Federal Reserve announces that its new system for instant payments, the FedNow® Service, is now live (https://www.federalreserve.gov/newsevents/pressreleases/other20230720a.htm) CBP Goes Paperless with Global Entry (https://www.cbp.gov/newsroom/local-media-release/cbp-goes-paperless-global-entry) Mexico Phasing Out Use of Paper Visitor Permits (FMM) (https://www.mexperience.com/mexico-begins-to-phase-out-paper-versions-of-the-fmm/#:~:text=Mexico%27s%20paper%20FMM%20forms%20being,Mexico%20no%20longer%20use%20them) New requirements coming in 2024 for Americans traveling to Europe (https://abcnews.go.com/GMA/Travel/new-requirements-coming-2024-americans-traveling-europe/story?id=101546203) Passport Palooza (https://markcathcart.com/2023/07/24/passport-palooza/) Relevant to your Interests Broadcom's $61 billion VMware deal wins conditional EU antitrust OK (https://www.reuters.com/markets/deals/broadcom-wins-conditional-eu-antitrust-approval-buy-vmware-2023-07-12/) Broadcom claims VMware's strategy isn't succeeding (https://www.theregister.com/2023/07/14/broadcom_vmware_cma_response/) Moderation actions (https://docs.joinmastodon.org/admin/moderation/) Shopify's anti-meeting crusade is failing and it's taken to shaming employees instead: 'Most of the modern work environment is broken' (https://fortune.com/2023/07/12/remote-work-zoom-meeting-shopify-cost-calculator-modern-work-broken/) Investors and business owners for 3x more likely to invest after reading a GPT-4 pitch deck (https://twitter.com/mrhinkle/status/1670431487621996547?s=20) 3 tax prep firms shared 'extraordinarily sensitive' data about taxpayers with Meta (https://apnews.com/article/irs-taxpayer-tax-preparation-meta-congress-9315cfca7a0942ab89f765d183fbf822) macOS Sonoma lets Chrome use passwords stored in iCloud (https://www.theverge.com/2023/7/13/23793532/apple-icloud-passwords-chrome-extension-mac-sonoma-beta) Passkeys in iOS 17: Watch a sneak peek at what's coming to 1Password for iOS | 1Password (https://blog.1password.com/apple-passkey-api-wwdc/?utm_medium=email&utm_source=beyond-passwords-newsletter-july&utm_campaign=passwordless&utm_ref=email-beyond-passwords-newsletter-july) Former Amazon Web Services data center leader Chris Vonderhaar joins Google Cloud (https://www.geekwire.com/2023/former-amazon-web-services-data-center-leader-chris-vonderhaar-joins-google-cloud/) AlmaLinux OS - Forever-Free Enterprise-Grade Operating System (https://almalinux.org/blog/future-of-almalinux/) Amazon Shares Jump 2% After Reporting Record Prime Day Sales (https://www.bloomberg.com/news/articles/2023-07-13/amazon-shares-jump-2-after-reporting-record-prime-day-sales) Threads Is About to Make All the Money That Twitter Isn't (https://slate.com/technology/2023/07/meta-threads-advertising-twitter-musk-zuckerberg.html) Mark Zuckerberg (@zuck) on Threads (https://www.threads.net/t/Cu0BgHESnwF/?igshid=MzRlODBiNWFlZA==) Jamin Ball (@jaminball) on Threads (https://www.threads.net/t/Cu3WuVGsWgy/?igshid=MzRlODBiNWFlZA==) Introducing NotebookLM (https://blog.google/technology/ai/notebooklm-google-ai/) Ford CEO explains why legacy car manufacturers cannot compete with Tesla in software (https://www.linkedin.com/feed/update/urn:li:activity:7084904611349757952?utm_source=share&utm_medium=member_desktop> linkedin.comlinkedin.com) Cloudflare as an AI play. An interview with CEO Matthew Prince. (https://redmonk.com/jgovernor/2023/07/17/cloudflare-as-an-ai-play-an-interview-with-ceo-matthew-prince/) This is huge: Llama-v2 is open source, with a license that authorizes commercial use! (http://ttps://twitter.com/ylecun/status/1681336284453781505?s=20) The Rise Of DIY In FinOps (https://www.forrester.com/blogs/the-rise-of-diy-in-finops/) Announcing Akita Has Joined Postman — Akita Software (https://www.akitasoftware.com/blog-posts/announcing-akita-has-joined-postman) Announcing the New Lightweight Postman API Client | Postman Blog (https://blog.postman.com/announcing-new-lightweight-postman-api-client/#:~:text=Starting%20May%2015%2C%202023%2C%20Scratch,calls%20through%20the%20Postman%20UI.) Does ‘Buy American' Policy Make Sense? The Answer Is Key for Your AI Portfolio Too (https://www.wsj.com/articles/does-buy-american-policy-make-sense-the-answer-is-key-for-your-ai-portfolio-too-562825af?st=zwct83dpy1hrssv) AlmaLinux says Red Hat source changes won't kill its RHEL-compatible distro (https://arstechnica.com/information-technology/2023/07/almalinux-says-red-hat-source-changes-wont-kill-its-rhel-compatible-distro/) Twitter becomes X (https://www.platformer.news/p/twitter-becomes-x?utm_source=substack&utm_medium=email) The problem with X? Meta, Microsoft, hundreds more own trademarks to new Twitter name (https://www.reuters.com/technology/problem-with-x-meta-microsoft-hundreds-more-own-trademarks-new-twitter-name-2023-07-25/) Meta Profit Is Up 16% to $7.8 Billion in Recent Quarter (https://www.nytimes.com/2023/07/26/technology/meta-earnings-second-quarter.html?smid=nytcore-ios-share&referringSource=articleShare) Top Announcements of the AWS Summit in New York, 2023 | Amazon Web Services (https://aws.amazon.com/blogs/aws/top-announcements-of-the-aws-summit-in-new-york-2023/?trk=d73defd9-9fc4-45cf-99f9-433b69146fbb&sc_channel=el) AWS Easily Beats Microsoft In $120B IaaS Cloud Market: Gartner (https://www.crn.com/news/cloud/aws-easily-beats-microsoft-in-120b-iaas-cloud-market-gartner) Russia Takes Its Ukraine Information War Into Video Games (https://www.nytimes.com/2023/07/30/technology/russia-propaganda-video-games.html) Breaking: AWS Begins Charging For Public IPv4 Addresses (https://www.lastweekinaws.com/blog/breaking-aws-begins-charging-for-public-ipv4-addresses/) The massive bug at the heart of the npm ecosystem (https://blog.vlt.sh/blog/the-massive-hole-in-the-npm-ecosystem) Tech Moves: Ex-Microsoft president joins Google Cloud as VP; iSpot hires research chief; and more (https://www.geekwire.com/2023/tech-moves-ex-microsoft-president-joins-google-cloud-as-vp-ispot-hires-research-chief-and-more/) A Day in the Life of a Senior Manager at Amazon (https://newsletter.pragmaticengineer.com/p/a-day-in-the-life-of-a-senior-manager) 7 generative AI innovations from AWS Summit New York 2023 (https://www.aboutamazon.com/news/aws/aws-summit-new-york-generative-ai) TikTok is adding text posts (https://www.theverge.com/2023/7/24/23805530/tiktok-text-posts-micro-blogging-twitter-threads) Prime Day 2023 Powered by AWS – All the Numbers (https://aws.amazon.com/blogs/aws/prime-day-2023-powered-by-aws-all-the-numbers/) AWS Launches Infrastructure Region in Israel (https://press.aboutamazon.com/2023/8/aws-launches-infrastructure-region-in-israel) AMD revenue falls 18% as PC market shows continued weakness (https://www.cnbc.com/2023/08/01/amd-earnings-report-q2-2023.html) From Docker to Dagger with Solomon Hykes (Changelog Interviews #550) (https://changelog.com/podcast/550) A New IT Automation Project? Moving Beyond Ansible And Keeping The Spirit (https://laserllama.substack.com/p/a-new-it-automation-project-moving) Google Docs can now automatically add line numbers (https://www.theverge.com/2023/7/24/23805822/google-docs-line-numbers-support) Q2 2023 is the largest quarter ever in the number of startup closures. (https://twitter.com/mahaniok/status/1682375196764717056) VCs Face an Existential Threat: There Are Too Many of Them (https://www.vice.com/en/article/4a3az9/venture-capital-vcs-existential-too-many) VC firm says their companies are good/leading, and you should invest in them too (https://twitter.com/Machiz/status/1680975185808171008) Nonsense FIGHTING (https://open.substack.com/pub/pmarca/p/fighting?r=2d4o&utm_medium=ios&utm_campaign=post) The Best Buy It for Life Backpack (Please Don't Call It Tactical) (Published 2020) (https://www.nytimes.com/wirecutter/reviews/buy-for-life-backpack/) Convicted felon gets DC contract to install car battery tech called impossible by experts (https://www.wusa9.com/article/news/investigations/lawrence-hardge-dc-battery-rejuvenation-contract/65-93a48463-e2fd-43e4-9a1b-9f727036ce0c) Americans spark backlash after claiming that Europeans ‘don't believe in water' (https://www.independent.co.uk/life-style/europe-travel-americans-water-bottles-b2377078.html) The Spongmonkeys, Fast Food's Most Unhinged Mascots, Are Back (https://www.eater.com/23797910/quiznos-spongmonkeys-unhinged-mascots-are-back) Here's why Elon Musk's rebranding of Twitter to 'X' is good, actually (https://techcrunch.com/2023/07/24/heres-why-elon-musks-rebranding-of-twitter-to-x-is-good-actually/) The First Room-Temperature Ambient-Pressure Superconductor (https://arxiv.org/abs/2307.12008) Conferences August 8th Kubernetes Community Day Australia (https://community.cncf.io/events/details/cncf-kcd-australia-presents-kubernetes-community-day-australia-2023/) in Sydney, Matt attending. August 21st to 24th SpringOne (https://springone.io/) & VMware Explore US (https://www.vmware.com/explore/us.html), in Las Vegas. Explore EU CFP is open. Sep 6th to 7th DevOpsDays Des Moines (https://devopsdays.org/events/2023-des-moines/welcome/), Coté speaking. Sep 18th to 19th SHIFT (https://shift.infobip.com/) in Zadar, Coté speaking. October 2-6, 2023, QCon San Francisco (https://qconsf.com/workshop/oct2023/open-source-kubernetes-cloud-cost-monitoring-opencost), Matt's doing a workshop October 6, 2023, KCD Texas 2023 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-2023/), CFP Closes: August 30, 2023 November 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor Jan 29, 2024 to Feb 1, 2024 That Conference Texas CFP Open 6/1 - 8/21 (https://that.us/call-for-counselors/tx/2024/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Full Circle (https://www.rottentomatoes.com/tv/full_circle_2023/s01) Matt: Amtrak Pacific Surfliner (https://www.amtrak.com/pacific-surfliner-train). Coté: A Waiter in Paris: Adventures in the Dark Heart of the City (https://amzn.to/47eBRws). Coté's Newsletter (https://cote.io/newsletter/) Photo Credits Header (https://unsplash.com/photos/ELf8M_YWRTY) Artwork (https://unsplash.com/photos/IOffoLkBmig)

Matt Wood is the VP of product at Amazon Web Services. He joins Big Technology Podcast live at the AWS Summit in New York City for a conversation about Amazon's plan to compete — and thrive — in the AI race. In this conversation, Wood describes Amazon's plan to support all AI models, not just one, and support builders via its computing infrastructure. Tune in for the most extensive comments from Amazon on its AI strategy to date. Stay tuned for the second half were we discuss ethics, company culture, and Jeff Bezos. You can read Alex's Substack story about the conversation here: Inside Amazon's Low Key Plan To Dominate AI --- Enjoying Big Technology Podcast? Please rate us five stars ⭐⭐⭐⭐⭐ in your podcast app of choice. For weekly updates on the show, sign up for the pod newsletter on LinkedIn: https://www.linkedin.com/newsletters/6901970121829801984/ Questions? Feedback? Write to: bigtechnologypodcast@gmail.com

This week, George K and George A delve into the sales shenanigans they endured recently, and report from the frontlines of enterprise AI tech. In this episode:

When 10,000 people show up to talk about cloud computing, what topics do they cover? Today, we sit down with Jeffery Kratz, Vice President, of Worldwide Public Sector Channels & Alliances to find out. With a conference this large, there are hundreds of stories to tell.  To focus on the needs of the federal government, we will look at how improvement with Amazon partners can help federal agencies reach their goals. First, Amazon is targeting partners with Transformation Modules.  This means that a partner can do the face-to-face work of understanding the needs of a specific federal program.  From there, they can take advantage of one of these modules to deepen their understanding of how innovations from Amazon can help federal agencies reduce costs and improve security for that specific initiative. Second, sometimes, great ideas come out of startups. Approaching solving federal concerns from a different perspective, Amazon is launching an AWS GovTech Accelerator for Startups.  They take the modules to the next level. The program includes a one-month virtual and combines it with in-person opportunities for technical and business mentorship for GovTech startups.  It is one thing to have a great solution, quite another to be able to package it in a format that will adhere to stringent federal requirements. It looks like this program will bring innovation faster to the federal government. Third, we learn something new.  According to the well-respected consulting firm Euroconsult, we will see 17,000 new satellites by 2030. Today's ground station technology is based on outdated proprietary hardware and software. Amazon is leading the charge when it comes to making today's ground stations simple and scalable. Jeffery Kratz mentions the success of a company out of Japan called Infostellar with a new array of 26 ground stations serving the satellite and space community. This is especially important for the newly created Space Force as well as existing programs at the Department of Defense. Listen to the interview to catch up with how Amazon is responding to the dynamic needs of federal agencies. Follow John Gilroy on Twitter @RayGilray Follow John Gilroy on LinkedIn  https://www.linkedin.com/in/john-gilroy/ Listen to past episodes of Federal Tech Podcast  www.federaltechpodcast.com  

You will remember that we had previously spoken to Allyson Fryhoff of Amazon Web Services, who explained how AWS provides many tech tools to ...

(Part 1/2) I attended the AWS Summit in DC last week, and here are some of my thoughts. #snowpal #projectmanagement #developer #api Integrate with Snowpal. Subscribe to Snowpal API. Manage personal and professional projects on https://snowpal.com. Download iOS and Android App.

(Part 2/2) I attended the AWS Summit in DC last week, and here are some of my thoughts. #snowpal #projectmanagement #developer #api Integrate with Snowpal. Subscribe to Snowpal API. Manage personal and professional projects on https://snowpal.com. Download iOS and Android App.

Capt. Erickson took the stage recently at the SWISH Data GIST 23 conference to share more about what his nascent office is doing to elevate data for transformation within the Coast Guard. Listen to what he had to say. Agencies across the federal government are looking to the cloud to elevate their next-gen computing capabilities. In this interview with Scoop News group's Wyatt Kash, Christian Hoff of AWS,highlights how NOAA, Customs and Border Protection and other agencies are using the cloud to advance their high-performance computing, data management and AI efforts — and what to look for at the upcoming AWS Summit in Washington, D.C. The Daily Scoop Podcast is available every Tuesday and Thursday afternoon. If you want to hear more of the latest from Washington, subscribe to The Daily Scoop Podcast on Apple Podcasts, Google Podcasts, Spotify and Stitcher. And if you like what you hear, please let us know in the comments.

Rijksoverheid heeft een overeenkomst bereikt met Amazon Web Services (AWS). Er is een 'framework agreement' getekend met tal van voorwaarden, onder meer qua privacy en beveiliging. Daardoor kunnen ministeries en andere overheids-departementen werken in de cloud met dat bedrijf. Dat is vandaag bekendgemaakt tijdens de AWS Summit in de RAI. Daar zijn zo'n zesduizend klanten, partners en geïnteresseerden in dergelijke toepassingen. En daar spraken we ook over dit nieuws met Merijn Schik, Senior Manager Public Policy Benelux bij Amazon Web Services. Verder in deze Tech Update: De Nederlandse overheid wil niet dat tech-bedrijven moeten gaan meebetalen aan ons telecom-netwerk. Dat blijkt nu weer uit een position paper in handen van Reuters, dat bedoeld is voor een meeting hierover met andere ministers die hierover gaan in de EU. Die komen hierover morgen bijeen in Luxemburg. "In tegenstelling tot de claims, heeft groei van het internetdata-verkeer nooit voor hogere kosten gezorgd bij telecom-bedrijven", klinkt het. See omnystudio.com/listener for privacy information.

AWS's US federal civilian and health director, Christian Hoff, highlights how NOAA, Customs and Border Protection and other agencies are using the cloud to advance their high-performance computing, data management and AI efforts — and what to look for at the upcoming AWS Summit in Washington, D.C. Host: Wyatt Kash, SVP, Content Strategy, Scoop News Group

About MattMatt is a Sr. Architect in Belfast, an AWS DevTools Hero, Serverless Architect, Author and conference speaker. He is focused on creating the right environment for empowered teams to rapidly deliver business value in a well-architected, sustainable and serverless-first way.You can usually find him sharing reusable, well architected, serverless patterns over at cdkpatterns.com or behind the scenes bringing CDK Day to life.Links Referenced: Previous guest appearance: https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/slinging-cdk-knowledge-with-matt-coulter/ The CDK Book: https://thecdkbook.com/ Twitter: https://twitter.com/NIDeveloper TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the best parts about, well I guess being me, is that I can hold opinions that are… well, I'm going to be polite and call them incendiary, and that's great because I usually like to back them in data. But what happens when things change? What happens when I learn new things?Well, do I hold on to that original opinion with two hands at a death grip or do I admit that I was wrong in my initial opinion about something? Let's find out. My guest today returns from earlier this year. Matt Coulter is a senior architect since he has been promoted at Liberty Mutual. Welcome back, and thanks for joining me.Matt: Yeah, thanks for inviting me back, especially to talk about this topic.Corey: Well, we spoke about it a fair bit at the beginning of the year. And if you're listening to this, and you haven't heard that show, it's not that necessary to go into; mostly it was me spouting uninformed opinions about the CDK—the Cloud Development Kit, for those who are unfamiliar—I think of it more or less as what if you could just structure your cloud resources using a programming language you claim to already know, but in practice, copy and paste from Stack Overflow like the rest of us? Matt, you probably have a better description of what the CDK is in practice.Matt: Yeah, so we like to say it's imperative code written in a declarative way, or declarative code written in an imperative way. Either way, it lets you write code that produces CloudFormation. So, it doesn't really matter what you write in your script; the point is, at the end of the day, you still have the CloudFormation template that comes out of it. So, the whole piece of it is that it's a developer experience, developer speed play, that if you're from a background that you're more used to writing a programming language than a YAML, you might actually enjoy using the CDK over writing straight CloudFormation or SAM.Corey: When I first kicked the tires on the CDK, my first initial obstacle—which I've struggled with in this industry for a bit—is that I'm just good enough of a programmer to get myself in trouble. Whenever I wind up having a problem that StackOverflow doesn't immediately shine a light on, my default solution is to resort to my weapon of choice, which is brute force. That sometimes works out, sometimes doesn't. And as I went through the CDK, a couple of times in service to a project that I'll explain shortly, I made a bunch of missteps with it. The first and most obvious one is that AWS claims publicly that it has support in a bunch of languages: .NET, Python, there's obviously TypeScript, there's Go support for it—I believe that went generally available—and I'm sure I'm missing one or two, I think? Aren't I?Matt: Yeah, it's: TypeScript, JavaScript, Python Java.Net, and Go. I think those are the currently supported languages.Corey: Java. That's the one that I keep forgetting. It's the block printing to the script that is basically Java cursive. The problem I run into, and this is true of most things in my experience, when a company says that we have deployed an SDK for all of the following languages, there is very clearly a first-class citizen language and then the rest that more or less drift along behind with varying degrees of fidelity. In my experience, when I tried it for the first time in Python, it was not a great experience for me.When I learned just enough JavaScript, and by extension TypeScript, to be dangerous, it worked a lot better. Or at least I could blame all the problems I ran into on my complete novice status when it comes to JavaScript and TypeScript at the time. Is that directionally aligned with what you've experienced, given that you work in a large company that uses this, and presumably, once you have more than, I don't know, two developers, you start to take on aspects of a polyglot shop no matter where you are, on some level?Matt: Yeah. So personally, I jump between Java, Python, and TypeScript whenever I'm writing projects. So, when it comes to the CDK, you'd assume I'd be using all three. I typically stick to TypeScript and that's just because personally, I've had the best experience using it. For anybody who doesn't know the way CDK works for all the languages, it's not that they have written a custom, like, SDK for each of these languages; it's a case of it uses a Node process underneath them and the language actually interacts with—it's like the compiled JavaScript version is basically what they all interact with.So, it means there are some limitations on what you can do in that language. I can't remember the full list, but it just means that it is native in all those languages, but there are certain features that you might be like, “Ah,” whereas, in TypeScript, you can just use all of TypeScript. And my first inclination was actually, I was using the Python one and I was having issues with some compiler errors and things that are just caused by that process. And it's something that talking in the cdk.dev Slack community—there is actually a very active—Corey: Which is wonderful, I will point out.Matt: [laugh]. Thank you. There is actually, like, an awesome Python community in there, but if you ask them, they would all ask for improvements to the language. So, personally if someone's new, I always recommend they start with TypeScript and then branch out as they learn the CDK so they can understand is this a me problem, or is this a problem caused by the implementation?Corey: From my perspective, I didn't do anything approaching that level of deep dive. I took a shortcut that I find has served me reasonably well in the course of my career, when I'm trying to do something in Python, and you pull up a tutorial—which I'm a big fan of reading experience reports, and blog posts, and here's how to get started—and they all have the same problem, which is step one, “Run npm install.” And that's “Hmm, you know, I don't recall that being a standard part of the Python tooling.” It's clearly designed and interpreted and contextualized through a lens of JavaScript. Let's remove that translation layer, let's remove any weird issues I'm going to have in that transpilation process, and just talk in the language it written in. Will this solve my problems? Oh, absolutely not, but it will remove a subset of them that I am certain to go blundering into like a small lost child trying to cross an eight-lane freeway.Matt: Yeah. I've heard a lot of people say the same thing. Because the CDK CLI is a Node process, you need it no matter what language you use. So, if they were distributing some kind of universal binary that just integrated with the languages, it would definitely solve a lot of people's issues with trying to combine languages at deploy time.Corey: One of the challenges that I've had as I go through the process of iterating on the project—but I guess I should probably describe it for those who have not been following along with my misadventures; I write blog posts about it from time to time because I need a toy problem to kick around sometimes because my consulting work is all advisory and I don't want to be a talking head-I have a Twitter client called lasttweetinaws.com. It's free; go and use it. It does all kinds of interesting things for authoring Twitter threads.And I wanted to deploy that to a bunch of different AWS regions, as it turns out, 20 or so at the moment. And that led to a lot of interesting projects and having to learn how to think about these things differently because no one sensible deploys an application simultaneously to what amounts to every AWS region, without canary testing, and having a phased rollout in the rest. But I'm reckless, and honestly, as said earlier, a bad programmer. So, that works out. And trying to find ways to make this all work and fit together led iteratively towards me discovering that the CDK was really kind of awesome for a lot of this.That said, there were definitely some fairly gnarly things I learned as I went through it, due in no small part to help I received from generous randos in the cdk.dev Slack team. And it's gotten to a point where it's working, and as an added bonus, I even mostly understand what he's doing, which is just kind of wild to me.Matt: It's one of those interesting things where because it's a programming language, you can use it out of the box the way it's designed to be used where you can just write your simple logic which generates your CloudFormation, or you can do whatever crazy logic you want to do on top of that to make your app work the way you want it to work. And providing you're not in a company like Liberty, where I'm going to do a code review, if no one's stopping you, you can do your crazy experiments. And if you understand that, it's good. But I do think something like the multi-region deploy, I mean, with CDK, if you'd have a construct, it takes in a variable that you can just say what the region is, so you can actually just write a for loop and pass it in, which does make things a lot easier than, I don't know, try to do it with a YAML, which you can pass in parameters, but you're going to get a lot more complicated a lot quicker.Corey: The approach that I took philosophically was I wrote everything in a region-agnostic way. And it would be instantiated and be told what region to run it in as an environment variable that CDK deploy was called. And then I just deploy 20 simultaneous stacks through GitHub Actions, which invoke custom runners that runs inside of a Lambda function. And that's just a relatively basic YAML file, thanks to the magic of GitHub Actions matrix jobs. So, it fires off 20 simultaneous processes and on every commit to the main branch, and then after about two-and-a-half minutes, it has been deployed globally everywhere and I get notified on anything that fails, which is always fun and exciting to learn those things.That has been, overall, just a really useful experiment and an experience because you're right, you could theoretically run this as a single CDK deploy and then wind up having an iterate through a list of regions. The challenge I have there is that unless I start getting into really convoluted asynchronous concurrency stuff, it feels like it'll just take forever. At two-and-a-half minutes a region times 20 regions, that's the better part of an hour on every deploy and no one's got that kind of patience. So, I wound up just parallelizing it a bit further up the stack. That said, I bet they are relatively straightforward ways, given the async is a big part of JavaScript, to do this simultaneously.Matt: One of the pieces of feedback I've seen about CDK is if you have multiple stacks in the same project, it'll deploy them one at a time. And that's just because it tries to understand the dependencies between the stacks and then it works out which one should go first. But a lot of people have said, “Well, I don't want that. If I have 20 stacks, I want all 20 to go at once the way you're saying.” And I have seen that people have been writing plugins to enable concurrent deploys with CDK out of the box. So, it may be something that it's not an out-of-the-box feature, but it might be something that you can pull in a community plug-in to actually make work.Corey: Most of my problems with it at this point are really problems with CloudFormation. CloudFormation does not support well, if at all, secure string parameters from the AWS Systems Manager parameter store, which is my default go-to for secret storage, and Secrets Manager is supported, but that also cost 40 cents a month per secret. And not for nothing, I don't really want to have all five secrets deployed to Secrets Manager in every region this thing is in. I don't really want to pay $20 a month for this basically free application, just to hold some secrets. So, I wound up talking to some folks in the Slack channel and what we came up with was, I have a centralized S3 bucket that has a JSON object that lives in there.It's only accessible from the deployment role, and it grabs that at deploy time and stuffs it into environment variables when it pushes these things out. That's the only stateful part of all of this. And it felt like that is, on some level, a pattern that a lot of people would benefit from if it had better native support. But the counterargument that if you're only deploying to one or two regions, then Secrets Manager is the right answer for a lot of this and it's not that big of a deal.Matt: Yeah. And it's another one of those things, if you're deploying in Liberty, we'll say, “Well, your secret is unencrypted at runtime, so you probably need a KMS key involved in that,” which as you know, the costs of KMS, it depends on if it's a personal solution or if it's something for, like, a Fortune 100 company. And if it's personal solution, I mean, what you're saying sounds great that it's IAM restricted in S3, and then that way only at deploy time can be read; it actually could be a custom construct that someone can build and publish out there to the construct library—or the construct hub, I should say.Corey: To be clear, the reason I'm okay with this, from a security perspective is one, this is in a dedicated AWS account. This is the only thing that lives in that account. And two, the only API credentials we're talking about are the application-specific credentials for this Twitter client when it winds up talking to the Twitter API. Basically, if you get access to these and are able to steal them and deploy somewhere else, you get no access to customer data, you get—or user data because this is not charge for anything—you get no access to things that have been sent out; all you get to do is submit tweets to Twitter and it'll have the string ‘Last Tweet in AWS' as your client, rather than whatever normal client you would use. It's not exactly what we'd call a high-value target because all the sensitive to a user data lives in local storage in their browser. It is fully stateless.Matt: Yeah, so this is what I mean. Like, it's the difference in what you're using your app for. Perfect case of, you can just go into the Twitter app and just withdraw those credentials and do it again if something happens, whereas as I say, if you're building it for Liberty, that it will not pass a lot of our Well-Architected reviews, just for that reason.Corey: If I were going to go and deploy this at a more, I guess, locked down environment, I would be tempted to find alternative approaches such as having it stored encrypted at rest via KMS in S3 is one option. So, is having global DynamoDB tables that wind up grabbing those things, even grabbing it at runtime if necessary. There are ways to make that credential more secure at rest. It's just, I look at this from a real-world perspective of what is the actual attack surface on this, and I have a really hard time just identifying anything that is going to be meaningful with regard to an exploit. If you're listening to this and have a lot of thoughts on that matter, please reach out I'm willing to learn and change my opinion on things.Matt: One thing I will say about the Dynamo approach you mentioned, I'm not sure everybody knows this, but inside the same Dynamo table, you can scope down a row. You can be, like, “This row and this field in this row can only be accessed from this one Lambda function.” So, there's a lot of really awesome security features inside DynamoDB that I don't think most people take advantage of, but they open up a lot of options for simplicity.Corey: Is that tied to the very recent announcement about Lambda getting SourceArn as a condition key? In other words, you can say, “This specific Lambda function,” as opposed to, “A Lambda in this account?” Like that was a relatively recent Advent that I haven't fully explored the nuances of.Matt: Yeah, like, that has opened a lot of doors. I mean, the Dynamo being able to be locked out in your row has been around for a while, but the new Lambda from SourceArn is awesome because, yeah, as you say, you can literally say this thing, as opposed to, you have to start going into tags, or you have to start going into something else to find it.Corey: So, I want to talk about something you just alluded to, which is the Well-Architected Framework. And initially, when it launched, it was a whole framework, and AWS made a lot of noise about it on keynote stages, as they are want to do. And then later, they created a quote-unquote, “Well-Architected Tool,” which let's be very direct, it's the checkbox survey form, at least the last time I looked at it. And they now have the six pillars of the Well-Architected Framework where they talk about things like security, cost, sustainability is the new pillar, I don't know, absorbency, or whatever the remainders are. I can't think of them off the top of my head. How does that map to your experience with the CDK?Matt: Yeah, so out of the box, the CDK from day one was designed to have sensible defaults. And that's why a lot of the things you deploy have opinions. I talked to a couple of the Heroes and they were like, “I wish it had less opinions.” But that's why whenever you deploy something, it's got a bunch of configuration already in there. For me, in the CDK, whenever I use constructs, or stacks, or deploying anything in the CDK, I always build it in a well-architected way.And that's such a loaded sentence whenever you say the word ‘well-architected,' that people go, “What do you mean?” And that's where I go through the six pillars. And in Liberty, we have a process, it used to be called SCORP because it was five pillars, but not SCORPS [laugh] because they added sustainability. But that's where for every stack, we'll go through it and we'll be like, “Okay, let's have the discussion.” And we will use the tool that you mentioned, I mean, the tool, as you say, it's a bunch of tick boxes with a text box, but the idea is we'll get in a room and as we build the starter patterns or these pieces of infrastructure that people are going to reuse, we'll run the well-architected review against the framework before anybody gets to generate it.And then we can say, out of the box, if you generate this thing, these are the pros and cons against the Well-Architected Framework of what you're getting. Because we can't make it a hundred percent bulletproof for your use case because we don't know it, but we can tell you out of the box, what it does. And then that way, you can keep building so they start off with something that is well documented how well architected it is, and then you can start having—it makes it a lot easier to have those conversations as they go forward. Because you just have to talk about the delta as they start adding their own code. Then you can and you go, “Okay, you've added these 20 lines. Let's talk about what they do.” And that's why I always think you can do a strong connection between infrastructure-as-code and well architected.Corey: As I look through the actual six pillars of the Well-Architected Framework: sustainability, cost optimization, performance, efficiency, reliability, security, and operational excellence, as I think through the nature of what this shitpost thread Twitter client is, I am reasonably confident across all of those pillars. I mean, first off, when it comes to the cost optimization pillar, please, don't come to my house and tell me how that works. Yeah, obnoxiously the security pillar is sort of the thing that winds up causing a problem for this because this is an account deployed by Control Tower. And when I was getting this all set up, my monthly cost for this thing was something like a dollar in charges and then another sixteen dollars for the AWS config rule evaluations on all of the deploys, which is… it just feels like a tax on going about your business, but fine, whatever. Cost and sustainability, from my perspective, also tend to be hand-in-glove when it comes to this stuff.When no one is using the client, it is not taking up any compute resources, it has no carbon footprint of which to speak, by my understanding, it's very hard to optimize this down further from a sustainability perspective without barging my way into the middle of an AWS negotiation with one of its power companies.Matt: So, for everyone listening, watch as we do a live well-architected review because—Corey: Oh yeah, I expect—Matt: —this is what they are. [laugh].Corey: You joke; we should do this on Twitter one of these days. I think would be a fantastic conversation. Or Twitch, or whatever the kids are using these days. Yeah.Matt: Yeah.Corey: And again, if so much of it, too, is thinking about the context. Security, you work for one of the world's largest insurance companies. I shitpost for a living. The relative access and consequences of screwing up the security on this are nowhere near equivalent. And I think that's something that often gets lost, per the perfect be the enemy of the good.Matt: Yeah that's why, unfortunately, the Well-Architected Tool is quite loose. So, that's why they have the Well-Architected Framework, which is, there's a white paper that just covers anything which is quite big, and then they wrote specific lenses for, like, serverless or other use cases that are shorter. And then when you do a well-architected review, it's like loose on, sort of like, how are you applying the principles of well-architected. And the conversation that we just had about security, so you would write that down in the box and be, like, “Okay, so I understand if anybody gets this credential, it means they can post this Last Tweet in AWS, and that's okay.”Corey: The client, not the Twitter account, to be clear.Matt: Yeah. So, that's okay. That's what you just mark down in the well-architected review. And then if we go to day one on the future, you can compare it and we can go, “Oh. Okay, so last time, you said this,” and you can go, “Well, actually, I decided to—” or you just keep it as a note.Corey: “We pivoted. We're a bank now.” Yeah.Matt: [laugh]. So, that's where—we do more than tweets now. We decided to do microtransactions through cryptocurrency over Twitter. I don't know but if you—Corey: And that ends this conversation. No no. [laugh].Matt: [laugh]. But yeah, so if something changes, that's what the well-architected reviews for. It's about facilitating the conversation between the architect and the engineer. That's all it is.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: And the lens is also helpful in that this is a serverless application. So, we're going to view it through that lens, which is great because the original version of the Well-Architected Tool is, “Oh, you built this thing entirely in Lambda? Have you bought some reserved instances for it?” And it's, yeah, why do I feel like I have to explain to AWS how their own systems work? This makes it a lot more streamlined and talks about this, though, it still does struggle with the concept of—in my case—a stateless app. That is still something that I think is not the common path. Imagine that: my code is also non-traditional. Who knew?Matt: Who knew? The one thing that's good about it, if anybody doesn't know, they just updated the serverless lens about, I don't know, a week or two ago. So, they added in a bunch of more use cases. So, if you've read it six months ago, or even three months ago, go back and reread it because they spent a good year updating it.Corey: Thank you for telling me that. That will of course wind up in next week's issue of Last Week in AWS. You can go back and look at the archives and figure out what week record of this then. Good work. One thing that I have learned as well as of yesterday, as it turns out, before we wound up having this recording—obviously because yesterday generally tends to come before today, that is a universal truism—is it I had to do a bit of refactoring.Because what I learned when I was in New York live-tweeting the AWS Summit, is that the Route 53 latency record works based upon where your DNS server is. Yeah, that makes sense. I use Tailscale and wind up using my Pi-hole, which lives back in my house in San Francisco. Yeah, I was always getting us-west-1 from across the country. Cool.For those weird edge cases like me—because this is not the common case—how do I force a local region? Ah, I'll give it its own individual region prepend as a subdomain. Getting that to work with both the global lasttweetinaws.com domain as well as the subdomain on API Gateway through the CDK was not obvious on how to do it.Randall Hunt over at Caylent was awfully generous and came up with a proof-of-concept in about three minutes because he's Randall, and that was extraordinarily helpful. But a challenge I ran into was that the CDK deploy would fail because the way that CloudFormation was rendered in the way it was trying to do stuff, “Oh, that already has that domain affiliated in a different way.” I had to do a CDK destroy then a CDK deploy for each one. Now, not the end of the world, but it got me thinking, everything that I see around the CDK more or less distills down to either greenfield or a day one experience. That's great, but throw it all away and start over is often not what you get to do.And even though Amazon says it's always day one, those of us in, you know, real companies don't get to just treat everything as brand new and throw away everything older than 18 months. What is the day two experience looking like for you? Because you clearly have a legacy business. By legacy, I of course, use it in the condescending engineering term that means it makes actual money, rather than just telling really good stories to venture capitalists for 20 years.Matt: Yeah. We still have mainframes running that make a lot of money. So, I don't mock legacy at all.Corey: “What's that piece of crap do?” “Well, about $4 billion a year in revenue. Perhaps show some respect.” It's a common refrain.Matt: Yeah, exactly. So yeah, anyone listening, don't mock legacy because as Corey says, it is running the business. But for us when it comes to day two, it's something that I'm actually really passionate about this in general because it is really easy. Like I did it with CDK patterns, it's really easy to come out and be like, “Okay, we're going to create a bunch of starter patterns, or quickstarts”—or whatever flavor that you came up with—“And then you're going to deploy this thing, and we're going to have you in production and 30 seconds.” But even day one later that day—not even necessarily day two—it depends on who it was that deployed it and how long they've been using AWS.So, you hear these stories of people who deployed something to experiment, and they either forget to delete, it cost them a lot of money or they tried to change it and it breaks because they didn't understand what was in it. And this is where the community starts to diverge in their opinions on what AWS CDK should be. There's a lot of people who think that at the minute CDK, even if you create an abstraction in a construct, even if I create a construct and put it in the construct library that you get to use, it still unravels and deploys as part of your deploy. So, everything that's associated with it, you don't own and you technically need to understand that at some point because it might, in theory, break. Whereas there's a lot of people who think, “Okay, the CDK needs to go server side and an abstraction needs to stay an abstraction in the cloud. And then that way, if somebody is looking at a 20-line CDK construct or stack, then it stays 20 lines. It never unravels to something crazy underneath.”I mean, that's one pro tip thing. It'd be awesome if that could work. I'm not sure how the support for that would work from a—if you've got something running on the cloud, I'm pretty sure AWS [laugh] aren't going to jump on a call to support some construct that I deployed, so I'm not sure how that will work in the open-source sense. But what we're doing at Liberty is the other way. So, I mean, we famously have things like the software accelerator that lets you pick a pattern or create your pipelines and you're deployed, but now what we're doing is we're building a lot of telemetry and automated information around what you deployed so that way—and it's all based on Well-Architected, common theme. So, that way, what you can do is you can go into [crosstalk 00:26:07]—Corey: It's partially [unintelligible 00:26:07], and partially at a glance, figure out okay, are there some things that can be easily remediated as we basically shift that whole thing left?Matt: Yeah, so if you deploy something, and it should be good the second you deploy it, but then you start making changes. Because you're Corey, you just start adding some stuff and you deploy it. And if it's really bad, it won't deploy. Like, that's the Liberty setup. There's a bunch of rules that all go, “Okay, that's really bad. That'll cause damage to customers.”But there's a large gap between bad and good that people don't really understand the difference that can cost a lot of money or can cause a lot of grief for developers because they go down the wrong path. So, that's why what we're now building is, after you deploy, there's a dashboard that'll just come up and be like, “Hey, we've noticed that your Lambda function has too little memory. It's going to be slow. You're going to have bad cold starts.” Or you know, things like that.The knowledge that I have had the gain through hard fighting over the past couple of years putting it into automation, and that way, combined with the well-architected reviews, you actually get me sitting in a call going, “Okay, let's talk about what you're building,” that hopefully guides people the right way. But I still think there's so much more we can do for day two because even if you deploy the best solution today, six months from now, AWS are releasing ten new services that make it easier to do what you just did. So, someone also needs to build something that shows you the delta to get to the best. And that would involve AWS or somebody thinking cohesively, like, these are how we use our products. And I don't think there's a market for it as a third-party company, unfortunately, but I do think that's where we need to get to, that at day two somebody can give—the way we're trying to do for Liberty—advice, automated that says, “I see what you're doing, but it would be better if you did this instead.”Corey: Yeah, I definitely want to spend more time thinking about these things and analyzing how we wind up addressing them and how we think about them going forward. I learned a lot of these lessons over a decade ago. I was fairly deep into using Puppet, and came to the fair and balanced conclusion that Puppet was a steaming piece of crap. So, the solution was that I was one of the very early developers behind SaltStack, which was going to do everything right. And it was and it was awesome and it was glorious, right up until I saw an environment deployed by someone else who was not as familiar with the tool as I was, at which point I realized hell is other people's use cases.And the way that they contextualize these things, you craft a finely balanced torque wrench, it's a thing of beauty, and people complain about the crappy hammer. “You're holding it wrong. No, don't do it that way.” So, I have an awful lot of sympathy for people building platform-level tooling like this, where it works super well for the use case that they're in, but not necessarily… they're not necessarily aligned in other ways. It's a very hard nut to crack.Matt: Yeah. And like, even as you mentioned earlier, if you take one piece of AWS, for example, API Gateway—and I love the API Gateway team; if you're listening, don't hate on me—but there's, like, 47,000 different ways you can deploy an API Gateway. And the CDK has to cover all of those, it would be a lot easier if there was less ways that you could deploy the thing and then you can start crafting user experiences on a platform. But whenever you start thinking that every AWS component is kind of the same, like think of the amount of ways you're can deploy a Lambda function now, or think of the, like, containers. I'll not even go into [laugh] the different ways to run containers.If you're building a platform, either you support it all and then it sort of gets quite generic-y, or you're going to do, like, what serverless cloud are doing though, like Jeremy Daly is building this unique experience that's like, “Okay, the code is going to build the infrastructure, so just build a website, and we'll do it all behind it.” And I think they're really interesting because they're sort of opposites, in that one doesn't want to support everything, but should theoretically, for their slice of customers, be awesome, and then the other ones, like, “Well, let's see what you're going to do. Let's have a go at it and I should hopefully support it.”Corey: I think that there's so much that can be done on this. But before we wind up calling it an episode, I had one further question that I wanted to explore around the recent results of the community CDK survey that I believe is a quarterly event. And I read the analysis on this, and I talked about it briefly in the newsletter, but it talks about adoption and a few other aspects of it. And one of the big things it looks at is the number of people who are contributing to the CDK in an open-source context. Am I just thinking about this the wrong way when I think that, well, this is a tool that helps me build out cloud infrastructure; me having to contribute code to this thing at all is something of a bug, whereas yeah, I want this thing to work out super well—Docker is open-source, but you'll never see me contributing things to Docker ever, as a pull request, because it does, as it says on the tin; I don't have any problems that I'm aware of that, ooh, it should do this instead. I mean, I have opinions on that, but those aren't pull requests; those are complete, you know, shifts in product strategy, which it turns out is not quite done on GitHub.Matt: So, it's funny I, a while ago, was talking to a lad who was the person who came up with the idea for the CDK. And CDK is pretty much the open-source project for AWS if you look at what they have. And the thought behind it, it's meant to evolve into what people want and need. So yes, there is a product manager in AWS, and there's a team fully dedicated to building it, but the ultimate aspiration was always it should be bigger than AWS and it should be community-driven. Now personally, I'm not sure—like you just said it—what the incentive is, given that right now CDK only works with CloudFormation, which means that you are directly helping with an AWS tool, but it does give me hope for, like, their CDK for Terraform, and their CDK for Kubernetes, and there's other flavors based on the same technology as AWS CDK that potentially could have a thriving open-source community because they work across all the clouds. So, it might make more sense for people to jump in there.Corey: Yeah, I don't necessarily think that there's a strong value proposition as it stands today for the idea of the CDK becoming something that works across other cloud providers. I know it technically has the capability, but if I think that Python isn't quite a first-class experience, I don't even want to imagine what other providers are going to look like from that particular context.Matt: Yeah, and that's from what I understand, I haven't personally jumped into the CDK for Terraform and we didn't talk about it here, but in CDK, you get your different levels of construct. And is, like, a CloudFormation-level construct, so everything that's in there directly maps to a property in CloudFormation, and then L2 is AWS's opinion on safe defaults, and then L3 is when someone like me comes along and turns it into something that you may find useful. So, it's a pattern. As far as I know, CDK for Terraform is still on L1. They haven't got the rich collection—Corey: And L4 is just hiring you as a consultant—Matt: [laugh].Corey: —to come in fix my nonsense for me?Matt: [laugh]. That's it. L4 could be Pulumi recently announced that you can use AWS CDK constructs inside it. But I think it's one of those things where the constructs, if they can move across these different tools the way AWS CDK constructs now work inside Pulumi, and there's a beta version that works inside CDK for Terraform, then it may or may not make sense for people to contribute to this stuff because we're not building at a higher level. It's just the vision is hard for most people to get clear in their head because it needs articulated and told as a clear strategy.And then, you know, as you said, it is an AWS product strategy, so I'm not sure what you get back by contributing to the project, other than, like, Thorsten—I should say, so Thorsten who wrote the book with me, he is the number three contributor, I think, to the CDK. And that's just because he is such a big user of it that if he sees something that annoys him, he just comes in and tries to fix it. So, the benefit is, he gets to use the tool. But he is a super user, so I'm not sure, outside of super users, what the use case is.Corey: I really want to thank you for, I want to say spending as much time talking to me about this stuff as you have, but that doesn't really go far enough. Because so much of how I think about this invariably winds up linking back to things that you have done and have been advocating for in that community for such a long time. If it's not you personally, just, like, your fingerprints are all over this thing. So, it's one of those areas where the entire software developer ecosystem is really built on the shoulders of others who have done a lot of work that came before. Often you don't get any visibility of who those people are, so it's interesting whenever I get to talk to someone whose work I have directly built upon that I get to say thank you. So, thank you for this. I really do appreciate how much more straightforward a lot of this is than my previous approach of clicking in the console and then lying about it to provision infrastructure.Matt: Oh, no worries. Thank you for the thank you. I mean, at the end of the day, all of this stuff is just—it helps me as much as it helps everybody else, and we're all trying to do make everything quicker for ourselves, at the end of the day.Corey: If people want to learn more about what you're up to, where's the best place to find you these days? They can always take a job at Liberty; I hear good things about it.Matt: Yeah, we're always looking for people at Liberty, so come look up our careers. But Twitter is always the best place. So, I'm @NIDeveloper on Twitter. You should find me pretty quickly, or just type Matt Coulter into Google, you'll get me.Corey: I like it. It's always good when it's like, “Oh, I'm the top Google result for my own name.” On some level, that becomes an interesting thing. Some folks into it super well, John Smith has some challenges, but you know, most people are somewhere in the middle of that.Matt: I didn't used to be number one, but there's a guy called the Kangaroo Kid in Australia, who is, like, a stunt driver, who was number one, and [laugh] I always thought it was funny if people googled and got him and thought it was me. So, it's not anymore.Corey: Thank you again for, I guess, all that you do. And of course, taking the time to suffer my slings and arrows as I continue to revise my opinion of the CDK upward.Matt: No worries. Thank you for having me.Corey: Matt Coulter, senior architect at Liberty Mutual. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice and leave an angry comment as well that will not actually work because it has to be transpiled through a JavaScript engine first.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Erik Bradly from ETR joins theCUBE hosts Dave Vellante and John Furrier live from our coverage of AWS Summit New York 2022

About MaishMaish Saidel-Keesing is a Senior Enterprise Developer Advocate @AWS working on containers and has been working in IT for the past 20 years and with a stronger focus on cloud and automation for the past 7.He has extensive experience with AWS Cloud technologies, DevOps and Agile practices and implementations, containers, Kubernetes, virtualization and, and a number of fun things he has done along the wayHe is constantly trying to bridge the gap between Developers and Operators to allow all of us provide a better service for our customers (and not wake up from pages in the middle of the night). He is an avid practitioner of dissolving silos - educating Ops how to code and explaining to Devs what the hell is OperationsLinks Referenced: @maishsk: https://twitter.com/maishsk duckbillgroup.com: https://duckbillgroup.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Fortinet. Fortinet's partnership with AWS is a better-together combination that ensures your workloads on AWS are protected by best-in-class security solutions powered by comprehensive threat intelligence and more than 20 years of cybersecurity experience. Integrations with key AWS services simplify security management, ensure full visibility across environments, and provide broad protection across your workloads and applications. Visit them at AWS re:Inforce to see the latest trends in cybersecurity on July 25-26 at the Boston Convention Center. Just go over to the Fortinet booth and tell them Corey Quinn sent you and watch for the flinch. My thanks again to my friends at Fortinet.Corey: Let's face it, on-call firefighting at 2am is stressful! So there's good news and there's bad news. The bad news is that you probably can't prevent incidents from happening, but the good news is that incident.io makes incidents less stressful and a lot more valuable. incident.io is a Slack-native incident management platform that allows you to automate incident processes, focus on fixing the issues and learn from incident insights to improve site reliability and fix your vulnerabilities. Try incident.io, recover faster and sleep more.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm a cloud economist at The Duckbill Group, and that was a fun thing for me to become because when you're starting to set out to solve a problem, well, what do you call yourself? I find that if you create a job title for yourself, well, no one knows quite how to categorize you and it leads to really interesting outcomes as a result. My guest today did something very similar. Maish Saidel-Keesing is an EntReloper, or Enterprise Developer Advocate, specifically for container services at AWS. Maish, thank you for joining me.Maish: Thank you for having me on the show, Corey. It's great to be here.Corey: So, how did you wind up taking a whole bunch of words such as enterprise, developer, advocate because I feel like the way you really express seniority at big companies, almost as a display of dominance, is to have additional words in your job title, which all those words are very enterprise-y, very business-y, and very serious. And in container services to boot, which is a somewhat interesting culture, just looking at the enterprise adoption of the pattern. And then at AWS, whose entire sense of humor can be distilled down into, “That's not funny.” You have the flexibility to refer to yourself as an EntReloper in public. I love it. Is it just something you started doing? Was there, like, 18 forms of approval you had to go through to do it? How did this happen? I love it.Maish: So, no. I didn't have to go through approval, of course. Same way, you didn't call yourself a cloud economist with anybody else's approval. But I got the idea mostly from you because I love your term of coining everybody who's in developer advocacy or developer relations as a DevReloper. And specifically, the reason that I coined the term of an EntReloper—and actually looked it up on Google to see if anybody had actually used that term before, and no they haven't—it's the fact of I came into the position on the premise of trying to bring the enterprise voice of the customer into developer advocacy.When we speak about developer advocates today, most of them are the people who are the small startups, developers who write the code, and we kind of forget that there is a whole big world outside of, besides small startups, which are these big, massive, behemoth sort of enterprise companies who kind of do things differently because they've been around for many, many years; they have many, many silos inside their organizations. And it's not the most simple thing to open up your laptop, and install whatever software you want on, because some of these people don't even give you admin rights on your laptop, or you're allowed to ssh out to a computer in the cloud because also the same thing: everything is blocked by corporate firewalls where you have to put in a ticket in order to get access to the outside world. I worked in companies like that when I was—before I moved to Amazon. So, I want to bring that perspective to the table on behalf of our customers.Corey: Bias is a very funny thing. I spent the overwhelming majority of my career in small environments like you describe. To me a big company is one that has 200 people there, and it turns out that there's a whole ‘nother sense of scale that goes beyond that. And there's, like, 18 different tiers beyond. But I still bias based upon my own experiences when I talk about how I do things and how I think about things to a certain persona that closely resembles my own experiences where, “Just install this thing as a tool and it'll be great,” ignoring entirely, the very realistic fact that you've got an entire universe out there of people who are not empowered to install things on their own laptop, for example.How is developer advocacy different within enterprises than in the common case of, “We're a startup. We're going to change the world with our amazing SaaS.” Great, maybe you will. Statistically, you won't. But enterprises have different concerns, different challenges, and absolutely a different sense of scale. How is the practice of advocacy different in those environments?Maish: So, I think the fact is, mostly working on standardization from the get-go that these big enterprises want things to work in a standard way where they can control it, they can monitor it, they can log everything, they can secure it mostly, of course, the most important thing. But it's also the fact that as a developer advocate, you don't always talk to developers within the enterprise. You also have to talk to the security team and to the network team and to the business itself or the C-level to understand. And as you also probably have found out as well in your job, you connect the people with inside the business one to another, these different groups, and get them talking to each other to make these decisions together. So, we act as kind of a bridge in between the people with inside their own company where they don't really talk to each other, or don't have the right connections, or the right conduit in order for them to start that conversation and make things better for themselves.Corey: On some level, my line about developer relations, developer advocacy, has generally taken the track of, “What does that mean? Well, it means you work in marketing, but they're scared to tell you that.” Do you view what you do as being within marketing, aligned with marketing, subtly different and I'm completely wrong, et cetera, et cetera? All positions are legitimate, by the way.Maish: So, I think, at the position that I'm currently in, which is a developer advocate but for the service team, is slightly different than a marketing developer advocate. The marketing developer advocate—and we have many of them which are amazing people and doing amazing work within AWS—their job is to teach everybody about the services and the capabilities available within AWS. That is also part of my job, but I would think that is the 40% of my job. I also go on stage, I go on podcasts like this, I present at conferences, I write blog posts. I also do the kind of marketing work as well.But the other 60% of my job as a service developer advocate is to seek out the feedback, or the signals, or the sentiment from our customers, and bring that back into the service teams, into the product management, into the engineering teams. And, as I said, sit as the enterprise customer in the chair in those meetings, to voice their concerns… their opinions, how they would like the products to go, how we can make the products better. So, the 60% is mostly what we call inbound, which is taking feedback from our customers back into the service teams directly in order to have some influence on the roadmap. And 40% is the outbound work, which we do, as I said, conferences, blog posts, and things like this.Corey: I have a perception. And I am thrilled to be corrected on this because it's not backed by data; it's backed by my own biases—and some people tend to conflate the two; I strive not to—that there's a—I think the term that I heard bandied around at one point was ‘the dark matter developers.' These are folks that primarily work in .NET or Java. They work for companies that are not themselves tech companies, but rather tech is a supporting function, usually in a central IT-style organization, that supports what the business actually does, and they generally are not visible to a lot of traditional developer advocacy approaches.They, by and large, don't go to conferences, they don't go on Twitter to yell at people about things, they commit the terrible sin—according to many startup folks—of daring to view the craft of writing software as this artistic thing, and they just view it as a job and a thing to make money for—filthy casuals—as opposed to this higher calling that's changing the world. Which I think is wild take. But there are a tremendous number of people out there who do fit the profile of they show up, they do their jobs working on this stuff, they don't go to conferences, they don't go out into the community, and they just do their job and go home. The end. Is that an accurate perception? Are there large swaths of folks like that in the industry, and if so, do they centralize or congregate more around enterprises than they do around smaller companies?Maish: I think that your perception is correct. Specifically, for my experience, when I worked, for example, my first two years before I was a developer advocate, I was an enterprise solutions architect which I worked with financial institutions, which are banks, which usually have software which are older than me, which are written in languages, which are older than I am. So, there are people which, as they say, they come there to—they do their job. They're not interested in looking at Twitter, or writing blog posts, or participating in any kind of thing which is outgoing. And they just, they're there to write the code. They go home at the end of the day.They also usually don't have pagers that page them in middle of the night because that's what you have operations teams for, not developers because they're completely different entities. So, I do think your perception might be correct, yes. There are people like that when you say, these dark matter people, dark matter developers.Corey: And I don't have any particular problem. I'm not here to cast shade on anything that they're doing, to be very clear.Maish: Not at all.Corey: Everyone makes different choices and that's great. I don't think necessarily everyone should have a job that is all-consuming, that eats them alive. I wish I didn't, some days. [laugh]. The challenge I have for you then is, as an EntReloper, how do you reach folks in positions like that? Or don't you?Maish: I think the way to reach those people is to firstly, expose them to technology, expose them to the capabilities that they can use in AWS in the cloud, specifically with my position in container services, and gain their trust because that's one of the LPs in Amazon itself: customer obsession. And we work consistently in order to—with our customers to gain their trust and help them along their journey, whatever it may be. If it might be the fact, okay, I only want to write software for nine to five and go home and do everything afterwards, which most normal people do without having to worry about work, or they still want to continue working and adopt the full model of you build it, you own it; manage everything in production on their own and go into the new world of modern software, which many enterprises, unfortunately, are not all the way there yet, but hopefully, they will get there sooner than later.Corey: There's a misguided perception in many corners that you have to be able to reach everyone at all times; wherever they are, you have to be able to go there. I don't think that's true. I think that showing up and badgering people who are just trying to get a job done into, “Hey, have you heard the good word of cloud?” It's like, evangelists knocking on your door at seven o'clock in the morning on a weekend and you're trying to sleep in because the kids are somewhere else for the week. Yeah, I might be projecting a little bit on that.I think that is the wrong direction to go. And I find that being able and willing to meet people where they are is key to success on this. I'm also a big believer in the idea that in any kind of developer advocacy role, regardless whether their targets are large, small, or in my case, patently ridiculous because my company is in fact ridiculous in some ways, you have to meet them where they are. There's no choice around that. Do you find that there are very different concerns that you have to wind up addressing with your audience versus a more, “Mainstream,” quote-unquote, developer advocacy role?Maish: For the enterprise audience, they need to, I would say, relate to what we're talking to. For an example, I gave a talk a couple of weeks ago on the AWS Summit here in Tel Aviv, of how to use App Runner. So, instead of explaining to the audiences how you use the console, this is what it does, you can deploy here, this is how the deployments work, blue, green, et cetera, et cetera, I made up an imaginary company and told the story of how the three people in the startup of this company would start working using App Runner in order to make the thing more relatable, something which people can hopefully remember and understand, okay, this is something which I would do as a startup, or this is what my project, which I'm doing or starting to work on, something I can use. So, to answer your question, in two words, tell stories instead of demo products.Corey: It feels like that's a… heavy lift, in many cases, because I guess it's also partially a perception issue on my part, where I'm looking at this across the board, where I see a company that has 5000 developers working there and, like, how do you wind up getting them to adopt cloud, or adopt new practices, or change anything? It feels like it's a Herculean, impossible task. But in practice, I feel like you don't try and do all of that at once. You start with small teams, you start with specific projects, and move on. Is that directionally accurate?Maish: Completely accurate. There's no way to move a huge mothership in one direction at one time. You have to do, as you say, start small, find the projects, which are going to bring value to the company or the business, and start small with those projects and those small teams, and continue that education within the organization and help the people with your teaching or introducing them to the cloud, to help others within inside their own organization. Make them, or enable them, or empower them to become leaders within their own organization. That's what I tried to do, at least.Corey: You and I have a somewhat similar background, which is weird given that we've just spent a fair bit of time talking about how different our upbringings were in tech at scales of companies and whatnot, but we're alike in that we are both fairly crusty, old operations-side folks, sysadmins—Maish: [laugh]. Yep.Corey: —grumpy people.Maish: Grumpy old sysadmins. Yeah, exactly.Corey: Exactly. Because do you ever notice there's never a happy one? Imagine that. And DevOps was always a meeting of the development and operations, meaning everyone's unhappy. And there's a school of thought that—like, I used to think that, “Oh, this is just what we call sysadmins once they want a better title and more money, but it's still the same job.”But then I started meeting a bunch of DevOps types who had come from the exact opposite of our background, where they were software developers and then they wound up having to learn not so much how the code stuff works the way that we did, but rather how systems work, how infrastructure works. Compare and contrast those for me. Who makes, I guess, the more successful DevOps engineer when you look at it through that lens?Maish: So, I might be crucified for this on the social media from a number of people from the other side of the fence, but I have the firm belief that the people who make the best DevOps engineers—and I hate that term—but people who move DevOps initiatives or changes or transformations with organization is actually the operations people because they usually have a broader perspective of what is going on around them besides writing code. Too many times in my career, I've been burned by DNS, by a network cable, by a power outage, by somebody making a misconfiguration in the Puppet module, or whatever it might have been, somebody wrote it to deploy to 15,000 machines, whatever it may be. These are things where developers, at least my perception of what developers have been doing up until now, don't really do that. In a previous organization I used to work for, the fact was, there was a very, very clear delineation about between the operations people, and the developers who wrote the software. We had very hard times getting them into rotations for on-call, we had very hard times educating them about the fact that not every single log line has to be written to the log because it doesn't interest anybody.But from developer perspective, of course, we need that log because we need to know what's happening in the end. But there are 15, different thousand… turtles all the way down, which have implications about the number of log lines which are written into a piece of software. So, I am very much of the belief that the people that make the best DevOps engineers—if we can use that term still today—are actually people which come from an operations background because it's easier to teach them how to write code or become a programmer than the other way round of teaching a developer how to become an operations person. So, the change or the move from one direction from operations to adding the additional toil of writing software is much easier to accomplish than the other way around, from a developer learning how to run infrastructure at scale.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: I once believed much the same because—and it made sense coming from the background that I was in. Everyone intellectually knows that if you're having trouble with a piece of equipment, have you made sure that it's plugged in? Yes, everyone knows that intellectually. But there's something about having worked on a thing for three hours that wasn't working and only discover it wasn't plugged in, that really sears that lesson into your bones. The most confidence-inspiring thing you can ever hear from someone an operations role is, “Oh, I've seen this problem before. Here's how we fixed it.”It feels like there are no junior DevOps engineers, for lack of a better term. And for a long time, I believed that the upcoming and operational side of the world were in fact, the better DevOps types. And in the fullness of time, I think a lot of that—at least my position on it—was rooted in some level of insecurity because I didn't know how to write code and the thing that I saw happening was my job that I had done historically was eroding. Today, I don't know that it's possible to be in the operation space and not be at least basically conversant with how code works. There's a reason most of these job interviews turn into algorithm hazing.And my articulation of it was rooted, for me at least—at least in a small way—in a sense of defensiveness and wanting to validate the thing that I had done with my career that I defined myself by, I was under threat. And obviously, the thing that I do is the best thing because otherwise it's almost a tacit admission that I made poor career choices at some point. And I don't think that's true, either. But for me, at least psychologically, it was very much centered in that. And honestly, I found that the right answer for me was, in fact, neither of those two things because I have met a couple of people in my life that I would consider to be full-stack engineers.And there's a colloquialism these days, that means oh, you do front-end and back-end. Yeah. The people I'm thinking of did front-end, they did back-end, they did mobile software, they did C-level programming, they wrote their own freaking device drivers at one point. Like, they have done basically everything. And they were the sort of person you could throw any technical issue whatsoever at and get out of their way because it was going to get solved. Those people are, as it turns out, the best. Like, who does a better job developer or operations, folks? Yes. Specifically, both of those things together.Maish: Exactly.Corey: And I think that is a hard thing to talk about. I think that it's a hard—it's certainly a hard thing to find. It turns out that there's a reason that I only know two or three of those folks in the course of my entire career. They're out there, but they're really, really hard to track down.Maish: I completely agree.Corey: A challenge that I hear articulated in some cases—and while we're saying things that are going to get us yelled out on social media, let's go for the fences on this one—a concern that comes up when talking about enterprises moving to cloud is that they have a bunch of existing sysadmin types—while we're on the topic—and well, those people need to learn to work within cloud. And the reality is, in many cases that first, that's a whole new skill set that not everyone is going to be willing or able to pick up. For those who can they have just found that their market rate has effectively doubled. And that seems, on some level, to pose a significant challenge to companies undergoing this, and the larger the company, the more significant the challenge.Because it's my belief that you pay market rate for the talent you have whether you want to or not. And if companies don't increase compensation, these people will leave for things that double their income. And if they raise compensation internally, good for them, but that does have a massive drag on their budget that may not have been accounted for in a lot of the TCO analyses. How do you find that the companies you talk to wind up squaring that circle?Maish: I don't think I have a correct answer for that. I do completely agree—Corey: Oh, I'm not convinced there's a correct answer at all. I'm just trying [laugh] to figure out how to even think about it.Maish: I… have seen this as well in companies which I used to work for and companies that were customers that I have also worked with as part of my tenure in AWS. It's the fact of, when companies are trying to move to the cloud and they start upskilling their people, there's always the concern in the back of their mind of the fact, “Okay, I'm now training this person with new technology. I'm investing time, I'm investing money. And why would I do this if I know that, for example, as soon as I finish this, I'm going to have to just say, I have to pay them more because they can go somewhere else and get the same job with a better pay? So, why would we invest amount of time and resources into upscaling the people?”And these are questions which I have received and conversations which I've had with customers many times over the last two, three years. And the answer, from my perspective always, is the fact is because, number one, you're making the world a better place. Number two, you're making your employees feel more appreciated, giving them better knowledge. And if you're afraid of the fact of teaching somebody to become better is going to have negative effects on your organization then, unfortunately, you deserve to have that person leave and let them find a better job because you're not taking good care of your people. And it's sometimes hard for companies to hear that.Sometimes we get, “You know what? You're completely right.” Sometimes I don't agree with you because I need to compete there, get to the bottom line, and make sure that I stay within my budget or my TCO. But the most important thing is to have the conversation, let people hear different ideas, see how it can benefit them, not only by giving people more options to maybe leave the company, but it can actually make their whole organization a lot better in the long run.Corey: I think that you have to do right by people because reputations last a long time. Even at big companies it becomes a very slow thing to change and almost impossible to do in the short term. So, people tell stories when they feel wronged. That becomes a problem. I do want to pivot a little bit because you're not merely an EntReloper; you are an EntReloper specifically focusing on container services.Maish: Correct.Corey: Increasingly, I am viewing containers as what amounts to effectively a packaging format. That is the framework through which I am increasingly seeing. How are you seeing customers use containers? Is that directionally correct? Is it completely moonbat stuff compared to what you're seeing in the wild, or something else?Maish: I don't think it's a packaging format; I think it's more as an accelerator to enable the customers to develop in a more modern way with using twelve-factor apps with modern technology and not necessarily have their own huge, sticky, big monolith of whatever it might be, written in C# or whatever, or C++ whatever it may be, as they've been using up until now, but they now have the option and the technology and the background in order to split it up into smaller services and develop in the way that most of the modern world—or at least, the what we perceive as the modern world—is developing and creating applications today.Corey: I feel like on some level, containers were a radical change to how companies envisioned software. They definitely provide a path of modernizing things that were very tied to hardware previously. It let some companies even just leapfrog the virtualization migration that they'd been considering doing. But, on some level, I also feel like it runs counter to the ideas of DevOps, where you have development and operations working in partnership, where now it's like, welp, inside the container is a development thing and outside the container, ops problem now. It feels almost, on some level, like, it reinforces a wall. But in a lot of cultures and a lot of companies, that wall is there and there's no getting rid of it anytime soon. So, I confess that I'm conflicted on that.Maish: I think you might be right, and it depends, of course, on the company and the company culture, but what I think that companies need to do is understand that there will never be one hundred percent of people writing software that want to know one hundred percent of how the underlying infrastructure works. And the opposite direction as well: that there will never be people which maintain infrastructure and understand how computers and CPUs and memory buses and NUMA works on motherboards, that they don't need to know how to write the most beautiful enticing and wonderful software for programs, for the world. There's always going to have to be a compromise of who's going to be doing this or who's going to be doing that, and how comfortable they are with taking at least part of the responsibility of the other side into their own realm of what they should be doing. So, there's going to be a compromise on both sides, but there is some kind of divide today of separating, okay, you just write the Helm chart for your Kubernetes Pod spec, or your ECS task, or whatever task definition, whatever you would like. And don't worry about the things in the background because they're just going to magically happen in the end. But they do have to understand exactly what is happening at the background in the end because if something goes wrong, and of course, something will go wrong, eventually, one day somewhere, somehow, they're going to have to know how to take care of it.Corey: I really want to thank you for taking the time to speak with me today about, well, I guess a wide ranging variety of topics, some of which will absolutely inspire people to take to their feet—or at least their Twitter accounts—and tell us, “You know what your problem is?” And I honestly live for that. If you don't evoke that kind of reaction on some level, have you ever really had an opinion in the first place? So, I'm looking forward to that. If people want to learn more about you, your beliefs, call set beliefs misguided, et cetera, et cetera, where's the best place to find you?Maish: So, I'm on Twitter under @maishsk. I assume that will be in the [show notes 00:26:31]. I pontificate some time on technology, on cooking every now and again, on Friday before the end of the weekend, a little bit of politics, but you can find me @maishsk on Twitter. Or maishsk everywhere else social that's possible.Corey: Excellent. We will toss links to that, of course, in the [show notes 00:26:50]. Thank you so much for being so generous with your time. I appreciate it.Maish: Thank you very much, Corey. It was fun.Corey: Maish Saidel-Keesing, EntReloper of container services at AWS. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated it, please leave a five-star review on your podcast platform of choice along with an angry comment that your 5000 enterprise developer colleagues can all pile on.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

In this episode of AWS Techchat, we started by talking about foundations, where we spoke about an overview of EventBridge and how it is different from CloudWatch Events. Then we talked about some of the features such as Archive and replay, Schema Registry, Global Endpoints and API Destinations And finally we dove into architecture patterns. Here we touched on the need to spend time modeling your logical architecture to get a good foundation for your event-driven architecture and explored event bus topologies and best practices. Speakers Shai Perednik - Global Tech Lead - Blockchain Cheryl Joseph - Solutions Architect, AWS Stephen Liedig - Principal SA - Serverless, AWS Resources *Amazon EventBridge resource policy samples* https://github.com/aws-samples/amazon-eventbridge-resource-policy-samples *AWS re:Invent 2020 session* Building event-driven applications with Amazon EventBridge (https://youtu.be/Wk0FoXTUEjo) *Introducing global endpoints for Amazon EventBridge* https://aws.amazon.com/blogs/compute/introducing-global-endpoints-for-amazon-eventbridge/ *ANZ Summit: Design event-driven integrations using Amazon EventBridge (Day 2)* * AWS Summit regisration (https://aws.amazon.com/events/summits/anz/) * Agenda at a glance (https://pages.awscloud.com/rs/112-TZM-766/images/AWS-Summit-ANZ-2022-Agenda.pdf) Blog Post * Building an event-driven application with Amazon EventBridge (https://aws.amazon.com/blogs/compute/building-an-event-driven-application-with-amazon-eventbridge/)

On The Cloud Pod this week, the team establishes that Justin may be immune to COVID. Plus all the latest from the AWS Summit, Azure Red Button team up on DDOS defense, and engines are revving in the great VMware showdown.  A big thanks to this week's sponsor, 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. This week's highlights

Holy Sh*t - The performance 23andMe saw on the AWS cloud nearly seems like science-FICTION. Bob & Josh are live from AWS Summit and discuss our customer 23andMe's presentation on leveraging AWS for ultimate flexibility.