Podcasts about chatops

In this episode of the Identity at the Center podcast, hosts Jeff and Jim dive into the concept of Identity Security Posture Management (ISPM) with Henrique Teixeira, Senior Vice President of Strategy at Saviynt and former Gartner analyst. Henrique explains ISPM as an Apple Watch for your identity program, focusing on preventive measures before an attack occurs. The discussion also covers the upcoming Gartner IAM Summit, AI's impact on identity management, and the anticipated trends for 2025. Additionally, they explore the differences between AI copilot, agent, and bot, and the future of non-human identity management. Henrique shares insights on balancing ITSM front ends with IGA systems and emphasizes the importance of continuous security investment. Tune in for a comprehensive look at ISPM, AI, and the evolving identity security landscape. Chapters 00:00 Welcome to the Podcast 01:47 Gartner IAM Summit Preview 04:48 Guest Introduction: Henrique Teixeira 05:28 Henrique's Career Transition 10:12 Conference Experiences and Insights 14:10 Understanding ISPM and ITDR 29:16 AI in Identity Management 35:58 Debating the Future of AI in IGA Systems 37:09 Evolution of Access Request Systems 37:59 The Rise of ChatOps in Identity Management 40:26 Multi-Channel Identity and Access Management 45:54 Influencers and Inspirations in Identity Strategy 49:06 Reflecting on 2024: Trends and Predictions 54:31 Looking Ahead: Identity and AI in 2025 01:02:50 Boxing Talk: Mike Tyson vs. Jake Paul 01:08:17 Wrapping Up: Final Thoughts and Farewells Connect with Henrique: https://www.linkedin.com/in/bernardes Learn more about Saviynt: https://saviynt.com/ Prevention + ITDR Venn Diagram - https://www.linkedin.com/posts/rezasoltani_identitysecurity-ispm-itdr-activity-7203522819014500353-8Kv_/ Connect with us on LinkedIn: Jim McDonald: https://www.linkedin.com/in/jimmcdonaldpmp/ Jeff Steadman: https://www.linkedin.com/in/jeffsteadman/ Visit the show on the web at http://idacpodcast.com Keywords: Identity Security, IAM, Digital Identity, AI, Artificial Intelligence, ISPM, ITDR, IGA, Gartner IAM Summit, Cybersecurity, Cloud Security, Machine Identity, Non-Human Identity, Podcast, Interview, Saviynt, Henrique Teixeira, Jim McDonald, Jeff Steadman

We didn't expect this from ChatOps! Keep watching until we implement an AI assistant for data filtering in under 60 seconds!This episode is all about productivity. Andrew Zigler, Developer Advocate at Mattermost, shares his top tips for using tech to improve your efficiency. Andrew explains ChatOps – a chat-based collaboration with automated workflows to make work easier and faster – and shares examples of how it's enhanced his productivity. He also shows how to embed AI into chat platforms to summarize messages, craft responses, and support decision-making. ❓What did you think of the show? Leave your anonymous feedback:https://forms.gle/Df5sDABiNMQn4YSj7CONNECT WITH ANDREW ZIGLER

В новом выпуске linkmeup sysadmins мы обсудим, можно ли строить сервисы, не имея серверов? Для каких сервисов годится такой подход, как при этом быть с масштабированием, контролем состояний, сетями и прочее. В гостях у нас ярый адвокат и знаток методик Serverless Антон Черноусов. Подробнее, о чем мы планируем говорить: Что такое Serverless. Базовый сервис — FaaS (функции, события и интеграции). Когда и кто первый раз рассказал про FaaS и Serverless? Почему разработчиков тригерит термин Serverless? Преимущества и недостатки Serverless. Экономию ресурсов, гибкость, масштабируемость. Ограничения на время выполнения и управление зависимостями. Массовые примеры использования Serverless. обработка изображений реализация чатов ChatOps Как условно работает серверлесс функция Как производится запуск Как производится оптимизация Как работает шедулер Как быть с сетью Serverless vs Traditional Architecture. Обсуждение преимуществ и недостатков обоих подходов. Сложность отладки и тестирования Проблемы безопасности Зависимость от провайдера Непредсказуемость расходов Проблемы с масштабированием Сложность управления Ограниченные возможности Сообщение sysadmins №43. Serverless. Правда или конь в вакууме? появились сначала на linkmeup.

AI is at the center of many tech conversations these days. How will it potentially impact the Cloud-native ecosystem now, and into the future?  SHOW: 716CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Upland Software: Modern, secure fax solutions for businesses of all sizes.Digital transformation that safeguards sensitive information. Upland Software's got the goods.Find "Breaking Analysis Podcast with Dave Vellante" on Apple, Google and SpotifyKeep up to data with Enterprise Tech with theCUBESHOW NOTES:Discussing AI in the Cloud-native Ecosystem (theCUBE at KubeConEU 2023)What's New - OPAL Co-Pilot Powered by GPT (from Observ)Honeycomb Query Assistant (Honeycomb)Using ChatGPT to document your software project (Aista)Tech Assistant for Writing Code (StarCoder)HOW WILL AI PLAY A ROLE IN CLOUD-NATIVE IT AND DEVELOPMENT?Who will build models?Where will the data/model be located?Does the vendor vs. open source dynamic change when data models are involved? What risks need to be mitigated?THERE'S SOMETHING FOR (MOSTLY EVERYBODY). EVERYBODY WILL HAVE A DIFFERENT VIEWPOINT ON THE SHOW.Writing documentationConfiguration generationConfiguration Best-Practices - Interactions with Docs | Consulting SystemsInteractive Support - Bots, ChatOps, etcAIOps - Self-correcting, self-adjusting systemsChaos EngineeringLog Interpretation and RemediationWriting Code | Pair Programming  FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

Cette semaine, nous parlons de HTTP/3 et de QUIC, mais pas que. Nous parlerons de S3 et DynamoDB, nous jeterons un regard rétrospectif sur 10 années d'évolution de EBS. Enfin, je vous indiquerai un nouveau moyen de bloquer les attaques sur la page d'authentification de vos apps. On parlera DevOps aussi - ou de ChatOps plus précisement.

Cette semaine, nous parlons de HTTP/3 et de QUIC, mais pas que. Nous parlerons de S3 et DynamoDB, nous jeterons un regard rétrospectif sur 10 années d'évolution de EBS. Enfin, je vous indiquerai un nouveau moyen de bloquer les attaques sur la page d'authentification de vos apps. On parlera DevOps aussi - ou de ChatOps plus précisement.

About ChrisChris Short has been a proponent of open source solutions throughout his over two decades in various IT disciplines, including systems, security, networks, DevOps management, and cloud native advocacy across the public and private sectors. He currently works on the Kubernetes team at Amazon Web Services and is an active Kubernetes contributor and Co-chair of OpenGitOps. Chris is a disabled US Air Force veteran living with his wife and son in Greater Metro Detroit. Chris writes about Cloud Native, DevOps, and other topics at ChrisShort.net. He also runs the Cloud Native, DevOps, GitOps, Open Source, industry news, and culture focused newsletter DevOps'ish.Links Referenced: DevOps'ish: https://devopsish.com/ EKS News: https://eks.news/ Containers from the Couch: https://containersfromthecouch.com opengitops.dev: https://opengitops.dev ChrisShort.net: https://chrisshort.net Twitter: https://twitter.com/ChrisShort 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. Coming back to us since episode two—it's always nice to go back and see the where are they now type of approach—I am joined by Senior Developer Advocate at AWS Chris Short. Chris, been a few years. How has it been?Chris: Ha. Corey, we have talked outside of the podcast. But it's been good. For those that have been listening, I think when we recorded I wasn't even—like, when was season two, what year was that? [laugh].Corey: Episode two was first pre-pandemic and the rest. I believe—Chris: Oh. So, yeah. I was at Red Hat, maybe, when I—yeah.Corey: Yeah. You were doing Red Hat stuff, back when you got to work on open-source stuff, as opposed to now, where you're not within 1000 miles of that stuff, right?Chris: Actually well, no. So, to be clear, I'm on the EKS team, the Kubernetes team here at AWS. So, when I joined AWS in October, they were like, “Hey, you do open-source stuff. We like that. Do more.” And I was like, “Oh, wait, do more?” And they were like, “Yes, do more.” “Okay.”So, since joining AWS, I've probably done more open-source work than the three years at Red Hat that I did. So, that's kind of—you know, like, it's an interesting point when I talk to people about it because the first couple months are, like—you know, my friends are like, “So, are you liking it? Are you enjoying it? What's going on?” And—Corey: Do they beat you with reeds? Like, all the questions people have about companies? Because—Chris: Right. Like, I get a lot of random questions about Amazon and AWS that I don't know the answer to.Corey: Oh, when I started telling people, I fixed Amazon bills, I had to quickly pivot that to AWS bills because people started asking me, “Well, can you save me money on underpants?” It's I—Chris: Yeah.Corey: How do you—fine. Get the prime credit card. It docks 5% off the bill, so there you go. But other than that, no, I can't.Chris: No.Corey: It's—Chris: Like, I had to call my bank this morning about a transaction that I didn't recognize, and it was from Amazon. And I was like, that's weird. Why would that—Corey: Money just flows one direction, and that's the wrong direction from my employer.Chris: Yeah. Like, what is going on here? It shouldn't have been on that card kind of thing. And I had to explain to the person on the phone that I do work at Amazon but under the Web Services team. And he was like, “Oh, so you're in IT?”And I'm like, “No.” [laugh]. “It's actually this big company. That—it's a cloud company.” And they're like, “Oh, okay, okay. Yeah. The cloud. Got it.” [laugh]. So, it's interesting talking to people about, “I work at Amazon.” “Oh, my son works at Amazon distribution center,” blah, blah, blah. It's like, cool. “I know about that, but very little. I do this.”Corey: Your son works in Amazon distribution center. Is he a robot? Is normally my next question on that? Yeah. That's neither here nor there.So, you and I started talking a while back. We both write newsletters that go to a somewhat similar audience. You write DevOps'ish. I write Last Week in AWS. And recently, you also have started EKS News because, yeah, the one thing I look at when I'm doing these newsletters every week is, you know what I want to do? That's right. Write more newsletters.Chris: [laugh].Corey: So, you are just a glutton for punishment? And, yeah, welcome to the addiction, I suppose. How's it been going for you?Chris: It's actually been pretty interesting, right? Like, we haven't pushed it very hard. We're now starting to include it in things. Like we did Container Day; we made sure that EKS news was on the landing page for Container Day at KubeCon EU. And you know, it's kind of just grown organically since then.But it was one of those things where it's like, internally—this happened at Red Hat, right—when I started live streaming at Red Hat, the ultimate goal was to do our product management—like, here's what's new in the next version thing—do those live so anybody can see that at any point in time anywhere on Earth, the second it's available. Similar situation to here. This newsletter actually is generated as part of a report my boss puts together to brief our other DAs—or developer advocates—you know, our solutions architects, the whole nine yards about new EKS features. So, I was like, why can't we just flip that into a weekly newsletter, you know? Like, I can pull from the same sources you can.And what's interesting is, he only does the meeting bi-weekly. So, there's some weeks where it's just all me doing it and he ends up just kind of copying and pasting the newsletter into his document, [laugh] and then adds on for the week. But that report meeting for that team is now getting disseminated to essentially anyone that subscribes to eks.news. Just go to the site, there's a subscribe thing right there. And we've gotten 20 issues in and it's gotten rave reviews, right?Corey: I have been a subscriber for a while. I will say that it has less Chris Short personality—Chris: Mm-hm.Corey: —to it than DevOps'ish does, which I have to assume is by design. A lot of The Duckbill Group's marketing these days is no longer in my voice, rather intentionally, because it turns out that being a sarcastic jackass and doing half-billion dollar AWS contracts can not to be the most congruent thing in the world. So okay, we're slowly ameliorating that. It's professional voice versus snarky voice.Chris: Well, and here's the thing, right? Like, I realized this year with DevOps'ish that, like, if I want to take a week off, I have to do, like, what you did when your child was born. You hired folks to like, do the newsletter for you, or I actually don't do the newsletter, right? It's binary: hire someone else to do it, or don't do it. So, the way I structured this newsletter was that any developer advocate on my team could jump in and take over the newsletter so that, you know, if I'm off that week, or whatever may be happening, I, Chris Short, am not the voice. It is now the entire developer advocate team.Corey: I will challenge you on that a bit. Because it's not Chris Short voice, that's for sure, but it's also not official AWS brand voice either.Chris: No.Corey: It is clearly written by a human being who is used to communicating with the audience for whom it is written. And that is no small thing. Normally, when oh, there's a corporate newsletter; that's just a lot of words to say it's bad. This one is good. I want to be very clear on that.Chris: Yeah, I mean, we have just, like, DevOps'ish, we have sections, just like your newsletter, there's certain sections, so any new, what's new announcements, those go in automatically. So, like, that can get delivered to your inbox every Friday. Same thing with new blog posts about anything containers related to EKS, those will be in there, then Containers from the Couch, our streaming platform, essentially, for all things Kubernetes. Those videos go in.And then there's some ecosystem news as well that I collect and put in the newsletter to give people a broader sense of what's going on out there in Kubernetes-land because let's face it, there's upstream and then there's downstream, and sometimes those aren't in sync, and that's normal. That's how Kubernetes kind of works sometimes. If you're running upstream Kubernetes, you are awesome. I appreciate you, but I feel like that would cause more problems and it's worse sometimes.Corey: Thank you for being the trailblazers. The rest of us can learn from your misfortune.Chris: [laugh]. Yeah, exactly. Right? Like, please file your bugs accordingly. [laugh].Corey: EKS is interesting to me because I don't see a lot of it, which is, probably, going to get a whole lot of, “Wait, what?” Moments because wait, don't you deal with very large AWS bills? And I do. But what I mean by that is that EKS, until you're using its Fargate expression, charges for the control plane, which rounds to no money, and the rest is running on EC2 instances running in a company's account. From the billing perspective, there is no difference between, “We're running massive fleets of EKS nodes.” And, “We're managing a whole bunch of EC2 instances by hand.”And that feels like an interesting allegory for how Kubernetes winds up expressing itself to cloud providers. Because from a billing perspective, it just looks like one big single-tenant application that has some really strange behaviors internally. It gets very chatty across AZs when there's no reason to, and whatnot. And it becomes a very interesting study in how to expose aspects of what's going on inside of those containers and inside of the Kubernetes environment to the cloud provider in a way that becomes actionable. There are no good answers for this yet, but it's something I've been seeing a lot of. Like, “Oh, I thought you'd be running Kubernetes. Oh, wait, you are and I just keep forgetting what I'm looking at sometimes.”Chris: So, that's an interesting point. The billing is kind of like, yeah, it's just compute, right? So—Corey: And my insight into AWS and the way I start thinking about it is always from a billing perspective. That's great. It's because that means the more expensive the services, the more I know about it. It's like, “IAM. What is that?” Like, “Oh, I have no idea. It's free. How important could it be?” Professional advice: do not take that philosophy, ever.Chris: [laugh]. No. Ever. No.Corey: Security: it matters. Oh, my God. It's like you're all stars. Your IAM policy should not be. I digress.Chris: Right. Yeah. Anyways, so two points I want to make real quick on that is, one, we've recently released an open-source project called Carpenter, which is really cool in my purview because it looks at your Kubernetes file and says, “Oh, you want this to run on ARM instance.” And you can even go so far as to say, right, here's my limits, and it'll find an instance that fits those limits and add that to your cluster automatically. Run your pod on that compute as long as it needs to run and then if it's done, it'll downsize—eventually, kind of thing—your cluster.So, you can basically just throw a bunch of workloads at it, and it'll auto-detect what kind of compute you will need and then provision it for you, run it, and then be done. So, that is one-way folks are probably starting to save money running EKS is to adopt Carpenter as your autoscaler as opposed to the inbuilt Kubernetes autoscaler. Because this is instance-aware, essentially, so it can say, like, “Oh, your massive ARM application can run here,” because you know, thank you, Graviton. We have those processors in-house. And you know, you can run your ARM64 instances, you can run all the Intel workloads you want, and it'll right size the compute for your workloads.And I'll look at one container or all your containers, however you want to configure it. Secondly, the good folks over at Kubecost have opencost, which is the open-source version of Kubecost, basically. So, they have a service that you can run in your clusters that will help you say, “Hey, maybe this one notes too heavy; maybe this one notes too light,” and you know, give you some insights into Kubernetes spend that are a little bit more granular as far as usage and things like that go. So, those two projects right there, I feel like, will give folks an optimal savings experience when it comes to Kubernetes. But to your point, it's just compute, right? And that's really how we treat it, kind of, here internally is that it's a way to run… compute, Kubernetes, or ECS, or any of those tools.Corey: A fairly expensive one because ignoring entirely for a second the actual raw cost of compute, you also have the other side of it, which is in every environment, unless you are doing something very strange or pre-funding as a one-person startup in your spare time, your payroll costs will it—should—exceed your AWS bill by a fairly healthy amount. And engineering time is always more expensive than services time. So, for example, looking at EKS, I would absolutely recommend people use that rather than rolling their own because—Chris: Rolling their own? Yeah.Corey: —get out of that engineering space where your time is free. I assure you from a business context, it is not. So, there's always that question of what you can do to make things easier for people and do more of the heavy lifting.Chris: Yeah, and to your rather cheeky point that there's 17 ways to run a container on AWS, it is answering that question, right? Like those 17 ways, like, how much of this do you want to run yourself, you could run EKS distro on EC2 instances if you want full control over your environment.Corey: And then run IoT Greengrass core on top within that cluster—Chris: Right.Corey: So, I can run my own Lambda function runtime, so I'm not locked in. Also, DynamoDB local so I'm not locked into AWS. At which point I have gone so far around the bend, no one can help me.Chris: Well—Corey: Pro tip, don't do that. Just don't do that.Chris: But to your point, we have all these options for compute, and specifically containers because there's a lot of people that want to granularly say, “This is where my engineering team gets involved. Everything else you handle.” If I want EKS on Spot Instances only, you can do that. If you want EKS to use Carpenter and say only run ARM workloads, you can do that. If you want to say Fargate and not have anything to manage other than the container file, you can do that.It's how much does your team want to manage? That's the customer obsession part of AWS coming through when it comes to containers is because there's so many different ways to run those workloads, but there's so many different ways to make sure that your team is right-sized, based off the services you're using.Corey: I do want to change gears a bit here because you are mostly known for a couple of things: the DevOps'ish newsletter because that is the oldest and longest thing you've been doing the time that I've known you; EKS, obviously. But when prepping for this show, I discovered you are now co-chair of the OpenGitOps project.Chris: Yes.Corey: So, I have heard of GitOps in the context of, “Oh, it's just basically your CI/CD stuff is triggered by Git events and whatnot.” And I'm sitting here going, “Okay, so from where you're sitting, the two best user interfaces in the world that you have discovered are YAML and Git.” And I just have to start with the question, “Who hurt you?”Chris: [laugh]. Yeah, I share your sentiment when it comes to Git. Not so much with YAML, but I think it's because I'm so used to it. Maybe it's Stockholm Syndrome, maybe the whole YAML thing. I don't know.Corey: Well, it's no XML. We'll put it that way.Chris: Thankfully, yes because if it was, I would have way more, like, just template files laying around to build things. But the—Corey: And rage. Don't forget rage.Chris: And rage, yeah. So, GitOps is a little bit more than just Git in IaC—infrastructure as Code. It's more like Justin Garrison, who's also on my team, he calls it infrastructure software because there's four main principles to GitOps, and if you go to opengitops.dev, you can see them. It's version one.So, we put them on the website, right there on the page. You have to have a declared state and that state has to live somewhere. Now, it's called GitOps because Git is probably the most full-featured thing to put your state in, but you could use an S3 bucket and just version it, for example. And make it private so no one else can get to it.Corey: Or you could use local files: copy-of-copy-of-this-thing-restored-parentheses-use-this-one-dot-final-dot-doc-dot-zip. You know, my preferred naming convention.Chris: Ah, yeah. Wow. Okay. [laugh]. Yeah.Corey: Everything I touch is terrifying.Chris: Yes. Geez, I'm sorry. So first, it's declarative. You declare your state. You store it somewhere. It's versioned and immutable, like I said. And then pulled automatically—don't focus so much on pull—but basically, software agents are applying the desired state from source. So, what does that mean? When it's—you know, the fourth principle is implemented, continuously reconciled. That means those software agents that are checking your desired state are actually putting it back into the desired state if it's out of whack, right? So—Corey: You're talking about agents running it persistently on instances, validating—Chris: Yes.Corey: —a checkpoint on a cron. How is this meaningfully different than a Puppet agent running in years past? Having spent I learned to speak publicly by being a traveling trainer for Puppet; same type of model, and in fact, when I was at Pinterest, we wound up having a fair bit—like, that was their entire model, where they would have—the Puppet's code would live in an S3 bucket that was then copied down, I believe, via Git, and then applied to the instance on a schedule. Like, that sounds like this was sort of a early days GitOps.Chris: Yeah, exactly. Right? Like so it's, I like to think of that as a component of GitOps, right? DevOps, when you talk about DevOps in general, there's a lot of stuff out there. There's a lot of things labeled DevOps that maybe are, or maybe aren't sticking to some of those DevOps core things that make you great.Like the stuff that Nicole Forsgren writes about in books, you know? Accelerate is on my desk for a reason because there's things that good, well-managed DevOps practices do. I see GitOps as an actual implementation of DevOps in an open-source manner because all the tooling for GitOps these days is open-source and it all started as open-source. Now, you can get, like, Flux or Argo—Argo, specifically—there's managed services out there for it, you can have Flux and not maintain it, through an add-on, on EKS for example, and it will reconcile that state for you automatically. And the other thing I like to say about GitOps, specifically, is that it moves at the speed of the Kubernetes Audit Log.If you've ever looked at a Kubernetes audit log, you know it's rather noisy with all these groups and versions and kinds getting thrown out there. So, GitOps will say, “Oh, there's an event for said thing that I'm supposed to be watching. Do I need to change anything? Yes or no? Yes? Okay, go.”And the change gets applied, or, “Hey, there's a new Git thing. Pull it in. A change has happened inGit I need to update it.” You can set it to reconcile on events on time. It's like a cron or it's like an event-driven architecture, but it's combined.Corey: How does it survive the stake through the heart of configuration management? Because before I was doing all this, I wasn't even a T-shaped engineer: you're broad across a bunch of things, but deep in one or two areas, and one of mine was configuration management. I wrote part of SaltStack, once upon a time—Chris: Oh.Corey: —due to a bunch of very strange coincidences all hitting it once, like, I taught people how to use Puppet. But containers ultimately arose and the idea of immutable infrastructure became a thing. And these days when we were doing full-on serverless, well, great, I just wind up deploying a new code bundle to the Lambdas function that I wind up caring about, and that is a immutable version replacement. There is no drift because there is no way to log in and change those things other than through a clear deployment of this as the new version that goes out there. Where does GitOps fit into that imagined pattern?Chris: So, configuration management becomes part of your approval process, right? So, you now are generating an audit log, essentially, of all changes to your system through the approval process that you set up as part of your, how you get things into source and then promote that out to production. That's kind of the beauty of it, right? Like, that's why we suggest using Git because it has functions, like, requests and issues and things like that you can say, “Hey, yes, I approve this,” or, “Hey, no, I don't approve that. We need changes.” So, that's kind of natively happening with Git and, you know, GitLab, GitHub, whatever implementation of Git. There's always, kind of—Corey: Uh, JIF-ub is, I believe, the pronunciation.Chris: JIF-ub? Oh.Corey: Yeah. That's what I'm—Chris: Today, I learned. Okay.Corey: Exactly. And that's one of the things that I do for my lasttweetinaws.com Twitter client that I build—because I needed it, and if other people want to use it, that's great—that is now deployed to 20 different AWS commercial regions, simultaneously. And that is done via—because it turns out that that's a very long to execute for loop if you start down that path—Chris: Well, yeah.Corey: I wound up building out a GitHub Actions matrix—sorry a JIF-ub—actions matrix job that winds up instantiating 20 parallel builds of the CDK deploy that goes out to each region as expected. And because that gets really expensive with native GitHub Actions runners for, like, 36 cents per deploy, and I don't know how to test my own code, so every time I have a typo, that's another quarter in the jar. Cool, but that was annoying for me so I built my own custom runner system that uses Lambda functions as runners running containers pulled from ECR that, oh, it just runs in parallel, less than three minutes. Every time I commit something between I press the push button and it is out and running in the wild across all regions. Which is awesome and also terrifying because, as previously mentioned, I don't know how to test my code.Chris: Yeah. So, you don't know what you're deploying to 20 regions sometime, right?Corey: But it also means I have a pristine, re-composable build environment because I can—Chris: Right.Corey: Just automatically have that go out and the fact that I am making a—either merging a pull request or doing a direct push because I consider main to be my feature branch as whenever something hits that, all the automation kicks off. That was something that I found to be transformative as far as a way of thinking about this because I was very tired of having to tweak my local laptop environment to, “Oh, you didn't assume the proper role and everything failed again and you broke it. Good job.” It wound up being something where I could start developing on more and more disparate platforms. And it finally is what got me away from my old development model of everything I build is on an EC2 instance, and that means that my editor of choice was Vim. I use the VS Code now for these things, and I'm pretty happy with it.Chris: Yeah. So, you know, I'm glad you brought up CDK. CDK gives you a lot of the capabilities to implement GitOps in a way that you could say, like, “Hey, use CDK to declare I need four Amazon EKS clusters with this size, shape, and configuration. Go.” Or even further, connect to these EKS clusters to RDS instances and load balancers and everything else.But you put that state into Git and then you have something that deploys that automatically upon changes. That is infrastructure as code. Now, when you say, “Okay, main is your feature branch,” you know, things happen on main, if this were running in Kubernetes across a fleet of clusters or the globe-wide in 20 regions, something like Flux or Argo would kick in and say, “There's been a change to source, main, and we need to roll this out.” And it'll start applying those changes. Now, what do you get with GitOps that you don't get with your configuration?I mean, can you rollback if you ever have, like, a bad commit that's just awful? I mean, that's really part of the process with GitOps is to make sure that you can, A, roll back to the previous good state, B, roll forward to a known good state, or C, promote that state up through various environments. And then having that all done declaratively, automatically, and immutably, and versioned with an audit log, that I think is the real power of GitOps in the sense that, like, oh, so-and-so approve this change to security policy XYZ on this date at this time. And that to an auditor, you just hand them a log file on, like, “Here's everything we've ever done to our system. Done.” Right?Like, you could get to that state, if you want to, which I think is kind of the idea of DevOps, which says, “Take all these disparate tools and processes and procedures and culture changes”—culture being the hardest part to adopt in DevOps; GitOps kind of forces a culture change where, like, you can't do a CAB with GitOps. Like, those two things don't fly. You don't have a configuration management database unless you absolutely—Corey: Oh, you CAB now but they're all the comments of the pull request.Chris: Right. Exactly. Like, don't push this change out until Thursday after this other thing has happened, kind of thing. Yeah, like, that all happens in GitHub. But it's very democratizing in the sense that people don't have to waste time in an hour-long meeting to get their five minutes in, right?Corey: DoorDash had a problem. As their cloud-native environment scaled and developers delivered new features, their monitoring system kept breaking down. In an organization where data is used to make better decisions about technology and about the business, losing observability means the entire company loses their competitive edge. With Chronosphere, DoorDash is no longer losing visibility into their applications suite. The key? Chronosphere is an open-source compatible, scalable, and reliable observability solution that gives the observability lead at DoorDash business, confidence, and peace of mind. Read the full success story at snark.cloud/chronosphere. That's snark.cloud slash C-H-R-O-N-O-S-P-H-E-R-E.Corey: So, would it be overwhelmingly cynical to suggest that GitOps is the means to implement what we've all been pretending to have implemented for the last decade when giving talks at conferences?Chris: Ehh, I wouldn't go that far. I would say that GitOps is an excellent way to implement the things you've been talking about at all these conferences for all these years. But keep in mind, the technology has changed a lot in the, what 11, 12 years of the existence of DevOps, now. I mean, we've gone from, let's try to manage whole servers immutably to, “Oh, now we just need to maintain an orchestration platform and run containers.” That whole compute interface, you go from SSH to a Docker file, that's a big leap, right?Like, you don't have bespoke sysadmins; you have, like, a platform team. You don't have DevOps engineers; they're part of that platform team, or DevOps teams, right? Like, which was kind of antithetical to the whole idea of DevOps to have a DevOps team. You know, everybody's kind of in the same boat now, where we see skill sets kind of changing. And GitOps and Kubernetes-land is, like, a platform team that manages the cluster, and its state, and health and, you know, production essentially.And then you have your developers deploying what they want to deploy in when whatever namespace they've been given access to and whatever rights they have. So, now you have the potential for one set of people—the platform team—to use one set of GitOps tooling, and your applications teams might not like that, and that's fine. They can have their own namespaces with their own tooling in it. Like, Argo, for example, is preferred by a lot of developers because it has a nice UI with green and red dots and they can show people and it looks nice, Flux, it's command line based. And there are some projects out there that kind of take the UI of Argo and try to run Flux underneath that, and those are cool kind of projects, I think, in my mind, but in general, right, I think GitOps gives you the choice that we missed somewhat in DevOps implementations of the past because it was, “Oh, we need to go get cloud.” “Well, you can only use this cloud.” “Oh, we need to go get this thing.” “Well, you can only use this thing in-house.”And you know, there's a lot of restrictions sometimes placed on what you can use in your environment. Well, if your environment is Kubernetes, how do you restrict what you can run, right? Like you can't have an easily configured say, no open-source policy if you're running Kubernetes. [laugh] so it becomes, you know—Corey: Well, that doesn't stop some companies from trying.Chris: Yeah, that's true. But the idea of, like, enabling your developers to deploy at will and then promote their changes as they see fit is really the dream of DevOps, right? Like, same with production and platform teams, right? I want to push my changes out to a larger system that is across the globe. How do I do that? How do I manage that? How do I make sure everything's consistent?GitOps gives you those ways, with Kubernetes native things like customizations, to make consistent environments that are robust and actually going to be reconciled automatically if someone breaks the glass and says, “Oh, I need to run this container immediately.” Well, that's going to create problems because it's deviated from state and it's just that one region, so we'll put it back into state.Corey: It'll be dueling banjos, at some point. You'll try and doing something manually, it gets reverted automatically. I love that pattern. You'll get bored before the computer does, always.Chris: Yeah. And GitOps is very new, right? When you think about the lifetime of GitOps, I think it was coined in, like, 2018. So, it's only four years old, right? When—Corey: I prefer it to ChatOps, at least, as far as—Chris: Well, I mean—Corey: —implementation and expression of the thing.Chris: —ChatOps was a way to do DevOps. I think GitOps—Corey: Well, ChatOps is also a way to wind up giving whoever gets access to your Slack workspace root in production.Chris: Mmm.Corey: But that's neither here nor there.Chris: Mm-hm.Corey: It's yeah, we all like to pretend that's not a giant security issue in our industry, but that's a topic for another time.Chris: Yeah. And that's why, like, GitOps also depends upon you having good security, you know, and good authorization and approval processes. It enforces that upon—Corey: Yeah, who doesn't have one of those?Chris: Yeah. If it's a sole operation kind of deal, like in your setup, your case, I think you kind of got it doing right, right? Like, as far as GitOps goes—Corey: Oh, to be clear, we are 11 people and we do have dueling pull requests and all the rest.Chris: Right, right, right.Corey: But most of the stuff I talk about publicly is not our production stuff, so it really is just me. Just as a point of clarity there. I've n—the 11 people here do not all—the rest of you don't just sit there and clap as I do all the work.Chris: Right.Corey: Most days.Chris: No, I'm sure they don't. I'm almost certain they don't clap… for you. I mean, they would—Corey: No. No, they try and talk me out of it in almost every case.Chris: Yeah, exactly. So, the setup that you, Corey Quinn, have implemented to deploy these 20 regions is kind of very GitOps-y, in the sense that when main changes, it gets updated. Where it's not GitOps-y is what if the endpoint changes? Does it get reconciled? That's the piece you're probably missing is that continuous reconciliation component, where it's constantly checking and saying, “This thing out there is deployed in the way I want it. You know, the way I declared it to be in my source of truth.”Corey: Yeah, when you start having other people getting involved, there can—yeah, that's where regressions enter. And it's like, “Well, I know where things are so why would I change the endpoint?” Yeah, it turns out, not everyone has the state of the entire application in their head. Ideally it should live in—Chris: Yeah. Right. And, you know—Corey: —you know, Git or S3.Chris: —when I—yeah, exactly. When I think about interactions of the past coming out as a new DevOps engineer to work with developers, it's always been, will developers have access to prod or they don't? And if you're in that environment with—you're trying to run a multi-billion dollar operation, and your devs have direct—or one Dev has direct access to prod because prod is in his brain, that's where it's like, well, now wait a minute. Prod doesn't have to be only in your brain. You can put that in the codebase and now we know what is in your brain, right?Like, you can almost do—if you document your code, well, you can have your full lifecycle right there in one place, including documentation, which I think is the best part, too. So, you know, it encourages approval processes and automation over this one person has an entire state of the system in their head; they have to go in and fix it. And what if they're not on call, or in Jamaica, or on a cruise ship somewhere kind of thing? Things get difficult. Like, for example, I just got back from vacation. We were so far off the grid, we had satellite internet. And let me tell you, it was hard to write an email newsletter where I usually open 50 to 100 tabs.Corey: There's a little bit of internet out Californ-ie way.Chris: [laugh].Corey: Yeah it's… it's always weird going from, like, especially after pandemic; I have gigabit symmetric here and going even to re:Invent where I'm trying to upload a bunch of video and whatnot.Chris: Yeah. Oh wow.Corey: And the conference WiFi was doing its thing, and well, Verizon 5G was there but spotty. And well, yeah. Usual stuff.Chris: Yeah. It's amazing to me how connectivity has become so ubiquitous.Corey: To the point where when it's not there anymore, it's what do I do with myself? Same story about people pushing back against remote development of, “Oh, I'm just going to do it all on my laptop because what happens if I'm on a plane?” It's, yeah, the year before the pandemic, I flew 140,000 miles domestically and I was almost never hamstrung by my ability to do work. And my only local computer is an iPad for those things. So, it turns out that is less of a real world concern for most folks.Chris: Yeah I actually ordered the components to upgrade an old Nook that I have here and turn it into my, like, this is my remote code server, that's going to be all attached to GitHub and everything else. That's where I want to be: have Tailscale and just VPN into this box.Corey: Tailscale is transformative.Chris: Yes. Tailscale will change your life. That's just my personal opinion.Corey: Yep.Chris: That's not an AWS opinion or anything. But yeah, when you start thinking about your network as it could be anywhere, that's where Tailscale, like, really shines. So—Corey: Tailscale makes the internet work like we all wanted to believe that it worked.Chris: Yeah. And Wireguard is an excellent open-source project. And Tailscale consumes that and puts an amazingly easy-to-use UI, and troubleshooting tools, and routing, and all kinds of forwarding capabilities, and makes it kind of easy, which is really, really, really kind of awesome. And Tailscale and Kubernetes—Corey: Yeah, ‘network' and ‘easy' don't belong in the same sentence, but in this case, they do.Chris: Yeah. And trust me, the Kubernetes story in Tailscale, there is a lot of there. I understand you might want to not open ports in your VPC, maybe, but if you use Tailscale, that node is just another thing on your network. You can connect to that and see what's going on. Your management cluster is just another thing on the network where you can watch the state.But it's all—you're connected to it continuously through Tailscale. Or, you know, it's a much lighter weight, kind of meshy VPN, I would say, if I had to sum it up in one sentence. That was not on our agenda to talk about at all. Anyways. [laugh]Corey: No, no. I love how many different topics we talk about on these things. We'll have to have you back soon to talk again. I really want to thank you for being so generous with your time. If people want to learn more about what you're up to and how you view these things, where can they find you?Chris: Go to ChrisShort.net. So, Chris Short—I'm six-four so remember, it's Short—dot net, and you will find all the places that I write, you can go to devopsish.com to subscribe to my newsletter, which goes out every week. This year. Next year, there'll be breaks. And then finally, if you want to follow me on Twitter, Chris Short: at @ChrisShort on Twitter. All one word so you see two s's. Like, it's okay, there's two s's there.Corey: Links to all of that will of course be in the show notes. It's easier for people to do the clicky-clicky thing as a general rule.Chris: Clicky things are easier than the wordy things, yes.Corey: Says the Kubernetes guy.Chris: Yeah. Says the Kubernetes guy. Yeah, you like that, huh? Like I said, Argo gives you a UI. [laugh].Corey: Thank you [laugh] so much for your time. I really do appreciate it.Chris: Thank you. This has been fun. If folks have questions, feel free to reach out. Like, I am not one of those people that hides behind a screen all day and doesn't respond. I will respond to you eventually.Corey: I'm right here, Chris. Come on, come on. You're calling me out in front of myself. My God.Chris: Egh. It might take a day or two, but I will respond. I promise.Corey: Thanks again for your time. This has been Chris Short, senior developer advocate 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 and if it's YouTube, click the thumbs-up button. Whereas if you've hated this podcast, same thing, smash the buttons five-star review and leave an insulting comment that is written in syntactically correct YAML because it's just so easy to do.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.

About ChrisChris is the Co-founder and Chief Product Officer at incident.io, where they're building incident management products that people actually want to use. A software engineer by trade, Chris is no stranger to gnarly incidents, having participated (and caused!) them at everything from early stage startups through to enormous IT organizations.Links Referenced: incident.io: https://incident.io Practical Guide to Incident Management: https://incident.io/guide/ 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: DoorDash had a problem. As their cloud-native environment scaled and developers delivered new features, their monitoring system kept breaking down. In an organization where data is used to make better decisions about technology and about the business, losing observability means the entire company loses their competitive edge. With Chronosphere, DoorDash is no longer losing visibility into their applications suite. The key? Chronosphere is an open-source compatible, scalable, and reliable observability solution that gives the observability lead at DoorDash business, confidence, and peace of mind. Read the full success story at snark.cloud/chronosphere. That's snark.cloud slash C-H-R-O-N-O-S-P-H-E-R-E.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. Today's promoted guest is Chris Evans, who's the CPO and co-founder of incident.io. Chris, first, thank you very much for joining me. And I'm going to start with an easy question—well, easy question, hard answer, I think—what is an incident.io exactly?Chris: Incident.io is a software platform that helps entire organizations to respond to recover from and learn from incidents.Corey: When you say incident, that means an awful lot of things. And depending on where you are in the ecosystem in the world, that means different things to different people. For example, oh, incident. Like, “Are you talking about the noodle incident because we had an agreement that we would never speak about that thing again,” style, versus folks who are steeped in DevOps or SRE culture, which is, of course, a fancy way to say those who are sad all the time, usually about computers. What is an incident in the context of what you folks do?Chris: That, I think, is the killer question. I think if you look at organizations in the past, I think incidents were those things that happened once a quarter, maybe once a year, and they were the thing that brought the entirety of your site down because your big central database that was in a data center sort of disappeared. The way that modern companies run means that the definition has to be very, very different. So, most places now rely on distributed systems and there is no, sort of, binary sense of up or down these days. And essentially, in the general case, like, most companies are continually in a sort of state of things being broken all of the time.And so, for us, when we look at what an incident is, it is essentially anything that takes you away from your planned work with a sense of urgency. And that's the sort of the pithy definition that we use there. Generally, that can mean anything—it means different things to different folks, and, like, when we talk to folks, we encourage them to think carefully about what that threshold is, but generally, for us at incident.io, that means basically a single error that is worthwhile investigating that you would stop doing your backlog work for is an incident. And also an entire app being down, that is an incident.So, there's quite a wide range there. But essentially, by sort of having more incidents and lowering that threshold, you suddenly have a heap of benefits, which I can go very deep into and talk for hours about.Corey: It's a deceptively complex question. When I talk to folks about backups, one of the biggest problems in the world of backup and building a DR plan, it's not building the DR plan—though that's no picnic either—it's okay. In the time of cloud, all your planning figures out, okay. Suddenly the site is down, how do we fix it? There are different levels of down and that means different things to different people where, especially the way we build apps today, it's not is the service or site up or down, but with distributed systems, it's how down is it?And oh, we're seeing elevated error rates in us-tire-fire-1 region of AWS. At what point do we begin executing on our disaster plan? Because the worst answer, in some respects is, every time you think you see a problem, you start failing over to other regions and other providers and the rest, and three minutes in, you've irrevocably made the cutover and it's going to take 15 minutes to come back up. And oh, yeah, then your primary site comes back up because whoever unplugged something, plugged it back in and now you've made the wrong choice. Figuring out all the things around the incident, it's not what it once was.When you were running your own blog on a single web server and it's broken, it's pretty easy to say, “Is it up or is it down?” As you scale out, it seems like that gets more and more diffuse. But it feels to me that it's also less of a question of how the technology has scaled, but also how the culture and the people have scaled. When you're the only engineer somewhere, you pretty much have no choice but to have the entire state of your stack shoved into your head. When that becomes 15 or 20 different teams of people, in some cases, it feels like it's almost less than a technology problem than it is a problem of how you communicate and how you get people involved. And the issues in front of the people who are empowered and insightful in a certain area that needs fixing.Chris: A hundred percent. This is, like, a really, really key point, which is that organizations themselves are very complex. And so, you've got this combination of systems getting more and more complicated, more and more sort of things going wrong and perpetually breaking but you've got very, very complicated information structures and communication throughout the whole organization to keep things up and running. The very best orgs are the ones where they can engage the entire, sort of, every corner of the organization when things do go wrong. And lived and breathed this firsthand when various different previous companies, but most recently at Monzo—which is a bank here in the UK—when an incident happened there, like, one of our two physical data center locations went down, the bank wasn't offline. Everything was resilient to that, but that required an immediate response.And that meant that engineers were deployed to go and fix things. But it also meant the customer support folks might be required to get involved because we might be slightly slower processing payments. And it means that risk and compliance folks might need to get involved because they need to be reporting things to regulators. And the list goes on. There's, like, this need for a bunch of different people who almost certainly have never worked together or rarely worked together to come together, land in this sort of like empty space of this incident room or virtual incident room, and figure out how they're going to coordinate their response and get things back on track in the sort of most streamlined way and as quick as possible.Corey: Yeah, when your bank is suddenly offline, that seems like a really inopportune time to be introduced to the database team. It's, “Oh, we have one of those. Wonderful. I feel like you folks are going to come in handy later today.” You want to have those pathways of communication open well in advance of these issues.Chris: A hundred percent. And I think the thing that makes incidents unique is that fact. And I think the solution to that is this sort of consistent, level playing field that you can put everybody on. So, if everybody understands that the way that incidents are dealt with is consistent, we declare it like this, and under these conditions, these things happen. And, you know, if I flag this kind of level of impact, we have to pull in someone else to come and help make a decision.At the core of it, there's this weird kind of duality to incidents where they are both kind of semi-formulaic and that you can basically encode a lot of the processes that happen, but equally, they are incredibly chaotic and require a lot of human impact to be resilient and figure these things out because stuff that you have never seen happen before is happening and failing in ways that you never predicted. And so, this is where incident.io plays into this is that we try to take the first half of that off of your hands, which is, we will help you run your process so that all of the brain capacity you have, it goes on to the bit that humans are uniquely placed to be able to do, which is responding to these very, very chaotic, sort of, surprise events that have happened.Corey: I feel as well—because I played around in this space a bit before I used to run ops teams—and, more or less I really should have had a t-shirt then that said, “I am the root cause,” because yeah, I basically did a lot of self-inflicted outages in various environments because it turns out, I'm not always the best with computers. Imagine that. There are a number of different companies that play in the space that look at some part of the incident lifecycle. And from the outside, first, they all look alike because it's, “Oh, so you're incident.io. I assume you're PagerDuty. You're the thing that calls me at two in the morning to make sure I wake up.”Conversely, for folks who haven't worked deeply in that space, as well, of setting things on fire, what you do sounds like it's highly susceptible to the Hacker News problem. Where, “Wait, so what you do is effectively just getting people to coordinate and talk during an incident? Well, that doesn't sound hard. I could do that in a weekend.” And no, no, you can't.If this were easy, you would not have been in business as long as you have, have the team the size that you do, the customers that you do. But it's one of those things that until you've been in a very specific set of a problem, it doesn't sound like it's a real problem that needs solving.Chris: Yeah, I think that's true. And I think that the Hacker News point is a particularly pertinent one and that someone else, sort of, in an adjacent area launched on Hacker News recently, and the amount of feedback they got around, you know, “You're a Slack bot. How is this a company?” Was kind of staggering. And I think generally where that comes from is—well, first of all that bias that engineers have, which is just everything you look at as an engineer is like, “Yeah, I can build that in a weekend.” I think there's often infinite complexity under the hood that just gets kind of brushed over. But yeah, I think at the core of it, you probably could build a Slack bot in a weekend that creates a channel for you in Slack and allows you to post somewhere that some—Corey: Oh, good. More channels in Slack. Just when everyone wants.Chris: Well, there you go. I mean, that's a particular pertinent one because, like, our tool does do that. And one of the things—so I built at Monzo, a version of incident.io that we used at the company there, and that was something that I built evenings and weekends. And among the many, many things I never got around to building, archiving and cleaning up channels was one of the ones that was always on that list.And so, Monzo did have this problem of littered channels everywhere, I think that sort of like, part of the problem here is, like, it is easy to look at a product like ours and sort of assume it is this sort of friendly Slack bot that helps you orchestrate some very basic commands. And I think when you actually dig into the problems that organizations above a certain size have, they're not solved by Slack bots. They're solved by platforms that help you to encode your processes that otherwise have to live on a Google Doc somewhere which is five pages long and when it's 2 a.m. and everything's on fire, I guarantee you not a single person reads that Google Doc, so your process is as good as not in place at all. That's the beauty of a tool like ours. We have a powerful engine that helps you basically to encode that and take some load off of you.Corey: To be clear, I'm also not coming at this from a position of judging other people. I just look right now at the Slack workspace that we have The Duckbill Group, and we have something like a ten-to-one channel-to-human ratio. And the proliferation of channels is a very real thing. And the problem that I've seen across the board with other things that try to address incident management has always been fanciful at best about what really happens when something breaks. Like, you talk about, oh, here's what happens. Step one: you will pull up the Google Doc, or you will pull up the wiki or the rest, or in some aspirational places, ah, something seems weird, I will go open a ticket in Jira.Meanwhile, here in reality, anyone who's ever worked in these environments knows that step one, “Oh shit, oh shit, oh shit, oh shit, oh shit. What are we going to do?” And all the practices and procedures that often exist, especially in orgs that aren't very practiced at these sorts of things, tend to fly out the window and people are going to do what they're going to do. So, any tool or any platform that winds up addressing that has to accept the reality of meeting people where they are not trying to educate people into different patterns of behavior as such. One of the things I like about your approach is, yeah, it's going to be a lot of conversation in Slack that is a given we can pretend otherwise, but here in reality, that is how work gets communicated, particularly in extremis. And I really appreciate the fact that you are not trying to, like, fight what feels almost like a law of nature at this point.Chris: Yeah, I think there's a few things in that. The first point around the document approach or the clearly defined steps of how an incident works. In my experience, those things have always gone wrong because—Corey: The data center is down, so we're going to the wiki to follow our incident management procedure, which is in the data center just lost power.Chris: Yeah.Corey: There's a dependency problem there, too. [laugh].Chris: Yeah, a hundred percent. [laugh]. A hundred percent. And I think part of the problem that I see there is that very, very often, you've got this situation where the people designing the process are not the people following the process. And so, there's this classic, I've heard it through John Allspaw, but it's a bunch of other folks who talk about the difference between people, you know, at the sharp end or the blunt end of the work.And I think the problem that people are facing the past is you have these people who sit in the, sort of, metaphorical upstairs of the office and think that they make a company safe by defining a process on paper. And they ship the piece of paper and go, “That is a good job for me done. I'm going to leave and know that I've made the bank—the other whatever your organization does—much, much safer.” And I think this is where things fall down because—Corey: I want to ambush some of those people in their performance reviews with, “Cool. Just for fun, all the documentation here, we're going to pull up the analytics to see how often that stuff gets viewed. Oh, nobody ever sees it. Hmm.”Chris: It's frustrating. It's frustrating because that never ever happens, clearly. But the point you made around, like, meeting people where you are, I think that is a huge one, which is incidents are founded on great communication. Like, as I said earlier, this is, like, a form of team with someone you've never ever worked with before and the last thing you want to do is be, like, “Hey, Corey, I've never met you before, but let's jump out onto this other platform somewhere that I've never been or haven't been for weeks and we'll try and figure stuff out over there.” It's like, no, you're going to be communicating—Corey: We use Slack internally, but we have a WhatsApp chat that we wind up using for incident stuff, so go ahead and log into WhatsApp, which you haven't done in 18 months, and join the chat. Yeah, in the dawn of time, in the mists of antiquity, you vaguely remember hearing something about that your first week and then never again. This stuff has to be practiced and it's important to get it right. How do you approach the inherent and often unfortunate reality that incident response and management inherently becomes very different depending upon the specifics of your company or your culture or something like that? In other words, how cookie-cutter is what you have built versus adaptable to different environments it finds itself operating in?Chris: Man, the amount of time we spent as a founding team in the early days deliberating over how opinionated we should be versus how flexible we should be was staggering. The way we like to describe it as we are quite opinionated about how we think incidents should be run, however we let you imprint your own process into that, so putting some color onto that. We expect incidents to have a lead. That is something you cannot get away from. However, you can call the lead whatever makes sense for you at your organization. So, some folks call them an incident commander or a manager or whatever else.Corey: There's overwhelming militarization of these things. Like, oh, yes, we're going to wind up taking a bunch of terms from the military here. It's like, you realize that your entire giant screaming fire is that the lights on the screen are in the wrong pattern. You're trying to make them in the right pattern. No one dies here in most cases, so it feels a little grandiose for some of those terms being tossed around in some cases, but I get it. You've got to make something that is unpleasant and tedious in many respects, a little bit more gripping. I don't envy people. Messaging is hard.Chris: Yeah, it is. And I think if you're overly virtuoustic and inflexible, you're sort of fighting an uphill battle here, right? So, folks are going to want to call things what they want to call things. And you've got people who want to import [ITIL 00:15:04] definitions for severity ease into the platform because that's what they're familiar with. That's fine.What we are opinionated about is that you have some severity levels because absent academic criticism of severity levels, they are a useful mechanism to very coarsely and very quickly assess how bad something is and to take some actions off of it. So yeah, we basically have various points in the product where you can customize and put your own sort of flavor on it, but generally, we have a relatively opinionated end-to-end expectation of how you will run that process.Corey: The thing that I find that annoys me—in some cases—the most is how heavyweight the process is, and it's clearly built by people in an ivory tower somewhere where there's effectively a two-day long postmortem analysis of the incident, and so on and so forth. And okay, great. Your entire site has been blown off the internet, yeah, that probably makes sense. But as soon as you start broadening that to things like okay, an increase in 500 errors on this service for 30 minutes, “Great. Well, we're going to have a two-day postmortem on that.” It's, “Yeah, sure would be nice if we could go two full days without having another incident of that caliber.” So, in other words, whose foot—are we going to hire a new team whose full-time job it is, is to just go ahead and triage and learn from all these incidents? Seems to me like that's sort of throwing wood behind the wrong arrows.Chris: Yeah, I think it's very reductive to suggest that learning only happens in a postmortem process. So, I wrote a blog, actually, not so long ago that is about running postmortems and when it makes sense to do it. And as part of that, I had a sort of a statement that was [laugh] that we haven't run a single postmortem when I wrote this blog at incident.io. Which is probably shocking to many people because we're an incident company, and we talk about this stuff, but we were also a company of five people and when something went wrong, the learning was happening and these things were sort of—we were carving out the time, whether it was called a postmortem, or not to learn and figure out these things. Extrapolating that to bigger companies, there is little value in following processes for the sake of following processes. And so, you could have—Corey: Someone in compliance just wound up spitting their coffee over their desktop as soon as you said that. But I hear you.Chris: Yeah. And it's those same folks who are the ones who care about the document being written, not the process and the learning happening. And I think that's deeply frustrating to me as—Corey: All the plans, of course, assume that people will prioritize the company over their own family for certain kinds of disasters. I love that, too. It's divorced from reality; that's ridiculous, on some level. Speaking of ridiculous things, as you continue to grow and scale, I imagine you integrate with things beyond just Slack. You grab other data sources and over in the fullness of time.For example, I imagine one of your most popular requests from some of your larger customers is to integrate with their HR system in order to figure out who's the last engineer who left, therefore everything immediately their fault because lord knows the best practice is to pillory whoever was the last left because then they're not there to defend themselves anymore and no one's going to get dinged for that irresponsible jackass's decisions, even if they never touched the system at all. I'm being slightly hyperbolic, but only slightly.Chris: Yeah. I think [laugh] that's an interesting point. I am definitely going to raise that feature request for a prefilled root cause category, which is, you know, the value is just that last person who left the organization. That it's a wonderful scapegoat situation there. I like it.To the point around what we do integrate with, I think the thing is actually with incidents that's quite interesting is there is a lot of tooling that exists in this space that does little pockets of useful, valuable things in the shape of incidents. So, you have PagerDuty is this system that does a great job of making people's phone making noise, but that happens, and then you're dropped into this sort of empty void of nothingness and you've got to go and figure out what to do. And then you've got things like Jira where clearly you want to be able to track actions that are coming out of things going wrong in some cases, and that's a great tool for that. And various other things in the middle there. And yeah, our value proposition, if you want to call it that, is to bring those things together in a way that is massively ergonomic during an incident.So, when you're in the middle of an incident, it is really handy to be able to go, “Oh, I have shipped this horrible fix to this thing. It works, but I must remember to undo that.” And we put that at your fingertips in an incident channel from Slack, that you can just log that action, lose that cognitive load that would otherwise be there, move on with fixing the thing. And you have this sort of—I think it's, like, that multiplied by 1000 in incidents that is just what makes it feel delightful. And I cringe a little bit saying that because it's an incident at the end of the day, but genuinely, it feels magical when some things happen that are just like, “Oh, my gosh, you've automatically hooked into my GitHub thing and someone else merged that PR and you've posted that back into the channel for me so I know that that happens. That would otherwise have been a thing where I jump out of the incident to go and figure out what was happening.”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: The problem with the cloud, too, is the first thing that, when there starts to be an incident happening is the number one decision—almost the number one decision point is this my shitty code, something we have just pushed in our stuff, or is it the underlying provider itself? Which is why the AWS status page being slow to update is so maddening. Because those are two completely different paths to go down and you are having to pursue both of them equally at the same time until one can be ruled out. And that is why time to identify at least what side of the universe it's on is so important. That has always been a bit of a tricky challenge.I want to talk a bit about circular dependencies. You target a certain persona of customer, but I'm going to go out on a limb and assume that one explicit company that you are not going to want to do business with in your current iteration is Slack itself because a tool to manage—okay, so our service is down, so we're going to go to Slack to fix it doesn't work when the service is Slack itself. So, that becomes a significant challenge. As you look at this across the board, are you seeing customers having problems where you have circular dependency issues with this? Easy example: Slack is built on top of AWS.When there's an underlying degradation of, huh, suddenly us-east-1 is not doing what it's supposed to be doing, now, Slack is degraded as well, as well as the customer site, it seems like at that point, you're sort of in a bit of tricky positioning as a customer. Counterpoint, when neither Slack nor your site are working, figuring out what caused that issue doesn't seem like it's the biggest stretch of the imagination at that point.Chris: I've spent a lot of my career working in infrastructure, platform-type teams, and I think you can end up tying yourself in knots if you try and over-optimize for, like, avoiding these dependencies. I think it's one of those, sort of, turtles all the way down situations. So yes, Slack are unlikely to become a customer because they are clearly going to want to use our product when they are down.Corey: They reach out, “We'd like to be your customer.” Your response is, “Please don't be.” None of us are going to be happy with this outcome.Chris: Yeah, I mean, the interesting thing that is that we're friends with some folks at Slack, and they believe it or not, they do use Slack to navigate their incidents. They have an internal tool that they have written. And I think this sort of speaks to the point we made earlier, which is that incidents and things failing or not these sort of big binary events. And so—Corey: All of Slack is down is not the only kind of incident that a company like Slack can experience.Chris: I'd go as far as that it's most commonly not that. It's most commonly that you're navigating incidents where it is a degradation, or some edge case, or something else that's happened. And so, like, the pragmatic solution here is not to avoid the circular dependencies, in my view; it's to accept that they exist and make sure you have sensible escape hatches so that when something does go wrong—so a good example, we use incident.io at incident.io to manage incidents that we're having with incident.io. And 99% of the time, that is absolutely fine because we are having some error in some corner of the product or a particular customer is doing something that is a bit curious.And I could count literally on one hand the number of times that we have not been able to use our products to fix our product. And in those cases, we have a fallback which is jump into—Corey: I assume you put a little thought into what happened. “Well, what if our product is down?” “Oh well, I guess we'll never be able to fix it or communicate about it.” It seems like that's the sort of thing that, given what you do, you might have put more than ten seconds of thought into.Chris: We've put a fair amount of thought into it. But at the end of the day, [laugh] it's like if stuff is down, like, what do you need to do? You need to communicate with people. So, jump on a Google Chat, jump on a Slack huddle, whatever else it is we have various different, like, fallbacks in different order. And at the core of it, I think this is the thing is, like, you cannot be prepared for every single thing going wrong, and so what you can be prepared for is to be unprepared and just accept that humans are incredibly good at being resilient, and therefore, all manner of things are going to happen that you've never seen before and I guarantee you will figure them out and fix them, basically.But yeah, I say this; if my SOC 2 auditor is listening, we also do have a very well-defined, like, backup plan in our SOC 2 [laugh] in our policies and processes that is the thing that we will follow that. But yeah.Corey: The fact that you're saying the magic words of SOC 2, yes, exactly. Being in a responsible adult and living up to some baseline compliance obligations is really the sign of a company that's put a little thought into these things. So, as I pull up incident.io—the website, not the company to be clear—and look through what you've written and how you talk about what you're doing, you've avoided what I would almost certainly have not because your tagline front and center on your landing page is, “Manage incidents at scale without leaving Slack.” If someone were to reach out and say, well, we're down all the time, but we're using Microsoft Teams, so I don't know that we can use you, like, the immediate instinctive response that I would have for that to the point where I would put it in the copy is, “Okay, this piece of advice is free. I would posit that you're down all the time because you're the kind of company to use Microsoft Teams.” But that doesn't tend to win a whole lot of friends in various places. In a slightly less sarcastic bent, do you see people reaching out with, “Well, we want to use you because we love what you're doing, but we don't use Slack.”Chris: Yeah. We do. A lot of folks actually. And we will support Teams one day, I think. There is nothing especially unique about the product that means that we are tied to Slack.It is a great way to distribute our product and it sort of aligns with the companies that think in the way that we do in the general case but, like, at the core of what we're building, it's a platform that augments a communication platform to make it much easier to deal with a high-stress, high-pressure situation. And so, in the future, we will support ways for you to connect Microsoft Teams or if Zoom sought out getting rich app experiences, talk on a Zoom and be able to do various things like logging actions and communicating with other systems and things like that. But yeah, for the time being very, very deliberate focus mechanism for us. We're a small company with, like, 30 people now, and so yeah, focusing on that sort of very slim vertical is working well for us.Corey: And it certainly seems to be working to your benefit. Every person I've talked to who is encountered you folks has nothing but good things to say. We have a bunch of folks in common listed on the wall of logos, the social proof eye chart thing of here's people who are using us. And these are serious companies. I mean, your last job before starting incident.io was at Monzo, as you mentioned.You know what you're doing in a regulated, serious sense. I would be, quite honestly, extraordinarily skeptical if your background were significantly different from this because, “Well, yeah, we worked at Twitter for Pets in our three-person SRE team, we can tell you exactly how to go ahead and handle your incidents.” Yeah, there's a certain level of operational maturity that I kind of just based upon the name of the company there; don't think that Twitter for Pets is going to nail. Monzo is a bank. Guess you know what you're talking about, given that you have not, basically, been shut down by an army of regulators. It really does breed an awful lot of confidence.But what's interesting to me is the number of people that we talk to in common are not themselves banks. Some are and they do very serious things, but others are not these highly regulated, command-and-control, top-down companies. You are nimble enough that you can get embedded at those startup-y of startup companies once they hit a certain point of scale and wind up helping them arrive at a better outcome. It's interesting in that you don't normally see a whole lot of tools that wind up being able to speak to both sides of that very broad spectrum—and most things in between—very effectively. But you've somehow managed to thread that needle. Good work.Chris: Thank you. Yeah. What else can I say other than thank you? I think, like, it's a deliberate product positioning that we've gone down to try and be able to support those different use cases. So, I think, at the core of it, we have always tried to maintain the incident.io should be installable and usable in your very first incident without you having to have a very steep learning curve, but there is depth behind it that allows you to support a much more sophisticated incident setup.So, like, I mean, you mentioned Monzo. Like, I just feel incredibly fortunate to have worked at that company. I joined back in 2017 when they were, I don't know, like, 150,000 customers and it was just getting its banking license. And I was there for four years and was able to then see it scale up to 6 million customers and all of the challenges and pain that goes along with that both from building infrastructure on the technical side of things, but from an organizational side of things. And was, like, front-row seat to being able to work with some incredibly smart people and sort of see all these various different pain points.And honestly, it feels a little bit like being in sort of a cheat mode where we get to this import a lot of that knowledge and pain that we felt at Monzo into the product. And that happens to resonate with a bunch of folks. So yeah, I feel like things are sort of coming out quite well at the moment for folks.Corey: The one thing I will say before we wind up calling this an episode is just how grateful I am that I don't have to think about things like this anymore. There's a reason that the problem that I chose to work on of expensive AWS bills being very much a business-hours only style of problem. We're a services company. We don't have production infrastructure that is externally facing. “Oh, no, one of our data analysis tools isn't working internally.”That's an interesting curiosity, but it's not an emergency in the same way that, “Oh, we're an ad network and people are looking at ads right now because we're broken,” is. So, I am grateful that I don't have to think about these things anymore. And also a little wistful because there's so much that you do it would have made dealing with expensive and dangerous outages back in my production years a lot nicer.Chris: Yep. I think that's what a lot of folks are telling us essentially. There's this curious thing with, like, this product didn't exist however many years ago and I think it's sort of been quite emergent in a lot of companies that, you know, as sort of things have moved on, that something needs to exist in this little pocket of space, dealing with incidents in modern companies. So, I'm very pleased that what we're able to build here is sort of working and filling that for folks.Corey: Yeah. I really want to thank you for taking so much time to go through the ethos of what you do, why you do it, and how you do it. If people want to learn more, where's the best place for them to go? Ideally, not during an incident.Chris: Not during an incident, obviously. Handily, the website is the company name. So, incident.io is a great place to go and find out more. We've literally—literally just today, actually—launched our Practical Guide to Incident Management, which is, like, a really full piece of content which, hopefully, will be useful to a bunch of different folks.Corey: Excellent. We will, of course, put a link to that in the [show notes 00:29:52]. I really want to thank you for being so generous with your time. Really appreciate it.Chris: Thanks so much. It's been an absolute pleasure.Corey: Chris Evans, Chief Product Officer and co-founder of incident.io. 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 episode, please leave a five-star review on your podcast platform of choice along with an angry comment telling me why your latest incident is all the intern's fault.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.

Want to give your ears a break and read this as an article? You're looking for this link:https://www.lastweekinaws.com/blog/the-chatops-issue-no-ones-chatting-aboutWant to watch the full dramatic reenactment of this podcast? Watch the YouTube Video here: https://youtu.be/eBKZ71OLjG8Never miss an episode Join the Last Week in AWS newsletter Subscribe wherever you get your podcasts Help the show Leave a review Share your feedback Subscribe wherever you get your podcasts What's Corey up to? Follow Corey on Twitter (@quinnypig) See our recent work at the Duckbill Group Apply to work with Corey and the Duckbill Group to help lower your AWS bill

When should you pivot your startup? Carl and Richard talk to Phil Haack about his experiences with Abbot - the chatbot designed to work within Slack. Phil talks about starting with Abbot focused on ChatOps, where Abbot would help with automation around the deployment of applications. And while there were some customers, it wasn't enough. The pivot was to customer support that also depends on tools like Slack. The conversation digs into focusing on understanding where customers have challenges and learning to solve them, rather than trying to offer a platform for everything!

When should you pivot your startup? Carl and Richard talk to Phil Haack about his experiences with Abbot - the chatbot designed to work within Slack. Phil talks about starting with Abbot focused on ChatOps, where Abbot would help with automation around the deployment of applications. And while there were some customers, it wasn't enough. The pivot was to customer support that also depends on tools like Slack. The conversation digs into focusing on understanding where customers have challenges and learning to solve them, rather than trying to offer a platform for everything!

When should you pivot your startup? Carl and Richard talk to Phil Haack about his experiences with Abbot - the chatbot designed to work within Slack. Phil talks about starting with Abbot focused on ChatOps, where Abbot would help with automation around the deployment of applications. And while there were some customers, it wasn't enough. The pivot was to customer support that also depends on tools like Slack. The conversation digs into focusing on understanding where customers have challenges and learning to solve them, rather than trying to offer a platform for everything!Support this podcast at — https://redcircle.com/net-rocks/donations

When should you pivot your startup? Carl and Richard talk to Phil Haack about his experiences with Abbot - the chatbot designed to work within Slack. Phil talks about starting with Abbot focused on ChatOps, where Abbot would help with automation around the deployment of applications. And while there were some customers, it wasn't enough. The pivot was to customer support that also depends on tools like Slack. The conversation digs into focusing on understanding where customers have challenges and learning to solve them, rather than trying to offer a platform for everything!Support this podcast at — https://redcircle.com/net-rocks/donations

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation.

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation.

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation.

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation. The post Tech Bytes: Bringing ChatOps Into SD-WAN To Simplify Operations (Sponsored) appeared first on Packet Pushers.

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation. The post Tech Bytes: Bringing ChatOps Into SD-WAN To Simplify Operations (Sponsored) appeared first on Packet Pushers.

Today on the Tech Bytes podcast, sponsored by Palo Alto Networks, we discuss a new ChatOps feature in Palo Alto's Prisma SD-WAN. Engineers and administrators can query the SD-WAN controller from a chat app such as Microsoft Teams and get a meaningful response. Sutapa Bansal, Director of Product Management at Palo Alto Networks, joins us to discuss how it works, use cases, and implementation. The post Tech Bytes: Bringing ChatOps Into SD-WAN To Simplify Operations (Sponsored) appeared first on Packet Pushers.

Michael Cucchi  (VP of Product @PagerDuty) talks about the challenges of increased hours, more frequent incident responses and overall tech burnout as a result of the 2020-21 pandemic.SHOW: 551CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:AWS Data Backup for Dummies (Veeam)Choose Your Own Cloud Adventure with Veeam and AWSDatadog Database Monitoring: Modern Monitoring and AnalyticsGet started monitoring performance analytics from any database with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.Spot by NetAppMore Cloud, Less Cost (Spot by NetApp)SHOW NOTES:PagerDuty (homepage)State of Digital Operations report (PagerDuty)Topic 1 - Welcome to the show. Tell us a little bit about your background.Topic 2 - PagerDuty recently published the 2021 State of Digital Operations report. What were some of the high-level takeaways?Topic 3 - Obviously the pandemic has disrupted where people work for the last 18 months. But what are some of the other factors that are causing so much disruption for Operations teams?Topic 4 - We're seeing the number of critical incidents per month increase (average 105/month). Do you think that's more a factor of companies having to change so much so quickly, or technical debts just continue to accumulate and the overall foundation is less stable?Topic 5 - There are tools (ChatOps) that are augmenting how we collaborate, but do you think the lack of face-to-face interactions between teams is causing some of the increased challenges we've seen this past year? Topic 6 - Any tips or tricks that you can give to Operations teams that are trying to manage this increased workload and may be struggling to keep up, or find the right balance between life and work?FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

ChatOps is core to all things we do at Mattermost, but sometimes it can be difficult to discern the meaning or emotion behind the words. To find out more, PJ sat down with Craig Tucker, the founder of V.E.R.N. AI  , a text based artificial intelligence tool that helps to understand the emotions of people communicating online.

Cloud Posse holds public "Office Hours" every Wednesday at 11:30am PST to answer questions on all things related to DevOps, Terraform, Kubernetes, CICD. Basically, it's like an interactive "Lunch & Learn" session where we get together for about an hour and talk shop. These are totally free and just an opportunity to ask us (or our community of experts) any questions you may have. You can register here: https://cloudposse.com/office-hoursJoin the conversation: https://slack.cloudposse.com/Find out how we can help your company:https://cloudposse.com/quizhttps://cloudposse.com/accelerate/Learn more about Cloud Posse:https://cloudposse.comhttps://github.com/cloudpossehttps://sweetops.com/https://newsletter.cloudposse.comhttps://podcast.cloudposse.com/- - -00:00:00​ Intro- - -00:01:25 Terraform 0.15 RC2 just releasedhttps://github.com/hashicorp/terraform/releases/tag/v0.15.0-rc2- - -00:02:05 Apache Mesos probably moving to “attic”https://lists.apache.org/x/thread.html/rab2a820507f7c846e54a847398ab20f47698ec5bce0c8e182bfe51ba%40%3Cdev.mesos.apache.org%3E- - -00:02:45 AWS Elasticsearch Announces “Auto-Tune”https://www.infoq.com/news/2021/04/amazon-elasticsearch-autotune/- - -00:06:05 AWS Announces Serial Console Access (for your pet servers)https://www.theregister.com/2021/04/01/aws_vm_serial_console/- - -00:06:55 GitHub Actions at war with Crypto Minershttps://therecord.media/github-investigating-crypto-mining-campaign-abusing-its-server-infrastructure/- - -00:08:57 PHP Git Repo (self-hosted) Hacked / Backdoor Installedhttps://www.theregister.com/2021/03/29/php_repository_infected/- - -00:11:00 Sponsor Cloud Posse / SweetOps / Office Hours for $1 / mo on GitHubhttps://github.com/sponsors/cloudposse- - -00:15:09 How to manage auto rotation of IAM User Access Keys within terraform- - -00:25:05 Istio upgrade vulnerability - - -00:26:16 Cloud Posse tutorials available - - -00:27:55 AWS CLI SDK copy AMI between regions - - -00:31:45 ChatOps engineering- - -00:36:10 Application custom metrics best practices- - -00:42:11 DevOps KPI metrics  - - -00:58:28 Outro- - -#officehours,#cloudposse,#sweetops,#devops,#sre,#terraform,#kubernetes,#awsSupport the show (https://cloudposse.com/office-hours/)

Can a chatbot make your team development process better? Carl and Richard talk to Phil Haack about his work building Ab.bot, a chatbot designed to work in Slack and Discord to help with building software - call it ChatOps - doing your development workflow with everyone able to see, sending commands through the bot. Phil talks about building add-ins to Ab.bot using C#, Python, and Javascript. ChatOps your way to an efficient team building great software!

Can a chatbot make your team development process better? Carl and Richard talk to Phil Haack about his work building Ab.bot, a chatbot designed to work in Slack and Discord to help with building software - call it ChatOps - doing your development workflow with everyone able to see, sending commands through the bot. Phil talks about building add-ins to Ab.bot using C#, Python, and Javascript. ChatOps your way to an efficient team building great software!Support this podcast at — https://redcircle.com/net-rocks/donations

Can a chatbot make your team development process better? Carl and Richard talk to Phil Haack about his work building Ab.bot, a chatbot designed to work in Slack and Discord to help with building software - call it ChatOps - doing your development workflow with everyone able to see, sending commands through the bot. Phil talks about building add-ins to Ab.bot using C#, Python, and Javascript. ChatOps your way to an efficient team building great software!Support this podcast at — https://redcircle.com/net-rocks/donations

In this episode, Quintessence Anx, Developer Advocate at PagerDuty where she helps to train people on patterns for notifications, alerts, stopping alerts, and stuff so you don't get woken up unless you absolutely really should be woken up, talks about battling alert fatigue, mean time to recovery and post-mortems as being not the way to measure things, the evolution of ChatOps, and why it’s important as a mentor to introduce newbies to your professional network.Should you find a burning need to share your thoughts or rants about the show, please spray them at devrel@newrelic.com. While you’re going to all the trouble of shipping us some bytes, please consider taking a moment to let us know what you’d like to hear on the show in the future. Despite the all-caps flaming you will receive in response, please know that we are sincerely interested in your feedback; we aim to appease. Follow us on the Twitters: @ObservyMcObserv.

Welcome to What Matters - a podcast from the folks at Mattermost! We are excited to talk about ChatOps, Open Source, DevOps, and the topics that matter most to you - our community!   We decided the best place to start would be at the beginning. So our Senior Developer Advocate, PJ Hagerty, sits down with Co-Founder and CEO Ian Tien to discuss where Mattermost started, why there is such a dedication to Open Source here, and where he sees Mattermost going in the future.

Jerry is joined by IBM Fellow and one of Forbes' “Top 20 Women in AI Research” Rama Akkiraju. They discuss AI for IT Operations (AIOps) and the incredible automation potential it has in the very near future. Rama introduces the idea of a “digital teammate” and explains how it all comes together in “ChatOps.”  Art by Matt Cardinal.

Unsere Themen:

Evan Culver builds developer tools at Segment, a customer data platform that lets product managers and software teams understand their users through data.Evan's career has spanned many years up and down the software stack, from frontend UI development to infrastructure and ops. For the past five years, his focus has been developer tooling and infrastructure, having worked on these during his tenure at Uber during its hypergrowth years and now on the dev tools team at Segment, where his charter is to "empower the engineers of Segment with the tools to automate, optimize, and streamline their workflows." In this episode, he explains to Beyang what exactly that means, discussing Segment's use of technologies from the AWS ecosystem, the popular open-source secret management tool they created, ChatOps, and various Docker- and Kubernetes-based tools that are useful for managing the deployment of many microservices.Show notes and transcript: https://about.sourcegraph.com/podcast/evan-culver

In this episode, we talk about SlackOps acquisitions, Slack downtime, Big Tech WFH policies, Op-ification (and automation) of Everything, and delivery metrics for DevOps. > Never miss a video // SUBSCRIBE: https://bit.ly/2PzTqAI // About The Ops Show // #TheOpsShow is a weekly YouTube show and podcast hosted by Tristan Pollock and Kyle Campbell covering the wide world of #workflows in #DevOps and the greater developer experience. Watch ALL EPISODES: https://bit.ly/2WgD1F5 + https://w.cto.ai/theopsshow > Join the community // SHIP TOGETHER: https://bit.ly/3fTPKpe // About CTO.ai // CTO.ai provides end-to-end serverless infrastructure designed for the needs of fast-moving development teams who want to optimize what the business cares about. Easy to use like Heroku, and powerful like Kubernetes, CTO.ai gives you the tools you need to workflow smarter, not harder. > Try out the platform: https://cto.ai/platform > Or come say hello: https://github.com/cto-ai https://twitter.com/CTO_ai https://www.linkedin.com/company/cto-ai/ https://www.instagram.com/cto.ai/ https://www.facebook.com/CTOdotAI/ https://www.twitch.tv/cto_ai

In this episode, we talk about DevOps technology, tools for remote work, ChatOps, the growing developer populace, TJ Holowaychuk, delivery metrics, and Kubernetes. > Never miss a video // SUBSCRIBE: https://bit.ly/2PzTqAI // About The Ops Show // #TheOpsShow is a weekly YouTube show and podcast hosted by Tristan Pollock and Kyle Campbell covering the wide world of #workflows in #DevOps and the greater developer experience. Watch ALL EPISODES: https://bit.ly/2WgD1F5 + https://w.cto.ai/theopsshow > Join the community // SHIP TOGETHER: https://bit.ly/3fTPKpe // About CTO.ai // CTO.ai provides end-to-end serverless infrastructure designed for the needs of fast-moving development teams who want to optimize what the business cares about. Easy to use like Heroku, and powerful like Kubernetes, CTO.ai gives you the tools you need to workflow smarter, not harder. > Try out the platform: https://cto.ai/platform > Or come say hello: https://github.com/cto-ai https://twitter.com/CTO_ai https://www.linkedin.com/company/cto-ai/ https://www.instagram.com/cto.ai/ https://www.facebook.com/CTOdotAI/ https://www.twitch.tv/cto_ai

Join me as I continue a series called Whiteboard Confessional with a look at the time Slackbot caused a company to experience a severity one incident which knocked their systems offline in an embarrassingly public way. Have a listen to learn how a nifty feature in Slack caused the issue, how things were working fine for four years before this problem reared its ugly head, why that’s a common occurrence, what you can do to avoid a similar fate, how this whole story should give you pause about hopping on the ChatOps bandwagon, what CloudTrail’s actual purpose is, and more.

Welcome to Episode 6 of our DevOps Podcast Series! In this episode, we do our best to summarize almost 8 hours of presentations from the Predict 2020 virtual conference held by devops.com. We break down 14 different presentations and try to capture the highlights of each and provide a summary that you can digest in the car on the way to the office. Hopefully, you will see what you care most about and dive deeper into the content they host on their site. https://predict2020.io/ See omnystudio.com/listener for privacy information.

Welcome to Episode 6 of our DevOps Podcast Series! In this episode, we do our best to summarize almost 8 hours of presentations from the Predict 2020 virtual conference held by devops.com. We break down 14 different presentations and try to capture the highlights of each and provide a summary that you can digest in the car on the way to the office. Hopefully, you will see what you care most about and dive deeper into the content they host on their site. https://predict2020.io/

Welcome to Episode 6 of our DevOps Podcast Series! In this episode, we do our best to summarize almost 8 hours of presentations from the Predict 2020 virtual conference held by devops.com. We break down 14 different presentations and try to capture the highlights of each and provide a summary that you can digest in the car on the way to the office. Hopefully, you will see what you care most about and dive deeper into the content they host on their site. https://predict2020.io/

Splunk is increasingly at the forefront of new approaches to IT Operations, especially in disruptive ‘cloud-native’ businesses. This session will help you understand how ‘New Ops’ techniques like Observability, Site Reliability Engineering, SLOs/SLIs, Error Budgets, ChatOps, and Blameless Post-Mortems can help your IT Ops team; and how you can adopt ‘New Ops’ technologies like Containers, Microservice Architectures, Machine Learning, Orchestration, Predictive Analytics, and AI for IT Ops. Speaker(s) Andi Mann, Chief Technology Advocate, Splunk Endre Peterfi, Staff Sales Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/IT1448.pdf?podcast=1577146211 Product: Splunk IT Service Intelligence, Splunk Machine Learning Toolkit, VictorOps Track: IT Operations Level: Intermediate

Splunk is increasingly at the forefront of new approaches to IT Operations, especially in disruptive ‘cloud-native’ businesses. This session will help you understand how ‘New Ops’ techniques like Observability, Site Reliability Engineering, SLOs/SLIs, Error Budgets, ChatOps, and Blameless Post-Mortems can help your IT Ops team; and how you can adopt ‘New Ops’ technologies like Containers, Microservice Architectures, Machine Learning, Orchestration, Predictive Analytics, and AI for IT Ops. Speaker(s) Andi Mann, Chief Technology Advocate, Splunk Endre Peterfi, Staff Sales Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/IT1448.pdf?podcast=1577146244 Product: Splunk IT Service Intelligence, Splunk Machine Learning Toolkit, VictorOps Track: IT Operations Level: Intermediate

Splunk is increasingly at the forefront of new approaches to IT Operations, especially in disruptive ‘cloud-native’ businesses. This session will help you understand how ‘New Ops’ techniques like Observability, Site Reliability Engineering, SLOs/SLIs, Error Budgets, ChatOps, and Blameless Post-Mortems can help your IT Ops team; and how you can adopt ‘New Ops’ technologies like Containers, Microservice Architectures, Machine Learning, Orchestration, Predictive Analytics, and AI for IT Ops. Speaker(s) Andi Mann, Chief Technology Advocate, Splunk Endre Peterfi, Staff Sales Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/IT1448.pdf?podcast=1577146263 Product: Splunk IT Service Intelligence, Splunk Machine Learning Toolkit, VictorOps Track: IT Operations Level: Intermediate

Can’t we just have a bot run our deployments? Yes we can. Here at Optum, our Splunk team has developed a hands-off method for deploying the Splunk Universal Forwarder on thousands of hosts in just minutes. With our automation we have been able to take advantage of bot integration via ChatOps to take care of our business needs, all while keeping our executives happy. Oh, and the backend configs? Yeah, we have tips on those too. Speaker(s) Shelbie Wise, Architecture Analyst, Optum Mitchell Peters, Sr Architecture Analyst, Optum Slides PDF link - https://conf.splunk.com/files/2019/slides/FN2156.pdf?podcast=1577146201 Product: Splunk Enterprise Track: Foundations/Platform Level: Intermediate

Can’t we just have a bot run our deployments? Yes we can. Here at Optum, our Splunk team has developed a hands-off method for deploying the Splunk Universal Forwarder on thousands of hosts in just minutes. With our automation we have been able to take advantage of bot integration via ChatOps to take care of our business needs, all while keeping our executives happy. Oh, and the backend configs? Yeah, we have tips on those too. Speaker(s) Shelbie Wise, Architecture Analyst, Optum Mitchell Peters, Sr Architecture Analyst, Optum Slides PDF link - https://conf.splunk.com/files/2019/slides/FN2156.pdf?podcast=1577146223 Product: Splunk Enterprise Track: Foundations/Platform Level: Intermediate

Splunk is increasingly at the forefront of new approaches to IT Operations, especially in disruptive ‘cloud-native’ businesses. This session will help you understand how ‘New Ops’ techniques like Observability, Site Reliability Engineering, SLOs/SLIs, Error Budgets, ChatOps, and Blameless Post-Mortems can help your IT Ops team; and how you can adopt ‘New Ops’ technologies like Containers, Microservice Architectures, Machine Learning, Orchestration, Predictive Analytics, and AI for IT Ops. Speaker(s) Andi Mann, Chief Technology Advocate, Splunk Endre Peterfi, Staff Sales Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/IT1448.pdf?podcast=1577146225 Product: Splunk IT Service Intelligence, Splunk Machine Learning Toolkit, VictorOps Track: IT Operations Level: Intermediate

Splunk is increasingly at the forefront of new approaches to IT Operations, especially in disruptive ‘cloud-native’ businesses. This session will help you understand how ‘New Ops’ techniques like Observability, Site Reliability Engineering, SLOs/SLIs, Error Budgets, ChatOps, and Blameless Post-Mortems can help your IT Ops team; and how you can adopt ‘New Ops’ technologies like Containers, Microservice Architectures, Machine Learning, Orchestration, Predictive Analytics, and AI for IT Ops. Speaker(s) Andi Mann, Chief Technology Advocate, Splunk Endre Peterfi, Staff Sales Engineer, Splunk Slides PDF link - https://conf.splunk.com/files/2019/slides/IT1448.pdf?podcast=1577146258 Product: Splunk IT Service Intelligence, Splunk Machine Learning Toolkit, VictorOps Track: IT Operations Level: Intermediate

Catch all the news (and there is a lot of it!) from KubeCon NA 2019 in this week’s show. We then talk to Vicki Cheung, the conference co-chair, and an Engineering Manager running Kubernetes infrastructure at Lyft. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod News of the week Docker sells its enterprise business: Mirantis press release Docker press release New Google Kubernetes Engine features: Preemptible VMs support is GA Node auto-provisioning is GA Vertical Pod Autoscaling is GA Batch on GKE is in Beta Surge upgrades are in Beta Google Cloud Run is GA Microsoft news: Secure enclave support in AKS Engine Azure Container Registry adds repository scoped permissions Kubernetes Event-Driven Autoscaling (KEDA) is 1.0 GitHub Actions for CNAB bundles & CNAB controller for Kubernetes Episode 61, with Jeremy Rickard and Ralph Squillace Helm 3 released, for real! Istio 1.4 released GitHub Octoverse Top and Trending Projects Kubernetes Security Announcement: CSI sidecar vulnerability Red Hat open-sources Quay and launches CodeReady Workspaces v2 VMware launches Crash Recovery and Enterprise PKS v1.6 CNCF announcements: 500 members New Platinum members: Arm, NetApp and Palo Alto Networks New Gold members: Equinix and Fidelity Investments Over 100 certified Kubernetes distributions Announcement of CNCF jobs board Datadog: Introducing Network Performance Monitoring 2019 Container Report What’s next for monitoring in Kubernetes? Gremlin launches chaos engineering for Kubernetes O’Reilly acquires Katacoda Kubernetes.io interactive training Mayadata adds Mayastor engine to OpenEBS PlanetScale launches CNDb Rancher announces k3s GA and Rio is in Beta Episode 57, with Darren Shepherd Cloud Native Security Hub from Sysdig Pipeline 2.0 Tech Preview from Banzai Cloud Episode 59, with Janos Matyas Clustered Microk8s from Ubuntu Episode 60, with Mark Shuttleworth Weave Flux and Argo CD join forces Portworx launches PX-Backup and PX-Autopilot Pulumi launches Crosswalk for Kubernetes, kx and .NET Core support Episode 76, with Joe Duffy Snyk Container Gloo 1.0 from Solo.io Episode 55, with Idit Levine Clusterman from Yelp adds Kubernetes Building Secure Reliable Systems book, new from Google Cloud A-Z Round: A10 Networks announced a Blueprint for automation of the Polynimbus secure application service Agile Stacks announced KubeFlex to aid in deploying and managing Kubernetes clusters in data centers and at the edge Alibaba Cloud released version alpha2 of the Open App Model Altinity announced their production-ready Kubernetes operator for ClickHouse data warehouses Aporeto launched new identity federation capabilities for Kubernetes and Istio Arrikto announced that MiniKF is now available on the GCP Marketplace Amazon has published a cost optimization guide for Kubernetes on AWS Buoyant launched Dive, a SaaS “team control plane” for Kubernetes clusters Chronosphere added tracing capabilities Containous launched a new Ambassador Program to reward and support Traefik community members Datawire announced a tool for automatic HTTPS for Kubernetes Ingress in Ambassador DeployHub announced the release of version 9.0 of their publishing and configuration offering DigitalOcean announced a Container Registry and a Kubernetes section in their 1-click apps market Fairwinds launched a new open source-as-a-service platform Insights, and Astro, a product for managing monitors in a dynamic environment Hammerspace announced a persistent data protection offering for Kubernetes Humio added streaming log management capabilities to their IBM Cloud Pak Hyscale has announced the open-sourcing of their app deployment tool Instana added support for Rancher Kublr announced Multi-Site Orchestration in Kublr 2.0 is now in Private Preview LINBIT announced Piraeus Datastore, a Software-Defined Storage offering for Kubernetes Maestro, from Cloud66, released a Kubernetes management tool for multi-cluster management Mattermost introduced ChatOps, an open source projects for real-time DevOps NetFoundry announced a programmable networking platform for apps at the edge NeuVector announced a Security Policy as Code tool for Kubernetes NS1 expanded their suite of integrations Opsani AI announced precision tuning for autoscalers Oracle announced Oracle API Gateway, Oracle Logging, and Kafka Compatibility for Oracle Streaming Redis Labs introduced RedisInsight Rookout announced a hybrid Kubernetes debugger for DevOps teams SignalFX announced Kubernetes Navigator to provide AI-driven insights StorageOS announced the release of version 1.5 Styra announced new features for their Compliance for Kubernetes tool Trilio announced support for TrilioVault on OpenShift Turbonomic announced Lemur, a New, Free, Observability Tool for developers Wallarm launched support for Envoy proxy and Envoy API protection with their SaaS Security product WhiteSource announced native integrations for top container registries Yugabyte announced YugabyteDB will be available as a self-managed database service on Crossplane Kubernetes clusters Zebrium announced that no-touch log monitoring for Kubernetes is now in private beta Links from the interview Duolingo OpenAI Lyft Engineering Episode 33: Envoy, with Matt Klein KubeCon NA 2019 Program co-chairs Episode 54: Tech, Life and KubeCon EU, with Bryan Liles Vicki Cheung on Twitter

ChatOps is not new! But many organizations have not understood nor leverage its full potential. The use cases spread from “What’s on todays cafeteria menu?” to “Deploy my latest Git commit as canary and scale based my SLOs!”.Listen to this podcast and learn from Nestor Zapata and Zohaib Hassan – both working at Citrix – on how they have started their ChatOps journey, how the built trust in the technology and how it helped them transform their organization towards more autonomy thanks to the self-service model enabled through the chat bots they developed. We discuss many of their self-service use cases such as Performance as a Self-Service or even Self-Healing which they implemented through Chat Bots integrated with Slack, Dynatrace, ServiceNow, Jira and other tools.If you want to see their chat ops in action watch our Performance Clinic on Automate Deployment and Site Reliability with Bots, ChatOps and Dynatracehttps://www.youtube.com/watch?v=xE_LMQ9u7l4

ChatOps is not new! But many organizations have not understood nor leverage its full potential. The use cases spread from “What’s on todays cafeteria menu?” to “Deploy my latest Git commit as canary and scale based my SLOs!”.Listen to this podcast and learn from Nestor Zapata and Zohaib Hassan – both working at Citrix – on how they have started their ChatOps journey, how the built trust in the technology and how it helped them transform their organization towards more autonomy thanks to the self-service model enabled through the chat bots they developed. We discuss many of their self-service use cases such as Performance as a Self-Service or even Self-Healing which they implemented through Chat Bots integrated with Slack, Dynatrace, ServiceNow, Jira and other tools.If you want to see their chat ops in action watch our Performance Clinic on Automate Deployment and Site Reliability with Bots, ChatOps and Dynatracehttps://www.youtube.com/watch?v=xE_LMQ9u7l4

פרק מספר 61 של באמפרס (377 למניין רברס עם פלטפורמה) - רן, אלון, ודותן מתאוששים מהבחירות (שוב) עם סקירה של טכנלוגיות ודברים מעניינים בשוק התוכנה הלוהט מהזמן האחרון, לפחות עד שיפורסמו התוצאות הרשמיות (ממשלת אחדות של React ו-Rust?! שמעתם את זה לראשונה כאן)רן - בלוג-פוסט מעניין שמגיע מ - Palo Alto Networks (שאחד ממייסדיה ישראלי) - השוואה של Security Features עבור Containers שונים - An Overview of Sandboxed Container Technologiesצעד אחורה לפני הצלילה - דוגמא נפוצה ל - Containers Technology זו Docker: טכנולוגיה שנחשבת פחות בטוחה מוירטואליזציה מלאה כיוון שכל ה-  Containers משתמשים באותו Kernel, ואעפ”י שננקטים הרבה צעדים על מנת לבודד בין ה - Containers השונים, הבידוד אף פעם לא מוחלט ותמיד יש חשש מזליגה של מידע או השפעה מאחד לשני - בעיה קיימת, שרירה וידועה בעולם ה - Containers נכון להיום, וכל הזמן מחפשים עבורה פתרונות שונים.הבלוג-פוסט המדובר מציג את מה שנחשב כ - state of the art נכון להיום: מה הן ה  -Containers Technologies הקיימות היום ואיזו רמה של בידוד נלקחת על מנת לספק רמה גבוהה יותר של Securityה - trade-off הקלאסי הוא Performance vs. Security.יש כאן תיאור של Use-cases שונים וגם תיאור הנדסי של איך כל טכנולוגיה עובדת, וזה מאוד מעניין.סקירה קצרה של מה שמתואר (אמ;לק) - לא טכנולוגית Containers (בתור התחלה . . . ) אבל נותנת מענה ל Use Case דומה - UniKernel: מעיין מערכת הפעלה שיש בה תוכנית אחת, למעשה - מערכת הפעלה שלמה שכל מה שהיא עושה זה להריץ את התוכנית שלכם (אם Zaphod Beeblebrox היה מתכנת וכו’); כיוון שכך - היא מאוד מוקשחת (כוללת רק את מה שהתוכנית שלכם צריכה - ולא יותר). כאמור - לא באמת Container אבל Use Case דומה - עם startup time מאוד קצר, מבנה מינימליסטי וכו’.מ-IBM מגיעה Container Technology בשם IBM Nabla - גם אם לא שמעתם על זה קודם (כאילו יש משהו של IBM שהוא לא AS400, Mainframe או משהו מהשכבה הגיאולוגית הזו כן שמעתם עליו), זה קיים - וברשימה.טכנולוגיה של Google בשם gVisor - טכנולוגיה שמשמשת את Google פנימית (וגם עבור App Engine לפני הרבה זמן), היום היא כבר מופיעה כקוד פתוח, ומהווה ברירת מחדל או משהו בסגנון עבור Kubernetes; מה שמעניין כאן הוא השימוש ב User-level Kernel - יש Kernel אבל ב - User level, כך שהוא לא משותף - אלא הרבה Kernels קטנים.יש את Amazon Firecracker - שעליו כבר דיברנו כמה פעמים (וגם כאן וכאן).וגם את OpenStack Kata - שגם עליו לא שמענו קודם (זאת אומרת - על OpenStack כן, Kata פחות - המושג עצמו מוסבר יפה ב - Phoenix Project).בסופו של דבר - סקירה מאוד יפה ומעמיקה מומלץ.אז בכל זאת TL;DR לאמ;לק? חלק מהטכנולוגיות ברמת בשלות גבוהה וחלק פחות; וכל אחת מהן לוקחת איזשהו Trade-off בין Performance ל - Security, וכל אחד צריך למצוא את המקום הנכון בשבילו - אין פתרון קסם אחד.יש גם טבלת סיכום בסוף המאמר, עם Features שונים כמו הפעלה דומה ל - Docker, האם הקוד פתוח (כן, כולם), וכו’ - יכול לעזור לבחור.בשורה התחתונה - אנחנו יודעים ש - Docker הכי פופלארי אם אתם בעניין של מיינסטרים (אפילו לא מופיע בסקירה . . . ), אבל גם סביר להניח שהוא הכי פחות בטוח (Secured), אז אם חשוב לכם Security כי למשל את מריצים workloads מגורמים שהם Un-trusted ואתם חייבים לשים לב; אם כל ה - workload שלכם פנימית אז הסכנה אולי פחות גדולה ועדיין מומלץ לשים לב ולמנוע מבעייה באחד ה - Containers לזלוג לאחרים.שורה תחתונה, שוב: ה - trade-off הקלאסי של Performance vs. Security, עם רמות בשלות שונות של הפלטפורמות השונות: gVisor ו - Firecracker ברמת בשלות גבוהה יחסית והשתיים האחרות פחות, אבל אף אחת לא פופלארית ברמה של Docker למשל.צריך לקחת בחשבון שלפעמים בענייני Security הדברים הכי פופלאריים הם גם הכי מסוכנים - אם מישהו מנסה Brut-force ויודע שרוב הסיכויים הם לנחות על Docker אז אולי ישקיע בזה יותר וזה סיכון.מצד אחד - אולי ככל שהפלטרפרומה יותר פופלארית כך היא תהווה מטרה יותר גדולה ל Hackers, ומצד שני  - יותר עיניים יסתכלו עליה כך שיותר באגים ימצאו ואולי כך היא תהפוך ליותר קשיחה. מאזן אימה . . .הבוטים באים! AWS Chatbot: ChatOps for AWSאיפה נועםר?אז AWS פרסמו פלטרפורמה בשם AWS Chatbot, שיכולה להוות נדבך משמעותי ב - Chat-Ops על AWS.רגע - ChatOps?מדובר ביכולת לנהל סביבת Production דרך צ’אט - אם זה Deployment או Provisioning למכונות, Scale up או Scale down, ניטור (Monitoring) . . . הכל דרך צ’אט.שיטה מקובלת בכל מיני חברות, אחת המפורסמות היא GitHub.יתרונות - שקיפות: אף פעם לא עושים SSH לאיזשהו Server, הכל דרך צ’אט אז כולם רואים מה קורה, וגם יכולים ללמוד איך לעשות את זה בפעם הבאה לבד.ובחזרה לאייטם - AWS Chatbot, מאפשרת לממש ChatOps על AWS.רן השתמש (בקטנה) לצרכי עבודה - פונקציות Lambda שמדווחות על Events ב-AWS, או כאלה ש”מאזינות לצ’אט” ועושות פעולות על AWS, ויש גם דברים אחרים.זו פלטפורמה קצת יותר הוליסטית, שיכולה להוות נקודת התחלה די טובה, בהנחה שאתם עובדים תחת AWS ורוצים ChatOps.אז עכשיו רק חסר להוסיף את זה עם פקודות קוליות ל Alexa . . . רק לחבר לשירות Text to Speech שלהם (Polly) וזהו?תכל’ס - מה הסיכוי שזה כבר קיים? כל ה-Echo Devices גם ככה מקשיבים כל הזמן, אז אפשר להתחיל להרים מכונות כבר כשמתמעורר הדיון בפינת הקפה, ואז כשסוף כל סוף מגיעה הפקודה זה מוכן ממש מהר. נשאר רק לממש Delay קטן כדי למנוע חשדות ולהפחית Creepiness .  . . אין על SkyNet.האם אפשר לשדר את כל הפקודות הקוליות בתדר שרק מכונות “שומעות”, ואז לעשות Hacking לכולם? בטח גם זה כבר קיים . . . מסביר מלא דברים.וברצינות (יחסית) - זה עובד רק על AWS או שניתן לבצע אינטגרציה עם מערכות אחרות?מה שהם מממשים עובד רק על AWS, עם ה - Backend של AWS - למשל EC2, ELB ,S3 וכאלה, אבל אפשר לקחת Design דומה, וקונספטואלית לעשות משהו דומה עבור פלטפורמה אחרת - וזה גם קיים -אחד הראשונים היה HUBOT של GitHub, והוא עדיין די פופלארי (על אף הרבה re-writes, במקור זה היה ב CoffeeScript, אבל יש מצב שיש כיום בעולם יותר מפתחי Cobol מ-CoffeeScript…)יש גם פלטפורמה חדשה שנכתבה ב-Go, עם השם הקליט joe…טרנד אחר שמתכתב עם זה הוא GitOps, אבל זה אולי לפעם אחרת.הכרזה של AWS על POP חדש בישראל - AWS CloudFront launches a POP in Israelלא פופ כזה . . . Point Of Presence - למעשה מדובר ב”קצה של ה-CDN” שנמצא בישראלגרם להתרגשות גדולה בקרב קהילת המפתחים בישראל (אלון בהדגמה חיה, פחות עובר בטקסט, דמיינו התרגשות).בסופו של דבר זה בסך הכל POP, ויכול קצת לזרז את הגישה ל-CDN של AWS, ואולי גם חישוביות במובן של Lambda@Edge, אבל כנראה שלא יותר מזה (חישוביות מוגבלת).ב-POP סטנדרטי של AWS יש CloudFront ו - Lambda@Edge (לא בכולם, כאן נראה שכן) - ודי זהו בגדול.מה הסיכוי שזה מתואם עם ההשקה של Amazon.com בישראל? אולי, אבל יש מצב שיותר קשור למכרזים ממשלתיים ש-AWS מתעניינת בהם (מול GCP ו-Azure בעיקר), ושכוללים בין השאר דרישה לתשתיות פיזיות בארץ, כך שאולי זה קשור כהכנה או משהו.אבל זה רק POP . . . פקידי הממשלה - שלא יעבדו עליכם! שוב . . . זה לא Storage וזה לא Compute - זו עדיין לא נוכחות “אמיתית”, אבל לפחות אנחנו על המפה ואנחנו נשארים במפה. הנה.בתיאוריה - יש את Lambda@Edge, אז ברמה התיאורטית אפשר “לעשות הכל” . . . זאת אומרת - רק דברים ש Lambda@Edge יכולה לעשות. יש מגבלות לעומת Lambda רגילה - שלחו גלויה אם אתם יודעים מה הן בדיוק (או בדקו ב Stack Overflow). בין הפותרים נכונה יוגרל פותר שלא ענה נכונה. או גלויה נוספת.ואם ב-AWS עסקינן - עוד הכרזה קטנה על Improved VPC networking for AWS Lambda functionsלמי שהתעסק על Functions ו-VPC יודע שהייתה בעיה בחיבור של Lambda עם VPC - כשה-Cold start עולה משמעותית יותר לאט (עד כדי 8-10 שניות, לעומת סדר גודל של עד שנייה אחת).יש לזה הרבה “תירוצים” של חיבורים ותשתיות וכו’עכשיו - נפתרה הבעיה, ובחיבור של Lambda עם VPC לא אמור להיות שינוי משמעותי ב-Cold start, שזה די מגניב כי זה הפריע לשימוש ב-Lambda במקרים מסויימים, למשל אם היה צריך להתחבר ל-Database שמאחורי VPC.האייטם הבא - GitHub: בהמשך להכרזה מלפני לא מעט זמן על GitHub Actions, אז GitHub Actions now supports CI/CD, free for public repositoriesהכרזה על Workflows, שזה בעצם CI/CD - בחינם עבור פרויקטים פומביים (Public).למעשה ניתן להשתמש עכשיו ב GitHub Actions על מנת להריץ CI, באותו אופן שבו יכולתם להריץ למשל CircleCI או Travis-CI וכו’.בכל מקרה - עכשיו זה מובנה בתוך GitHub וזה די נחמדרן כבר השתמש בזה בפרויקט (טיזר להמשך . . . )ה-Feature כולו עדיין ב-Beta, אבל אתם יכולים להגיש בקשה להתקבל ל-Beta (רן התקבל, רק אומרים).אז

It is a MASSIVE episode of updates that Simon and Nikki do their best to cover! There is also an EXTRA SPECIAL bonus just for AWS Podcast listeners! Special Discount for Intersect Tickets: https://int.aws/podcast use discount code 'podcast' - note that tickets are limited! Chapters: 02:19 Infrastructure 03:07 Storage 05:34 Compute 13:47 Network 14:54 Databases 17:45 Migration 18:36 Developer Tools 21:39 Analytics 29:25 IoT 33:24 End User Computing 34:08 Machine Learning 40:21 AR and VR 41:11 Application Integration 43:57 Management and Governance 48:04 Customer Engagement 49:13 Media 50:17 Mobile 50:36 Security 51:26 Gaming 51:39 Robotics 52:13 Training Shownotes: Special Discount for Intersect Tickets: https://int.aws/podcast use discount code 'podcast' - note that tickets are limited! Topic || Infrastructure Announcing the new AWS Middle East (Bahrain) Region | https://aws.amazon.com/about-aws/whats-new/2019/07/announcing-the-new-aws-middle-east--bahrain--region-/ Topic || Storage EBS default volume type updated to GP2 | https://aws.amazon.com/about-aws/whats-new/2019/07/ebs-default-volume-type-updated-to-gp2/ AWS Backup will Automatically Copy Tags from Resource to Recovery Point | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-backup-will-automatically-copy-tags-from-resource-to-recovery-point/ Configuration update for Amazon EFS encryption of data in transit | https://aws.amazon.com/about-aws/whats-new/2019/07/configuration-update-for-amazon-efs-encryption-data-in-transit/ AWS Snowball and Snowball Edge available in Seoul – Amazon Web Services | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-snowball-and-aws-snowball-edge-available-in-asia-pacific-seoul-region/ Amazon S3 adds support for percentiles on Amazon CloudWatch Metrics | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-s3-adds-support-for-percentiles-on-amazon-cloudwatch-metrics/ Amazon FSx Now Supports Windows Shadow Copies for Restoring Files to Previous Versions | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-fsx-now-supports-windows-shadow-copies-for-restoring-files-to-previous-versions/ Amazon CloudFront Announces Support for Resource-Level and Tag-Based Permissions | https://aws.amazon.com/about-aws/whats-new/2019/08/cloudfront-resource-level-tag-based-permission/ Topic || Compute Amazon EC2 AMD Instances are Now Available in additional regions | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-amd-instances-available-in-additional-regions/ Amazon EC2 P3 Instances Featuring NVIDIA Volta V100 GPUs now Support NVIDIA Quadro Virtual Workstation | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-p3-nstances-featuring-nvidia-volta-v100-gpus-now-support-nvidia-quadro-virtual-workstation/ Introducing Amazon EC2 I3en and C5n Bare Metal Instances | https://aws.amazon.com/about-aws/whats-new/2019/08/introducing-amazon-ec2-i3en-and-c5n-bare-metal-instances/ Amazon EC2 C5 New Instance Sizes are Now Available in Additional Regions | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-ec2-c5-new-instance-sizes-are-now-available-in-additional-regions/ Amazon EC2 Spot Now Available for Red Hat Enterprise Linux (RHEL) | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-spot-now-available-red-hat-enterprise-linux-rhel/ Amazon EC2 Now Supports Tagging Launch Templates on Creation | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-now-supports-tagging-launch-templates-on-creation/ Amazon EC2 On-Demand Capacity Reservations Can Now Be Shared Across Multiple AWS Accounts | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-on-demand-capacity-reservations-shared-across-multiple-aws-accounts/ Amazon EC2 Fleet Now Lets You Modify On-Demand Target Capacity | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-ec2-fleet-modify-on-demand-target-capacity/ Amazon EC2 Fleet Now Lets You Set A Maximum Price For A Fleet Of Instances | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-ec2-fleet-now-lets-you-submit-maximum-price-for-fleet-of-instances/ Amazon EC2 Hibernation Now Available on Ubuntu 18.04 LTS | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ec2-hibernation-now-available-ubuntu-1804-lts/ Amazon ECS services now support multiple load balancer target groups | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ecs-services-now-support-multiple-load-balancer-target-groups/ Amazon ECS Console now enables simplified AWS App Mesh integration | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ecs-console-enables-simplified-aws-app-mesh-integration/ Amazon ECR now supports increased repository and image limits | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ecr-now-supports-increased-repository-and-image-limits/ Amazon ECR Now Supports Immutable Image Tags | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-ecr-now-supports-immutable-image-tags/ Amazon Linux 2 Extras now provides AWS-optimized versions of new Linux Kernels | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-linux-2-extras-provides-aws-optimized-versions-of-new-linux-kernels/ Lambda@Edge Adds Support for Python 3.7 | https://aws.amazon.com/about-aws/whats-new/2019/08/lambdaedge-adds-support-for-python-37/ AWS Batch Now Supports the Elastic Fabric Adapter | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-batch-now-supports-elastic-fabric-adapter/ Topic || Network Elastic Fabric Adapter is officially integrated into Libfabric Library | https://aws.amazon.com/about-aws/whats-new/2019/07/elastic-fabric-adapter-officially-integrated-into-libfabric-library/ Now Launch AWS Glue, Amazon EMR, and AWS Aurora Serverless Clusters in Shared VPCs | https://aws.amazon.com/about-aws/whats-new/2019/08/now-launch-aws-glue-amazon-emr-and-aws-aurora-serverless-clusters-in-shared-vpcs/ AWS DataSync now supports Amazon VPC endpoints | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-datasync-now-supports-amazon-vpc-endpoints/ AWS Direct Connect Now Supports Resource Based Authorization, Tag Based Authorization, and Tag on Resource Creation | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-direct-connect-now-supports-resource-based-authorization-tag-based-authorization-tag-on-resource-creation/ Topic || Databases Amazon Aurora Multi-Master is Now Generally Available | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-aurora-multimaster-now-generally-available/ Amazon DocumentDB (with MongoDB compatibility) Adds Aggregation Pipeline and Diagnostics Capabilities | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-documentdb-with-mongodb-compatibility-adds-aggregation-pipeline-and-diagnostics-capabilities/ Amazon DynamoDB now helps you monitor as you approach your account limits | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-dynamodb-now-helps-you-monitor-as-you-approach-your-account-limits/ Amazon RDS for Oracle now supports new instance sizes | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-rds-for-oracle-now-supports-new-instance-sizes/ Amazon RDS for Oracle Supports Oracle Management Agent (OMA) version 13.3 for Oracle Enterprise Manager Cloud Control 13c | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-rds-for-oracle-supports-oracle-management-agent-oma-version133-for-oracle-enterprise-manager-cloud-control13c/ Amazon RDS for Oracle now supports July 2019 Oracle Patch Set Updates (PSU) and Release Updates (RU) | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-rds-for-oracle-supports-july-2019-oracle-patch-set-and-release-updates/ Amazon RDS SQL Server now supports changing the server-level collation | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-rds-sql-server-supports-changing-server-level-collation/ PostgreSQL 12 Beta 2 Now Available in Amazon RDS Database Preview Environment | https://aws.amazon.com/about-aws/whats-new/2019/08/postgresql-beta-2-now-available-in-amazon-rds-database-preview-environment/ Amazon Aurora with PostgreSQL Compatibility Supports Publishing PostgreSQL Log Files to Amazon CloudWatch Logs | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-aurora-with-postgresql-compatibility-support-logs-to-cloudwatch/ Amazon Redshift Launches Concurrency Scaling in Five additional AWS Regions, and Enhances Console Performance Graphs in all supported AWS Regions | https://aws.amazon.com/about-aws/ whats-new/2019/08/amazon-redshift-launches-concurrency-scaling-five-additional-regions-enhances-console-performance-graphs/ Amazon Redshift now supports column level access control with AWS Lake Formation | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-redshift-spectrum-now-supports-column-level-access-control-with-aws-lake-formation/ Topic || Migration AWS Migration Hub Now Supports Import of On-Premises Server and Application Data From RISC Networks to Plan and Track Migration Progress | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-migration-hub-supports-import-of-on-premises-server-application-data-from-risc-networks-to-track-migration-progress/ Topic || Developer Tools AWS CodePipeline Achieves HIPAA Eligibility | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-codepipeline-achieves-hipaa-eligibility/ AWS CodePipeline Adds Pipeline Status to Pipeline Listing | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-codepipeline-adds-pipeline-status-to-pipeline-listing/ AWS Amplify Console adds support for automatically deploying branches that match a specific pattern | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-amplify-console-support-git-based-branch-pattern-detection/ Amplify Framework Adds Predictions Category | https://aws.amazon.com/about-aws/whats-new/2019/07/amplify-framework-adds-predictions-category/ Amplify Framework adds local mocking and testing for GraphQL APIs, Storage, Functions, and Hosting | https://aws.amazon.com/about-aws/whats-new/2019/08/amplify-framework-adds-local-mocking-and-testing-for-graphql-apis-storage-functions-hostings/ Topic || Analytics AWS Lake Formation is now generally available | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-lake-formation-is-now-generally-available/ Announcing PartiQL: One query language for all your data | https://aws.amazon.com/blogs/opensource/announcing-partiql-one-query-language-for-all-your-data/ AWS Glue now supports the ability to run ETL jobs on Apache Spark 2.4.3 (with Python 3) | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-glue-now-supports-ability-to-run-etl-jobs-apache-spark-243-with-python-3/ AWS Glue now supports additional configuration options for memory-intensive jobs submitted through development endpoints | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-glue-now-supports-additional-configuration-options-for-memory-intensive-jobs-submitted-through-deployment-endpoints/ AWS Glue now provides the ability to bookmark Parquet and ORC files using Glue ETL jobs | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-glue-now-provides-ability-to-bookmark-parquet-and-orc-files-using-glue-etl-jobs/ AWS Glue now provides FindMatches ML transform to deduplicate and find matching records in your dataset | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-glue-provides-findmatches-ml-transform-to-deduplicate/ Amazon QuickSight adds support for custom colors, embedding for all user types and new regions! | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-quicksight-adds-support-for-custom-colors-embedding-for-all-user-types-and-new-regions/ Achieve 3x better Spark performance with EMR 5.25.0 | https://aws.amazon.com/about-aws/whats-new/2019/08/achieve-3x-better-spark-performance-with-emr-5250/ Amazon EMR now supports native EBS encryption | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon_emr_now_supports_native_ebs_encryption/ Amazon Athena adds Support for AWS Lake Formation Enabling Fine-Grained Access Control on Databases, Tables, and Columns | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-athena-adds-support-for-aws-lake-formation-enabling-fine-grained-access-control-on-databases-tables-columns/ Amazon EMR Integration With AWS Lake Formation Is Now In Beta, Supporting Database, Table, and Column-level access controls for Apache Spark | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-emr-integration-with-aws-lake-formation-now-in-beta-supporting-database-table-column-level-access-controls/ Topic || IoT AWS IoT Device Defender Expands Globally | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-iot-device-defender-expands-globally/ AWS IoT Device Defender Supports Mitigation Actions for Audit Results | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-iot-device-defender-supports-mitigation-actions-for-audit-results/ AWS IoT Device Tester v1.3.0 is Now Available for Amazon FreeRTOS 201906.00 Major | https://aws.amazon.com/about-aws/whats-new/2019/07/aws_iot_device_tester_v130_for_amazon_freertos_201906_00_major/ AWS IoT Events actions now support AWS Lambda, SQS, Kinesis Firehose, and IoT Events as targets | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-iot-events-supports-invoking-actions-to-lambda-sqs-kinesis-firehose-iot-events/ AWS IoT Events now supports AWS CloudFormation | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-iot-events-now-supports-aws-cloudformation/ Topic || End User Computing AWS Client VPN now adds support for Split-tunnel | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-client-vpn-now-adds-support-for-split-tunnel/ Introducing AWS Chatbot (beta): ChatOps for AWS in Amazon Chime and Slack Chat Rooms | https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-aws-chatbot-chatops-for-aws/ Amazon AppStream 2.0 Adds CLI Operations for Programmatic Image Creation | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-appstream-2-adds-cli-operations-for-programmatic-image-creation/ NICE DCV Releases Version 2019.0 with Multi-Monitor Support on Web Client | https://aws.amazon.com/about-aws/whats-new/2019/08/nice-dcv-releases-version-2019-0-with-multi-monitor-support-on-web-client/ New End User Computing Competency Solutions | https://aws.amazon.com/about-aws/whats-new/2019/08/end-user-computing-competency-solutions/ Amazon WorkDocs Migration Service | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon_workdocs_migration_service/ Topic || Machine Learning SageMaker Batch Transform now enables associating prediction results with input attributes | https://aws.amazon.com/about-aws/whats-new/2019/07/sagemaker-batch-transform-enable-associating-prediction-results-with-input-attributes/ Amazon SageMaker Ground Truth Adds Data Labeling Workflow for Named Entity Recognition | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-sagemaker-ground-truth-adds-data-labeling-workflow-for-named-entity-recognition/ Amazon SageMaker notebooks now available with pre-installed R kernel | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-sagemaker-notebooks-available-with-pre-installed-r-kernel/ New Model Tracking Capabilities for Amazon SageMaker Are Now Generally Available | https://aws.amazon.com/about-aws/whats-new/2019/08/new-model-tracking-capabilities-for-amazon-sagemaker-now-generally-available/ Amazon Comprehend Custom Entities now supports multiple entity types | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-comprehend-custom-entities-supports-multiple-entity-types/ Introducing Predictive Maintenance Using Machine Learning | https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-predictive-maintenance-using-machine-learning/ Amazon Transcribe Streaming Now Supports WebSocket | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-transcribe-streaming-now-supports-websocket/ Amazon Polly Launches Neural Text-to-Speech and Newscaster Voices | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-polly-launches-neural-text-to-speech-and-newscaster-voices/ Manage a Lex session using APIs on the client | https://aws.amazon.com/about-aws/whats-new/2019/08/manage-a-lex-session-using-apis-on-the-client/ Amazon Rekognition now detects violence, weapons, and self-injury in images and videos; improves accuracy for nudity detection | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-rekognition-now-detects-violence-weapons-and-self-injury-in-images-and-videos-improves-accuracy-for-nudity-detection/ Topic || AR and VR Amazon Sumerian Now Supports Physically-Based Rendering (PBR) | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-sumerian-now-supports-physically-based-rendering-pbr/ Topic || Application Integration Amazon SNS Message Filtering Adds Support for Attribute Key Matching | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-sns-message-filtering-adds-support-for-attribute-key-matching/ Amazon SNS Adds Support for AWS X-Ray | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-sns-adds-support-for-aws-x-ray/ Temporary Queue Client Now Available for Amazon SQS | https://aws.amazon.com/about-aws/whats-new/2019/07/temporary-queue-client-now-available-for-amazon-sqs/ Amazon MQ Adds Support for AWS Key Management Service (AWS KMS), Improving Encryption Capabilities | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-mq-adds-support-for-aws-key-management-service-improving-encryption-capabilities/ Amazon MSK adds support for Apache Kafka version 2.2.1 and expands availability to EU (Stockholm), Asia Pacific (Mumbai), and Asia Pacific (Seoul) | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-msk-adds-support-apache-kafka-version-221-expands-availability-stockholm-mumbai-seoul/ Amazon API Gateway supports secured connectivity between REST APIs & Amazon Virtual Private Clouds in additional regions | https://aws.amazon.com/about-aws/whats-new/2019/08/amazon-api-gateway-supports-secured-connectivity-between-reset-apis-and-amazon-virtual-private-clouds-in-additional-regions/ Topic || Management and Governance AWS Cost Explorer now Supports Usage-Based Forecasts | https://aws.amazon.com/about-aws/whats-new/2019/07/usage-based-forecasting-in-aws-cost-explorer/ Introducing Amazon EC2 Resource Optimization Recommendations | https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-amazon-ec2-resource-optimization-recommendations/ AWS Budgets Announces AWS Chatbot Integration | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-budgets-announces-aws-chatbot-integration/ Discovering Documents Made Easy in AWS Systems Manager Automation | https://aws.amazon.com/about-aws/whats-new/2019/07/discovering-documents-made-easy-in-aws-systems-manager-automation/ AWS Systems Manager Distributor makes it easier to create distributable software packages | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-systems-manager-distributor-makes-it-easier-to-create-distributable-software-packages/ Now use AWS Systems Manager Maintenance Windows to select resource groups as targets | https://aws.amazon.com/about-aws/whats-new/2019/07/now-use-aws-systems-manager-maintenance-windows-to-select-resource-groups-as-targets/ Use AWS Systems Manager to resolve operational issues with your .NET and Microsoft SQL Server Applications | https://aws.amazon.com/about-aws/whats-new/2019/08/use-aws-systems-manager-to-resolve-operational-issues-with-your-net-and-microsoft-sql-server-applications/ CloudWatch Logs Insights adds cross log group querying | https://aws.amazon.com/about-aws/whats-new/2019/07/cloudwatch-logs-insights-adds-cross-log-group-querying/ AWS CloudFormation now supports higher StackSets limits | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-cloudformation-now-supports-higher-stacksets-limits/ Topic || Customer Engagement Introducing AI-Driven Social Media Dashboard | https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-ai-driven-social-media-dashboard/ New Amazon Connect integration for ChoiceView from Radish Systems on AWS | https://aws.amazon.com/about-aws/whats-new/2019/07/new-amazon-connect-integration-for-choiceview-from-radish-systems-on-aws/ Amazon Pinpoint Adds Campaign and Application Metrics APIs | https://aws.amazon.com/about-aws/whats-new/2019/07/amazon-pinpoint-adds-campaign-and-application-metrics-apis/ Topic || Media AWS Elemental Appliances and Software Now Available in the AWS Management Console | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-elemental-appliances-and-software-now-available-in-aws-management-console/ AWS Elemental MediaConvert Expands Audio Support and Improves Performance | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-elemental-mediaconvert-expands-audio-support-and-improves-performance/ AWS Elemental MediaConvert Adds Ability to Prioritize Transcoding Jobs | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-elemental-mediaconvert-adds-ability-to-prioritize-transcoding-jobs/ AWS Elemental MediaConvert Simplifies Editing and Sharing of Settings | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-elemental-mediaconvert-simplifies-editing-and-sharing-of-settings/ AWS Elemental MediaStore Now Supports Resource Tagging | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-elemental-mediastore-now-supports-resource-tagging/ AWS Elemental MediaLive Enhances Support for File-Based Inputs for Live Channels | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-elemental-medialive-enhances-support-for-file-based-inputs-for-live-channels/ Topic || Mobile AWS Device Farm improves device start up time to enable instant access to devices | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-device-farm-improves-device-start-up-time-to-enable-instant-access-to-devices/ Topic || Security Introducing the Amazon Corretto Crypto Provider (ACCP) for Improved Cryptography Performance | https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-the-amazon-corretto-crypto-provider/ AWS Secrets Manager now supports VPC endpoint policies | https://aws.amazon.com/about-aws/whats-new/2019/07/AWS-Secrets-Manager-now-supports-VPC-endpoint-policies/ Topic || Gaming Lumberyard Beta 1.20 Now Available | https://aws.amazon.com/about-aws/whats-new/2019/07/lumberyard-beta-120-now-available/ Topic || Robotics AWS RoboMaker now supports offline logs and metrics for the AWS RoboMaker CloudWatch cloud extension | https://aws.amazon.com/about-aws/whats-new/2019/07/aws-robomaker-now-supports-offline-logs-metrics-aws-robomaker-cloudwatch-cloud-extension/ Topic || Training New AWS Certification Exam Vouchers Make Certifying Groups Easier | https://aws.amazon.com/about-aws/whats-new/2019/07/new-aws-certification-exam-vouchers-make-certifying-groups-easier/ Announcing New Resources and Website to Accelerate Your Cloud Adoption | https://aws.amazon.com/about-aws/whats-new/2019/07/announcing-new-resources-and-website-to-accelerate-your-cloud-adoption/ AWS Developer Series Relaunched on edX | https://aws.amazon.com/about-aws/whats-new/2019/08/aws-developer-series-relaunched-on-edx/

This week my homie supreme, Jason Hand joins me on On-Call Nightmares. We talk monitoring, SRE and getting in the van. Jason has spent the last 5 years connecting with technologists around the world on ideas related to balancing system and service reliability with the speed and agility required in today's digital world. Previously at VictorOps, Jason authored four books on the subjects of Site Reliability Engineering, Post-Incident Reviews, and ChatOps and was named "DevOps Evangelist of the Year" in 2016 by DevOps.com. Co-organizer and emcee of the annual DevOpsDays Rockies conference, the Frontrange Site Reliability Meetup, Denver DevOps Meetup, and DevOps Road Trip, Jason enjoys connecting story tellers and actionable ideas with those who are hungry to learn. Co-host of the podcast "Community Pulse", Jason helps to bring together ideas and expertise as it relates to building community within tech (I.e. advocacy, evangelism). In his spare time, you'll find Jason soaking up the beautiful Colorado outdoors on a trail, lake, river, or mountain by day and enjoying craft IPA's and bluegrass music by night. Transcript: https://aka.ms/AA5q317 https://twitter.com/jasonhand

Jason Palmer is the Product Manager of Web Infrastructure at Spotify and core Jest team member. He joins us on The Undefined to talk about engineering team management, avoiding useless meetings, optimal testing strategies, and getting swole AF for conference season.FeaturingJason Palmer - Twitter, GithubKen Wheeler – Twitter, GitHub, WebsiteJared Palmer – Twitter, GitHub, WebsiteLinks"You don't need standup" by Jason PalmerAstro EmailTwistMinecraft Redstone CircuitSpotify audio visualizerWinamp visualizerVisual BasicWebflowAssert(JS) ConfCypress.io"Write tests. Not too many. Mostly integration." by Kent C. DoddsKent C. Dodds's Testing TrophyPicksDebowa VodkaNative Instruments MaschineNobuJarvis DeskJestXenoblade 2Google StadiaGFuel

This article and episode is aimed at a technical audience: architects, developers and release managers. A foundation for rapidly building microservices on Kubernetes We’re looking now at the DevOps stack we’re building with, notably the stack that we are using to build Glu (https://www.glu.lu/ (https://www.glu.lu/?utm_source=ep08&utm_medium=Podcast&utm_campaign=345TechTalks) ) that will go into live Beta next month. If you’ve been following the podcast series you’ll know that we’re building a microservices platform leaning heavily on Kubernetes hosted in AWS. The tech stack we describe here is our way of doing this – if you’re looking to put in place a similar stack elsewhere you should be able to get some great ideas from what we’re discussing here. You can always book a free call with us to talk about your technology stack and your DevOps needs, we love hearing from you! Going through the stack one piece at a time We’ll step through the stack piece by piece and explain what we use each of these for. This is a whistlestop tour of what we discuss in the episode, so please take time to listen to the episode in full! GitHub As we’ve said in the last episode (https://www.345.systems/podcast/episode-6-our-10-principles-for-devops-part-one/) , Git is the source of truth. This is true for both infrastructure and applications. You can use any flavour of Git; we have chosen GitHub (https://github.com/) for a number of reasons: Cloud-based, no maintenance, developers can access from anywhere. The ecosystem of apps that play well with GitHub via webhooks. The tooling around pull requests, branch permissions and protecting branches, meaning we can keep our core code branches clean, tested and high quality. Shippable We use a cloud-based CI tool called Shippable (https://www.shippable.com/) that integrates with GitHub. This runs our CI process. We use this because: Builds run in containers so we can control the build stack easily. It works well with GitHub for reporting build success and code coverage. It’s easy to use. It’s inexpensive. It’s cloud-based and hosted. Minimal maintenance. Spinnaker We use Spinnaker (https://www.spinnaker.io/) as a deployment platform. We host this in AWS using a dedicated Kubernetes cluster just for Spinnaker. This is because the DevOps tools need to run outside of the other environments. Spinnaker comes from the Netflix stable, and supports a number of deployment models we’re interested in using such as canary and blue-green. Pypyr Pypyr (https://github.com/pypyr) is an opensource pipeline runner developer by fellow 345 partner Thomas (https://www.345.systems/author/thomas/) . We use Pypyr because it lets us do many of the DevOps tasks that you normally write shell scripts for, but Pypyr lets you express them as YAML files. This gives us a more readable script, plus the underlying code to execute the steps is tested and high quality. ClickUp We use ClickUp (https://clickup.com/) for project management. Tasks integrate with GitHub well, and the software is not opinionated in how it is used, unlike some others (JIRA, we might be looking at you here). ClickUp lets us organise tasks very flexibly through its tagging system, which lets a task belong to multiple hierarchies at the same time. We can prioritise, organise by actor, organise by size, area of the system. It’s easy to search, filter and update. The software is still maturing and there are areas where it can be seen as weak, however the flexibility we gain more than offsets this (to us, at any rate). Developer Workstation We use a posix workstation for development. A lot of the devs like to work natively on Macs, whereas if you’re on Windows we use virtual machines running a flavour of Linux. Arch Linux (https://www.archlinux.org/) is a popular one, as it’s so lean. IDE We are not prescriptive about IDE, but our default choice is Visual Studio Code (https://code.visualstudio.com/) . Some of the guys use other editors, it depends on their personal choice. Slack For internal communications we use Slack (https://slack.com/) . This gives us a flexible ChatOps platform that integrates with the tools above so we get a feed from GitHub for pull requests and merges, we get a feed from Shippable for builds, and we can get feeds from ClickUp when actions have taken place on tasks.

Long-time Dynatracer Nestor Zapata chats with us about Citrix’s fundamental shift from reactive to proactive and predictive operations; moving from data sets and charts to AI-powered answers. His session detailed advantages of a “Gen 3” monitoring approach and how to get there.

Long-time Dynatracer Nestor Zapata chats with us about Citrix’s fundamental shift from reactive to proactive and predictive operations; moving from data sets and charts to AI-powered answers. His session detailed advantages of a “Gen 3” monitoring approach and how to get there.

Long-time Dynatracer Nestor Zapata chats with us about Citrix’s fundamental shift from reactive to proactive and predictive operations; moving from data sets and charts to AI-powered answers. His session detailed advantages of a “Gen 3” monitoring approach and how to get there.

Long-time Dynatracer Nestor Zapata chats with us about Citrix’s fundamental shift from reactive to proactive and predictive operations; moving from data sets and charts to AI-powered answers. His session detailed advantages of a “Gen 3” monitoring approach and how to get there.

In this episode, Sean Martin is joined by Dinis Cruz, the CISO for the Photobox Group, to talk about automating and scaling the end user security awareness decision-making process through the use of ChatOps — which is essentially the use of a chat platform and supporting technologies to operationalize and decentralize the sharing of information and decisions. One key point that Dinis makes as he walks us through some real-world scenarios he is implementing is that security teams often make the mistake of trying to own everything. Dinis suggests that there is value in the security team focusing on demonstrating what can be done through a quick proof of concept and then to hand the project over to others within the organization that have the resources and deep skillsets to see the project reach its full potential. There are a number of great nuggets in here from Dinis — we hope you enjoy the conversation.

Join Ashish Nanotkar, CTO at Yash Solutions, as he introduces their Red Hat certified container – YashOne. YashOne is an AI powered event-trigger based integration platform that integrates all your IT tools into one system and provides GUI, API, CLI and ChatOps access to manage workflows in an automated self healing fashion.

Si quieres ver el vídeo con slides: https://youtu.be/hVJ_xKLudnk La automatización es una tarea muy importante en el flujo del desarrollo de software, pero ¿sabemos cuando debemos aplicarla? ¿que beneficios podemos obtener? Estamos acostumbrados a aplicar buenas prácticas en el código y en los tests, pero muchas veces dejamos en un segundo plano la automatización de ciertas tareas y las cuales afectan directamente a nuestra productividad. En esta charla hablaré de diversos aspectos que considero importantes a la hora de automatizar y algunos de los procesos que utilizo en mi día a día, como herramientas de generación automática de código, automatización de despliegues, automatización de tests utilizando contenedores(Docker-in-Docker vs Docker-outside-Docker) y bots para gestión operacional desde herramientas de mensajería(ejemplo práctico utilizando Hubot de github para ChatOps). Puedes ver la charla en video: https://youtu.be/hVJ_xKLudnk

Keith Hoodlet and Paul Asadoorian talk about The Apache Struts2 RCE Vulnerability. They cover: - CVE-2018-11776 - How the 3 Ways of DevOps can guide us toward better security practices - Shared Version Control - Test Environments - Shared Ticketing - ChatOps - Buying Time Full Show Notes: https://wiki.securityweekly.com/ASW_Episode30 Follow us on Twitter: https://www.twitter.com/securityweekly

Keith Hoodlet and Paul Asadoorian talk about The Apache Struts2 RCE Vulnerability. They cover: - CVE-2018-11776 - How the 3 Ways of DevOps can guide us toward better security practices - Shared Version Control - Test Environments - Shared Ticketing - ChatOps - Buying Time Full Show Notes: https://wiki.securityweekly.com/ASW_Episode30 Follow us on Twitter: https://www.twitter.com/securityweekly

On this episode of Datanauts, we chat with Brandon Olin, the creator of PoshBot, a PowerShell based chatbot for ops teams. What does PoshBot do? How was PoshBot built? How do chatbots impact Brandon's delivery model? The post Datanauts 136: ChatOps Using PoshBot With Brandon Olin appeared first on Packet Pushers.

On this episode of Datanauts, we chat with Brandon Olin, the creator of PoshBot, a PowerShell based chatbot for ops teams. What does PoshBot do? How was PoshBot built? How do chatbots impact Brandon's delivery model? The post Datanauts 136: ChatOps Using PoshBot With Brandon Olin appeared first on Packet Pushers.

On this episode of Datanauts, we chat with Brandon Olin, the creator of PoshBot, a PowerShell based chatbot for ops teams. What does PoshBot do? How was PoshBot built? How do chatbots impact Brandon's delivery model? The post Datanauts 136: ChatOps Using PoshBot With Brandon Olin appeared first on Packet Pushers.

Arnab Sinha ( https://www.linkedin.com/in/arnabsinha4u/ ), Continuous Delivery and ChatOps expert, gave us a great overview on ChatOps, how to get started, how to proof the value and how to scale. More details about his talk on the DevOps Tallinn website. ( https://www.topconf.com/conference/devops-tallinn-2018/talk/chatops-what-s-how-s-possibilities/ )

Arnab Sinha ( https://www.linkedin.com/in/arnabsinha4u/ ), Continuous Delivery and ChatOps expert, gave us a great overview on ChatOps, how to get started, how to proof the value and how to scale. More details about his talk on the DevOps Tallinn website. ( https://www.topconf.com/conference/devops-tallinn-2018/talk/chatops-what-s-how-s-possibilities/ )

On this episode, our very own chatbot expert, Daniel Pritchett, joins Mo and Ben to discuss chat as a service. While there is a lot of hype around chatbots recently, these engineers decode chat as a platform and engage in all kinds of fun along the way. Listen in to hear about the implicit increases in efficiency, knowledge sharing, and time savings that can come with chatbots. Also, look out for Daniel’s talk at Southeast Ruby in October and his upcoming book! ##Things Mentioned Github’s hubot Astro Mail Crowdfire Slackbot Facebook Messenger Memtech Memtech's Elvis Bot IFTTT (If This Then That) Heroku ChatOps Jira Jenkins ELIZA Zork Microsoft Bot Framework For more information, check out our website at clearfunction.com. Follow us on Twitter at @clearfunction.

Server administration is an activity that often happens in an isolated context in a terminal. ChatOps is a way of bringing that work into a shared environment and unlocking more collaboration. This week Jacob Tomlinson talks about the work he has done on opsdroid, a new bot framework targeted at tying together the various services and environments that modern production systems rely on.

In this episode of the ARCHITECHT AI and Robot Show, Derrick Harris speaks with Demisto co-founder Rishi Bhargava about the state of cybersecurity, and how machine learning can help bring order to the chaos. Bhargava discusses current threat vectors and the shortcomings of many response tactics, and explains how Demisto's technology uses ChatOps to analyze response behavior, suggest courses of action, and give security personnel a single point of interaction across dozens of tools. In the news segment, co-hosts Derrick Harris, Signe Brewster and Chris Albrecht discuss, among other things, Drive.ai's big funding round for driverless cars; how municipal infrastructure will change to accommodate driverless cars; the challenges around robot-gripping (even in space); and whether we've reach the tipping point where AI is here to stay.

In this podcast Shane Hastie, InfoQ Lead Editor for Culture & Methods, spoke to Jason Hand of VictorOps about the DevOps culture, what ChatOps is and powerful post-mortems. Why listen to this podcast: - The misaligned incentives between development and operations in many organisations - The need to instil a sense of ownership across the whole delivery organisation where everyone takes responsibility for solving problems, rather than saying “that’s not my job” - There is no roadmap to change the culture of a company, because every company is different - In complex systems you can’t avoid failure, so make sure you can learn from it and respond rapidly More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2qKmrPe You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2qKmrPe

What is DevOps? How does it relate to Operations and Software Development? Bridget Kromhout, Principal Technologist for Cloud Foundry at Pivotal answers these questions. Bridget explained what Operations Engineering is and what she used to work on when she was focused in this area. We then talked about how DevOps emerged and how it differs from Operations. At the end we talked about VoiceOps and ChatOps and the future of DevOps.

DevOps, SecOps, DevSecOps, ChatOps, NoOps, the terms go on and on. In this episode of TNS Analysts Toph Whitmore, Principal Analyst at Blue Hill Research, talks about DataOps. He describes it as looking at the data production pipeline in a holistic manner, marrying data-management objectives with data-consumption ideals to maximize data-derived value. Learn more at: https://thenewstack.io/delving-dataops-matters/

Chat bots are your newest co-worker. Slack, HipChat, and other chat clients allow developers and other team members to communicate more dynamically than the limits of email. Companies have started to add bots to their chat rooms. These bots can give you technical information, restart a server, or notify you that a build has finished. The post ChatOps with Jason Hand appeared first on Software Engineering Daily.

Overview:   Jason Hand and I discuss the importance of moving away from a blame-oriented culture and towards a learning culture. Jason talks about the importance of understanding how cognitive biases influence decision-making and the need to understand this when conducting post mortems. Jason talks about balancing efficiency and thoroughness, and the importance of using blame-free post mortems as a means for learning. While Jason comes from a tech world, this talk has application to a variety of sectors, including high-risk industrial work. Jason Hand’s Biography: DevOps Evangelist at VictorOps, organizer of DevOpsDays - Rockies, author of the books O’Reilly’s “ChatOps: Managing Operations from Group Chat" as well as "ChatOps for Dummies”. Jason is a co-host of “Community Pulse” (a podcast on building community in tech), and organizer of a number of DevOps related events in the Denver/Boulder area. A frequent speaker at DevOps events around the country, Jason enjoys talking to audiences large and small on a variety of technical and non-technical subjects such as Modern Incident Management, Learning From Failure, Cognitive Bias, ChatOps, and building communities. Show Notes: Information Technology is no longer just a cost center and needs to be seen as a way for companies to innovate and become market leaders. Trying to innovate and experiencing failure can be an important way to learn. Post-Mortems are an important tool for learning and organizations should be transparent about learning and sharing that information about safety with others in the industry. Root cause analysis may uncover something that broke, and that can be fixed, but it may result in a lack of innovation in complex systems unless the organization tries to avoid a check the box mentality for a quick-fix and actually learn and improve the system. After negative events occur, when investigators use the word “why” that can sometimes imply “who” and it is important to avoid blame during post-mortem events, yet organizations often seek blame and accountability from a single individual. Accountability means to “give an account of what took place” or describe what too place. Accountability is not the same as responsibility. DevOps works to create high-functioning teams rather than silo’d teams. When silo’ing goes away organizations can become more innovative and other industries may learn a great deal from how DevOps is working to overcome silo’ing and a lack of cooperation towards system goals. Theory of Constraints may be used to help understand system goals and reduce silos in organizations. Sign up for our Newsletter here, or go to: www.v-speedsafety.com/email-subscription Resources: Books: The Phoenix Project by Gene Kim, George Spafford, and Kevin Behr, Thinking Fast and Slow by Daniel Kahneman, Black Box Thinking by Matthew Syed and The Cynefin Mini-Book-Info-Q by Greg Brougham Contact: Web: www.victorops.com www.jasonhand.com www.techbeacon.com Twitter: @jasonhand Keywords: Disruptive leadership podcast, safety podcast, leadership podcast, safety innovation podcast, high-reliability organizations podcast, human performance, human performance podcast, Crew Resource Management, Crew Resource Management Podcast, HRO podcast, DevOps, blame free post-mortems

How do you build a blameless post-mortem culture? And should you? Richard chats with Jason Hand from VictorOps about the blameless culture, which is a methodology embraced by the safest and most reliable organizations - think aircraft safety. Having everyone involved in an incident able to discuss everything they did and saw helps to get a clear picture of the truth. Without that information, it's very hard to make real improvements in our organizations. Jason talks about ChatOps as a strategy to get there, using tools like Slack to let people see the conversations going on and capture the critical information during an incident to address problems.

En este episodio debatimos sobre ChatOps.

Mark Imbriaco (Operable) returns to discuss the changing role of Operations, ChatOps, and more.   Show notes at devopscafe.org

In today's episode, I interview Sam Lambert, Director of Systems at GitHub. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

Peter Sankauskas Advanced AWS Meetup / SF Immutable Deployments with AWS CloudFormation by Fabrizio Branca Stackformation Stack Overflow 2016 Developer Survey ChatOps at Github Hubot CloudNative Yeobot kappa cruddy Botkit Dropbox leaving AWS The Epic Story of Dropbox's Exodus from the Amazon Cloud Empire Scaling to exabytes and beyond

Jason Hand (@jasonhand) DevOps Evangelist for VictorOps (@VictorOps) joins us this week on The Hot Aisle to talk about ChatOps and the benefit it has on a well oiled DevOps teams' overall function. Your hosts Brent Piatti (@BrentPiatti) and Brian Carpenter (@intheDC) get the details on how ChatOps became a thing, Who is using it, […]

Brian talks with Mark Imbriaco (@markimbriaco; Co-founder & CEO at @OperableInc) about the state of Cloud operations, the changes to DevOps, the human challenges of web scale operations and opinionated PaaS platforms. Check out O-Reilly's new initiative: Learning Paths. Show Links: Operable Homepage Topic 1 - The last time we spoke, you were part of the operations team at GitHub. Some things have changed since then. What’s new in your world? Topic 2 - What are the biggest changes that you’ve seen over the last 18 months that impact operations? How has DevOps continued to evolve? Topic 3 - Topic 3 - How much have things changed that require operations to deal with things in real-time? How much gets automatically remediated? Topic 4 - Topic 4 - What is most important to operations teams today? Topic 5 - Topic 5 - Lots of new frameworks and new ways to build applications. Any guidance that you have from an operations perspective to development teams?

Matt & Trevor sit down with Jason Hand (VictorOps), Sasha Rosenbaum (10th Magnitude), and Peter Burkholder (Chef) to discuss ChatOps.

Matt & Trevor sit down with Jason Hand (VictorOps), Sasha Rosenbaum (10th Magnitude), and Peter Burkholder (Chef) to discuss ChatOps.

About the Webinar DevOps is all about delivering business value as rapidly as possible. Embracing its philosophies goes beyond implementing automation and tooling to speed software development and delivery. DevOps is a culture of communication and collaboration. For many of us, shifting to this new culture can create organizational "culture shock," or discomfort by those suddenly subjected to an unfamiliar culture, way of life, or set of attitudes. DevOps is not something you purchase or have implemented by a DevOps Engineer. Instead, a shared vision and common goals across teams and team members are critical to making a successful culture transformation. Join us for a discussion about ways to shift organizational culture to achieve DevOps. We will highlight communication tools and movements, such as ChatOps. DevOps is all about teams working together to continually improve their processes and achieve their shared business goals. With cross-functional teams, documentation must be in place. We will discuss strategies for curating information repositories that fit how a team works. Also, project and team management are core components of ensuring that team members are able to work efficiently and don’t get lost in meetings and context switching. Automated tools further enhance communication by exposing project data to everyone.

This week, Dave and Gunnar talk about: computers that think, computers that think they’re thinking, and people that think computers are people. Gunnar is a Trello addict The Mother of all Web Tracking Catalogs. I think we’re done now. Housewarming gift via Heat template: Germans get free heating from the cloud BrowserStack gets utterly humiliated ChatOps is just thrilling User modeling with Watson That Time 2 Bots Were Talking, and Bank of America Butted In The ultimate weapon against GamerGate time-wasters: a 1960s chat bot that wastes their time Lauren and her juggling app mentioned on Gizmodo and Lifehacker UK GCN wins Gunnarbait of the week Preceded by this article on DHS and Coverity. Succeeded by Dave’s article 6 tips for adopting open source published on GCN RHEL Atomic beta now out! Dave keeps the SELinux on in the Docker docs OpenShift Enterprise 2.2 is out, with Fuse and A-MQ Messaging cartridges (xPaaS!) and CloudForms integration https://install.openshift.com/ is mind-blowing. Red Hat Enterprise Linux 6.5 to 6.6 risk report Google Cloud Platform says: “Red Hat has contributed tirelessly to almost every component of the stack and has been instrumental in shaping and improving the overall production readiness of Kubernetes.” Not my circus, not my monkey: Idioms of the World HT Bob St. Clair and related: Management Time: Who’s Got the Monkey?  Cutting Room Floor Cat Math What Happens When A Photographer Secretly Takes Over A Town’s Surveillance Camera Software-Defined Talk Podcast We Give Thanks Bob St. Clair for monkey management tips

ChatOps- Говорим О Возрождении Чатов by Konstantin Nazarov

Ryo Nakamuraさんをゲストに迎えて、JSON Schema, Rails, Postgres, RSpec, ChatOps, Markdown, 絵文字などについて話しました。 Show Notes Qiita クックパッドとマイクロサービス cookpad/garage JSON Schema and Hyper-Schema r7kamura/jdoc JSON SchemaとAPIテスト - YAPC::Asia 2014 Heroku | JSON Schema for the Heroku Platform API JSON Hyper-Schemaのようなサービスディスクリプションがうまくいかない理由 rails/jbuilder rails-api/active_model_serializers apotonick/roar Upgrading GitHub to Rails 3 with Zero Downtime Continuous Delivery at GitHub // Speaker Deck cookpad/chanko PostgreSQL: Documentation: 9.4: JSON Types miyagawa/mongery Query Documents - MongoDB Manual Query Mongo: MySQL to MongoDB Query Translator Rubyテスティングフレームワークの歴史 Transpec - The RSpec Syntax Converter Autodoc - r7km/s r7kamura/ruboty Ruby製HubotクローンのRubotyをSlackで動かす - Qiita jimmycuadra/lita The Twelve-Factor App Heroku | Introducing Heroku Button Hubot Scripting チャット経由でデプロイする - Qiita Markdownを拡張して独自記法をつくる - Qiita increments/qiita-markdown html-pipeline: Chainable Content Filters Open sourcing Twitter emoji for everyone | Twitter Blogs Six Apart絵文字 特集 : 絵文字が開いてしまった「パンドラの箱」 Unicode proposes a way to let an emoji black man and white woman hold hands Advent Calendar - Qiita

Johannes of Software Engineering Radio (http://www.se-radio.net) talks with Rachel Laycock and Max Lincoln from ThoughtWorks about continuous delivery on Windows. The outline includes: introduction to continuous delivery; continuous integration; DevOps and ChatOps; decisions to be taken when implementing continuous delivery on windows; build tools on windows; packaging and deploy on windows; infrastructure automation and infrastructure as code with chef, puppet or ansible; snowflake server versus phoenix server; Windows PowerShell; the relation between open source and Microsoft tools; why not to use Linux; current development in the windows DevOps space; licensing and proprietary software in continuous delivery. This discussion was recorded live at the ThoughtWorks North American Away Day, The Westin Peachtree, Atlanta, Georgia

Johannes talks with Rachel Laycock and Max Lincoln from ThoughtWorks about continuous delivery on Windows. The outline includes: introduction to continuous delivery; continuous integration; DevOps and ChatOps; decisions to be taken when implementing continuous delivery on windows; build tools on windows; packaging and deploy on windows; infrastructure automation and infrastructure as code with chef, puppet […]

伊藤直也さんをゲストに迎えて、GitHub, Pull Request, Hubot, リモートワークなどについて話しました。(6/1 GitHub Kaigiにて収録) Show Notes GitHub Kaigi GitHub Kaigiレポート GitHub 時代のデプロイ戦略 Git - git-request-pull Documentation WEB+DB PRESS Vol.81 pull requestを利用した開発ワークフロー Linus won't do GitHub Pull Requests Rebuild 45: Remembering WSDL A successful Git branching model ) developブランチなんてオワコン Hacker Way: Releasing and Optimizing Mobile Apps for the World CircleCI atmos/hubot-deploy ChatOps at GitHub miyagawa/hubot-cron crontab.org - CRONTAB(5) Hubotレビュアーおみくじ HuBoard ZenHub.io waffle.io Contributing to Atom LICEcap It's settled! Creator tells us how to pronounce 'GIF' Sqwiggle が良いという話、またはリモートでアジャイル開発をどう進めるか Sqwiggle QuicklyChat

本期由 Daniel 主持，参与嘉宾有 SaitoWu, Dingding Ye。武鑫(Saito) 是著名自托管 Git 项目仓库开源项目 GitLab 的核心开发者之一，也是 RubyConfChina 2012 的讲师，给大家做了期很精彩的 GitLab 实现介绍。本期我们很荣幸能请到 SaitoWu 同学来跟大家聊聊他的从业经历，他所感兴趣的话题，包括 Git，GitHub，以及 GitLab。 Why Git is better than X Git 为什么这么好? Unlocking the Secrets of Git Git scaling at GitHub Chatops at Github Sinatra How gitlab works SVN VPN git-svn 蓝光党 Ruby Tuesday http://clojure.org/ Haskell Rich Hickey 七周七语言 JDK8 Github Enterprise authorized_keys Gitosis Gitolite Twisted GitHub is Moving to Rackspace! Engine Yard And GitHub Transition Zach Holman Github Boxen libgit2 Hubot Play - Company's DJ Redcarpet Unicorn html-pipeline Resque Gitcafe Redmine Use pull request Scrum要素 Component Hexo Special Guest: saitowu.