This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Evan Phoenix of Miren about why deployment is still painful, what teams keep getting wrong when they try to simplify it, and why small teams may need better defaults more than more platform knobs.Evan is the CEO of Miren. He previously worked on Terraform Enterprise and Waypoint at HashiCorp, and he also built Puma and Rubinius.We talk about deployment as the “final boss” of software delivery. Not because teams do not know how to ship code, but because deployment is where everything collides: runtimes, registries, secrets, networking, cloud services, databases, rollbacks, and the internal platform nobody wants to touch anymore.A big theme is opinionated tooling. Engineers often say they want flexibility, but many teams are really asking for good defaults, a clear happy path, and fewer decisions to own.We also get into Terraform Enterprise, Terraform Cloud, Terragrunt, OpenTofu, Waypoint, Kubernetes, Heroku, ECS, container registries, and how AI changes the deployment conversation. AI can generate infrastructure code, but when that setup breaks, someone still has to understand it and be on call for it.Highlights• Why deployment is still painful after years of platforms and abstractions• What Evan learned from Terraform Enterprise and Waypoint• Why Terraform structure, state, modules, and repo layout remain hard• Why OpenTofu gained traction beyond the Terraform licensing change• Why Kubernetes can be too much surface area for some teams• What small teams actually need from deployment tooling• How AI changes infrastructure and deployment workflows• Why generated infrastructure still needs ownership and accountabilityLinks• Miren: https://miren.dev• Miren on GitHub: https://github.com/mirendev• Evan Phoenix: https://evanphx.dev• Evan on Bluesky: https://bsky.app/profile/evanphx.dev• Evan on Linkedin: https://www.linkedin.com/in/evanphoenix/Things mentioned• Terraform Enterprise: https://developer.hashicorp.com/terraform/enterprise• Terraform Cloud: https://developer.hashicorp.com/terraform/cloud-docs• Terragrunt: https://terragrunt.gruntwork.io• OpenTofu: https://opentofu.org• HashiCorp Waypoint: https://github.com/hashicorp/waypoint• Knative: https://knative.devOur linksMore episodes + show notes: https://shipitweekly.fmOn Call Brief: https://oncallbrief.com

This week on Ship It Weekly: Amazon Q Developer and the AWS language servers had a pair of trust-boundary CVEs, JFrog found hijacked npm and Go packages using hidden VS Code tasks to run malware when a workspace opens, AWS WAF had HTTP/2 request-body inspection issues, and AWS introduced Lambda MicroVMs for running user-generated and AI-generated code in isolated sandboxes.The bigger theme: execution is the boundary now. The repo, the IDE, the AI assistant, the WAF, and the sandbox all sit at the point where something gets to run, inspect, block, or decide. Before execution, trust is a policy. After execution, trust is a blast radius.In the lightning round, Brian covers GitHub’s record advisory volume, Git 2.55, Valkey 9.1 on Amazon ElastiCache, and a quick Fable 5 callback now that Anthropic’s Fable 5 is back online.LinksAWS security bulletin: Amazon Q / AWS language server CVEs https://aws.amazon.com/security/security-bulletins/2026-047-aws/JFrog: Hijacked npm packages using VS Code tasks https://research.jfrog.com/post/hijacked-npm-vscode-tasks-blockchain/AWS security bulletin: AWS WAF HTTP/2 inspection issues https://aws.amazon.com/security/security-bulletins/2026-048-aws/AWS Lambda MicroVMs https://aws.amazon.com/blogs/aws/run-isolated-sandboxes-with-full-lifecycle-control-aws-lambda-introduces-microvms/GitHub Advisory Database record volume https://github.blog/security/supply-chain-security/inside-the-advisory-database-and-what-happens-when-vulnerability-volume-breaks-records/Git 2.55 highlights https://github.blog/open-source/git/highlights-from-git-2-55/Amazon ElastiCache Valkey 9.1 https://aws.amazon.com/blogs/database/announcing-valkey-9-1-for-amazon-elasticache/Claude Fable 5 and Mythos 5 model docs https://platform.claude.com/docs/en/about-claude/models/introducing-claude-fable-5-and-claude-mythos-5This week’s On Call Brief https://www.tellerstech.com/on-call-brief-news/2026-W27/More episodes and full show notes https://shipitweekly.fm/

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Kat Traxler of Vectra AI about AI security, the zero-day clock, IAM, cloud risk, AI-assisted bug hunting, and why the scariest future security problems may still start with the boring fundamentals teams already struggle with today.Kat is a Principal Security Researcher at Vectra AI focused on abuse techniques and vulnerabilities in the public cloud, especially around the intersection of cloud security, AppSec, IAM, managed identities, and insecure-by-design flaws.We talk about the current AI security mood, from the excitement around faster research and bug hunting to the fear that AI could shrink the window between vulnerability disclosure and exploitation. Kat explains the “San Francisco Consensus,” why the zero-day clock is getting so much attention, and why she thinks the facts may be real while some of the conclusions are overextended.The bigger theme here is that AI is absolutely changing security work, but it does not erase the fundamentals. Attackers still take the lowest-friction path that works. For most teams, that still means credentials, IAM, misconfigurations, known vulnerabilities, and systems that were never threat-modeled as deeply as people assume.Highlights• Why AI security feels exciting and unsettling at the same time• What the “San Francisco Consensus” means and why people are talking about the zero-day clock• How AI may shrink the time between vulnerability disclosure and exploitation• Why Kat is skeptical of the full “zero-day apocalypse” narrative• Why credentials, IAM, misconfigurations, and known vulnerabilities still matter most for many teams• How AI helps narrow the search space in bug hunting and security research• Where AI is useful for code-level bugs, and where it still struggles with context and threat modeling• Why human expertise still matters when using AI for writing, research, and cloud security analysis• Why IAM remains hard because it sits at the intersection of people, access, and technology• What insecure-by-design flaws are, and why AI may not solve those anytime soonKat / Vectra AI links• Kat Traxler at Vectra AI: https://www.vectra.ai/about/author/kat-traxler• Kat’s site: https://kattraxler.cloud/• The San Francisco Consensus: https://kattraxler.cloud/the-san-francisco-consensus/• Kat on X: https://x.com/NightmareJS• Vectra AI: https://www.vectra.ai/Our linksMore episodes + show notes + links: https://shipitweekly.fmOn Call Brief: https://oncallbrief.com

This week on Ship It Weekly: containerd disclosed a batch of CRI plugin vulnerabilities, Datadog tested PostgreSQL high availability on Kubernetes and found that failover is not useful if it cannot happen safely, AWS DevOps Agent and Datadog MCP Server moved AI incident response closer to real production workflows, and Amazon EKS added customer-routed control-plane egress.The bigger theme: the control plane keeps getting wider. Runtimes, databases, incident agents, API-server egress, credentials, the cloud console, and object metadata are all becoming part of the production blast radius. And when something breaks, users do not experience your architecture diagram. They experience waiting.In the lightning round, Brian covers GitHub self-service credential revocation for incident response, AWS Management Console Private Access without internet connectivity, Vercel Connect and short-lived agent credentials, and Amazon S3 annotations.Linkscontainerd CRI plugin vulnerabilities / AWS security bulletin https://aws.amazon.com/security/security-bulletins/2026-046-aws/Datadog: PostgreSQL high availability on Kubernetes https://www.datadoghq.com/blog/engineering/postgresql-ha-kubernetes/AWS DevOps Agent and Datadog MCP Server https://aws.amazon.com/blogs/devops/production-ready-autonomous-incident-resolution-with-aws-devops-agent-now-ga-and-datadog-mcp-server/Amazon EKS customer-routed control-plane egress https://aws.amazon.com/blogs/containers/amazon-eks-now-supports-control-plane-egress-through-your-vpc/GitHub self-service credential revocation for incident response https://github.blog/changelog/2026-06-24-self-service-credential-revocation-for-incident-response/AWS Management Console Private Access https://aws.amazon.com/about-aws/whats-new/2026/06/aws-management-console-private/Vercel Connect https://vercel.com/blog/introducing-vercel-connectAmazon S3 annotations https://aws.amazon.com/blogs/aws/amazon-s3-annotations-attach-rich-queryable-context-directly-to-your-objects/Marc Brooker: Waiting, latency, MTTR, and the inspection paradox https://brooker.co.za/blog/2026/06/19/waiting.htmlThis week’s On Call Brief https://www.tellerstech.com/on-call-brief-news/2026-W26/More episodes and full show notes https://www.shipitweekly.fm

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Joel DeStefano from Guardsquare about mobile app security, why it is different from backend and cloud security, and why scanning alone is not enough once an app is shipped into the real world.We talk about the shift in trust model that happens with mobile apps. In backend and cloud systems, teams usually have more control over the runtime, infrastructure, policies, and monitoring. With mobile, the app becomes a public artifact running on someone else’s device, in an environment you do not fully control.The bigger theme here is that mobile security is not just “scan it before release.” Scanning matters, but teams also need to think about app hardening, obfuscation, runtime protection, monitoring, and whether the app connecting back to their APIs is genuine and uncompromised.Highlights• Why mobile changes the trust model compared to backend and cloud systems• What DevOps, SRE, and platform teams should understand about mobile app risk• Why scanning is useful, but not enough by itself• The danger of assuming app store approval means an app is secure• Why “we do not store sensitive data in the app” can be a misleading security argument• How attackers can reverse engineer apps, inspect workflows, and learn how the app talks to backend APIs• What code hardening and obfuscation actually help protect against• Why runtime checks matter for rooted devices, compromised environments, debuggers, hooking frameworks, overlays, and accessibility abuse• The difference between Android and iOS security assumptions• Why the OS is not responsible for protecting your app’s business logic• How mobile security should fit into CI/CD without destroying release velocity• What should block a release versus what should become tracked risk• Why testing, hardening, runtime protection, and monitoring should work together as one strategy• How AI may speed up attackers without fundamentally changing the need for strong security fundamentals• Joel’s advice for improving mobile security posture: start with the app’s critical workflows, backend interactions, and real business riskJoel / Guardsquare links• Guardsquare: https://hubs.ly/Q04fJgkJ0• Guardsquare Blog: https://www.guardsquare.com/blogOWASP mobile security links• OWASP Mobile Application Security: https://owasp.org/www-project-mobile-app-security/• OWASP MASVS: https://mas.owasp.org/MASVS/Our linksMore episodes + show notes + links: https://shipitweekly.fmOn Call Brief: https://oncallbrief.com

This episode of Ship It Weekly is about default trust getting punished. Brian covers Oracle’s emergency PeopleSoft advisory for CVE-2026-35273, npm v12 changing install-script defaults, GitHub Agentic Workflows moving away from long-lived personal access tokens, and Anthropic disabling Fable 5 and Mythos 5 after a U.S. export-control directive. The common thread: legacy ERP systems, package installs, CI/CD agents, and AI models all become production risks when teams trust the default without checking what that trust can actually do.In the lightning round, Brian covers Tekton CloudEvents moving to a dedicated events controller, NVIDIA Triton Inference Server 26.04 changing inference defaults, AWS Nitro Isolation Engine bringing formal verification to Graviton5-based isolation, and Homebrew 6.0 adding explicit trust for third-party taps. The bigger theme: production does not care why you trusted the default. It only cares what that default was allowed to do.The bigger theme: production does not care why you trusted the default. It only cares what that default was allowed to do.LinksOracle PeopleSoft CVE-2026-35273 advisory https://www.oracle.com/security-alerts/alert-cve-2026-35273.htmlnpm v12 breaking changes https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/GitHub Agentic Workflows no longer need PATs https://github.blog/changelog/2026-06-11-agentic-workflows-no-longer-need-a-personal-access-token/Anthropic Fable 5 / Mythos 5 access statement https://www.anthropic.com/news/fable-mythos-accessTekton Pipelines releases https://github.com/tektoncd/pipeline/releasesNVIDIA Triton Inference Server 26.04 release notes https://docs.nvidia.com/deeplearning/triton-inference-server/release-notes/rel-26-04.htmlAWS Nitro Isolation Engine https://aws.amazon.com/blogs/compute/aws-nitro-isolation-engine-formally-verifying-the-hypervisor-in-the-aws-nitro-system/Homebrew 6.0.0 https://brew.sh/2026/06/11/homebrew-6.0.0/This week’s On Call Brief https://www.tellerstech.com/on-call-brief-news/2026-W25/More episodes and show notes https://shipitweekly.fm/

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Francois Richard, Engineering Director at Meta, about reliability at scale, how AI is changing production risk, what teams actually learn from incidents, and why recovery practice matters just as much as prevention.We talk about the proactive and reactive sides of reliability, why SLOs should represent a promise to users instead of just another dashboard number, how incident reviews should drive real system improvements, and how teams can practice recovery before production forces the lesson on them.The bigger theme here is that reliability is not just about avoiding failure. It is about knowing what happens when prevention fails. That means practicing regional failure, understanding overload behavior, improving incident response, using AI carefully during investigation, and making reliability targets match the actual lifecycle and importance of the system.Highlights• Why reliability work starts with both prevention and recovery• The difference between reactive incident response and proactive reliability engineering• How Meta thinks about disaster recovery testing and regional failure practice• Why an SLO should be treated like a promise to users, not just a dashboard metric• How SLO trends help teams decide when to invest more in reliability or take more product risk• What engineers actually learn during the “pressure cooker” of an incident• Why incident reviews should produce follow-up work, not just a nicer explanation of what broke• The difference between finding the cause of an incident and improving the system• Where AI agents can help with incident investigation, telemetry, metrics, and query building• Why AI-generated code can increase change volume while reducing human context• How faster code generation changes the kinds of reliability problems teams should expect• Why recovery practice matters, especially for region loss, traffic spikes, overload, and restart behavior• What smaller DevOps and SRE teams can learn from Meta-scale reliability patterns• Why not every system needs six nines, especially early in a product lifecycle• How to think about reliability investment based on user promise, product maturity, and operational risk• Why At Scale Systems & Reliability is focused on the infrastructure behind AI and the use of AI to operate large-scale systemsFrancois’ links• LinkedIn: https://www.linkedin.com/in/francoisrichard/At Scale links• Systems & Reliability 2026: https://bit.ly/4xd2FdG• At Scale Conferences: https://atscaleconference.com/Our linksMore episodes + show notes + links: https://shipitweekly.fmOn Call Brief: https://oncallbrief.com

This episode of Ship It Weekly is about the hidden glue holding production together.Brian covers Coinbase’s May 7 outage postmortem, where an AWS us-east-1 cooling failure exposed the difference between being “multi-AZ” on paper and actually being able to recover when stateful, low-latency systems are tied to a failed zone.Then he looks at Meta’s AI-assisted Instagram support issue and why account recovery is identity infrastructure, not just customer support. If AI can influence password resets, email changes, MFA resets, or account ownership flows, that workflow needs to be treated like a production control plane.The episode also covers AWS AgentCore CLI CVE-2026-11393, where collaborator metadata could break out into generated Python code during agent import, and an Apigee cross-tenant issue from Google’s Apigee security bulletins that shows why tenant isolation has to be tested beyond the obvious happy path.LinksCoinbase May 7 outage postmortem https://www.coinbase.com/blog/a-postmortem-of-our-may-7-2026-outageMeta AI support / Instagram account recovery reporting https://www.theverge.com/tech/945658/meta-ai-support-chatbot-exploit-instagram-accountsAWS AgentCore CLI CVE-2026-11393 https://aws.amazon.com/security/security-bulletins/2026-040-aws/AgentCore CLI GitHub advisory https://github.com/aws/agentcore-cli/security/advisories/GHSA-m4x6-gwgp-4pm7Google Apigee security bulletins https://docs.cloud.google.com/apigee/docs/security-bulletins/security-bulletinsCloudflare real-time threat intel WAF rules https://blog.cloudflare.com/realtime-threat-intel-waf-rules/AWS Lambda tenant isolation with event source mappings https://aws.amazon.com/blogs/compute/integrating-event-source-mappings-with-aws-lambda-tenant-isolation-mode/Amazon OpenSearch Serverless next generation https://aws.amazon.com/about-aws/whats-new/2026/05/amazon-opensearch-serverless-next-generation-generally-available/GitHub Enterprise Managed Users IP allow list coverage https://github.blog/changelog/2026-06-08-ip-allow-list-coverage-for-emu-namespaces-in-general-availability/This week’s On Call Brief https://www.tellerstech.com/on-call-brief-news/2026-W24/More episodes and show notes https://shipitweekly.fm/

This episode of Ship It Weekly is about automation’s hidden boundaries. Brian covers Kiro CLI CVE-2026-9255, where piped stdin could act like user approval, Amazon Braket SDK CVE-2026-9291 and the very normal Python pickle risk hiding inside quantum job results, AWS Organizations finally emitting CloudTrail events when accounts join or leave an org, and KEDA updates that remind us autoscaling upgrades are production behavior changes.The bigger thread this week is that automation does not remove boundaries. It moves them. Approval paths, trusted data, account membership, scaling signals, platform access, and AI-generated output all need clear ownership and visibility.Brian also covers Kubernetes Dashboard being archived with Headlamp as the path forward, Google Cloud Remote MCP Server for AlloyDB, Apache Kafka 4.3.0, and Atlassian’s AI-native SDLC productivity claims.Sponsored by @Scale: Systems & Reliability, happening June 25 at the Meydenbauer Center in Bellevue, Washington. Register at https://bit.ly/4xd2FdGLinksKiro CLI CVE-2026-9255 https://aws.amazon.com/security/security-bulletins/2026-035-aws/Amazon Braket SDK CVE-2026-9291 https://aws.amazon.com/security/security-bulletins/2026-036-aws/AWS Organizations CloudTrail account events https://aws.amazon.com/about-aws/whats-new/2026/05/aws-organizations-cloudtrail/KEDA v2.20.0 release https://github.com/kedacore/keda/releases/tag/v2.20.0KEDA v2.19.0 release https://github.com/kedacore/keda/releases/tag/v2.19.0Kubernetes Dashboard archived / Headlamp path forward https://kubernetes.io/blog/2026/06/04/dashboard-archived-what-now/Google Cloud Remote MCP Server for AlloyDB https://cloud.google.com/blog/products/databases/alloydb-remote-mcp-server-now-gaApache Kafka 4.3.0 https://www.confluent.io/blog/apache-kafka-4-3-release-announcement/Atlassian AI-native SDLC productivity claims https://www.atlassian.com/blog/software-teams/ai-native-sdlcThis week’s On Call Brief https://www.tellerstech.com/on-call-brief/2026-W23/More episodes and show notes https://shipitweekly.fm/

This episode of Ship It Weekly is about trusted tools becoming production dependencies. Brian covers a rough GitHub supply chain week, including the compromised Nx Console VS Code extension tied to exposed GitHub internal repositories and the Megalodon campaign abusing GitHub Actions workflows across thousands of public repos.The bigger thread this week is that the tools around production are increasingly part of production. Brian also covers Railway’s GCP account suspension outage, Discord’s voice outage during a Kubernetes migration, AWS changing SDK retry behavior, CVE-2026-9133 in the RabbitMQ AWS plugin, and a Reddit story about stolen AWS keys turning into a $14,000 Bedrock bill.Brian also touches on OpenTelemetry graduating from the CNCF, Claude Code security risk, GitLab Secrets Manager, Google Cloud AI spend caps, and a Redshift Python driver RCE.Full source list and extra links are available on this episode’s page at shipitweekly.fm.LinksNx Console compromise https://www.stepsecurity.io/blog/nx-console-vs-code-extension-compromisedMegalodon GitHub Actions attack https://www.stepsecurity.io/blog/megalodon-mass-github-actions-secret-exfiltration-across-5-500-public-repositoriesRailway GCP outage https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outageDiscord voice outage https://discord.com/blog/behind-the-scenes-of-the-3-25-26-voice-outageAWS SDK retry changes https://aws.amazon.com/blogs/developer/announcing-updated-retry-behavior-for-aws-sdks-and-tools/RabbitMQ AWS plugin CVE-2026-9133 https://aws.amazon.com/security/security-bulletins/2026-034-aws/AWS Bedrock cost spike Reddit thread https://www.reddit.com/r/aws/comments/1tm3ydo/aws_bedrock_cost_spike_14000_usd/This week’s On Call Brief https://www.tellerstech.com/on-call-brief/2026-W22/More episodes and show notes https://shipitweekly.fm/