<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on pyToshka's DevSecOps Blog</title><link>https://blog.pytoshka.me/en/tags/aws/</link><description>Recent content in Aws on pyToshka's DevSecOps Blog</description><generator>Hugo</generator><language>en-US</language><managingEditor>ping@pytoshka.me (pyToshka)</managingEditor><webMaster>ping@pytoshka.me (pyToshka)</webMaster><lastBuildDate>Sun, 26 Apr 2026 00:09:11 +0400</lastBuildDate><atom:link href="https://blog.pytoshka.me/en/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Wazuh MCP Server: Claude Desktop + OpenSearch (Part 2)</title><link>https://blog.pytoshka.me/en/post/wazuh-aws-bedrock-mcp-part-2/</link><pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/wazuh-aws-bedrock-mcp-part-2/</guid><description>&lt;h2 id="introduction"&gt;
 Introduction
 &lt;a class="header-anchor" href="#introduction" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;In &lt;a href="https://blog.pytoshka.me/en/post/wazuh-aws-bedrock-mcp-part-1/"&gt;Part 1&lt;/a&gt; we connected AWS Bedrock Claude to the Wazuh Dashboard chat via ML Commons. That approach works well for analysts working inside the Wazuh UI. In this part we open a second channel: &lt;strong&gt;Model Context Protocol (MCP)&lt;/strong&gt;, which allows any compatible client - Claude Desktop, custom applications, CI pipelines - to query Wazuh Indexer data through a standardized tool interface.&lt;/p&gt;</description></item><item><title>Wazuh + AWS Bedrock: AI Security in Docker (Part 1)</title><link>https://blog.pytoshka.me/en/post/wazuh-aws-bedrock-mcp-part-1/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/wazuh-aws-bedrock-mcp-part-1/</guid><description>&lt;h2 id="introduction"&gt;
 Introduction
 &lt;a class="header-anchor" href="#introduction" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;In the &lt;a href="https://blog.pytoshka.me/en/post/local-ollama-in-the-wazuh-dashboard-for-llm-powered-insights/"&gt;previous article&lt;/a&gt; we embedded a local Ollama model directly into the Wazuh Dashboard chat via ML Commons. That approach provides full control over data with no cloud dependencies. In this series we take a parallel path: using &lt;strong&gt;AWS Bedrock&lt;/strong&gt; - specifically &lt;strong&gt;Claude Sonnet 4.5&lt;/strong&gt; - as the inference backend, while all security data stays strictly within the local Docker network.&lt;/p&gt;</description></item><item><title>From Wazuh Ambassador to AWS Community Builder</title><link>https://blog.pytoshka.me/en/post/aws-community-builder/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/aws-community-builder/</guid><description>&lt;img src="https://d1.awsstatic.com/developer-center/community/community-builders/AWS-Community-Builders-Logo.389c323f26b3e5f97ba985e08e989f88c7d73e29.png" alt="AWS Community Builders"&gt;&lt;h2 id="introduction"&gt;
 Introduction
 &lt;a class="header-anchor" href="#introduction" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;I&amp;rsquo;m excited to share that I&amp;rsquo;ve been accepted into the &lt;strong&gt;AWS Community Builders&lt;/strong&gt; program for the 2026 cohort in the &lt;strong&gt;Security&lt;/strong&gt; category. For me, this is a natural next step after becoming a &lt;a href="https://blog.pytoshka.me/en/post/wazuh-ambassador-announcement/"&gt;Wazuh Ambassador&lt;/a&gt; - another milestone in a journey that has always been centered around open-source security and cloud infrastructure.&lt;/p&gt;</description></item><item><title>Two LLM Security Assistants for Wazuh and AWS Analysis</title><link>https://blog.pytoshka.me/en/post/security-ai-models/</link><pubDate>Tue, 07 Oct 2025 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/security-ai-models/</guid><description>&lt;h2 id="when-your-soc-analyst-cant-keep-up-or-just-needs-a-break"&gt;
 When Your SOC Analyst Can&amp;rsquo;t Keep Up (Or Just Needs a Break)
 &lt;a class="header-anchor" href="#when-your-soc-analyst-cant-keep-up-or-just-needs-a-break" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;Let&amp;rsquo;s be honest: analyzing thousands of security events every day isn&amp;rsquo;t the most exciting job.&lt;/p&gt;</description></item><item><title>Amazon EKS SOC 2 Type II Compliance Checklist part 1</title><link>https://blog.pytoshka.me/en/post/amazon-eks-soc2-type-ii-compliance-checklist-part-1/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/amazon-eks-soc2-type-ii-compliance-checklist-part-1/</guid><description>&lt;h2 id="introduction"&gt;
 Introduction
 &lt;a class="header-anchor" href="#introduction" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;Navigating the world of compliance can feel like trying to read a map in a language you don&amp;rsquo;t speak. When you throw Kubernetes into the mix, it gets even trickier. That&amp;rsquo;s why we&amp;rsquo;ve put together this straightforward, human-friendly checklist to help you get your Amazon EKS clusters ready for a SOC 2 Type II audit.&lt;/p&gt;</description></item><item><title>Amazon EKS SOC 2 Type II Compliance Checklist part 2</title><link>https://blog.pytoshka.me/en/post/amazon-eks-soc2-type-ii-compliance-checklist-part-2/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/post/amazon-eks-soc2-type-ii-compliance-checklist-part-2/</guid><description>&lt;p&gt;Moving on, let&amp;rsquo;s look at the other controls for EKS SOC Type 2.&lt;/p&gt;
&lt;p&gt;For container security best practices, see our guide on &lt;a href="https://blog.pytoshka.me/en/post/container-image-security-with-wazuh-and-trivy/"&gt;Container Image Security with Wazuh and Trivy&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="cc3-risk-assessment"&gt;
 CC3: Risk Assessment
 &lt;a class="header-anchor" href="#cc3-risk-assessment" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;hr&gt;
&lt;h3 id="eks-specific-risk-assessment"&gt;
 EKS-Specific Risk Assessment
 &lt;a class="header-anchor" href="#eks-specific-risk-assessment" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h3&gt;&lt;p&gt;Identify, evaluate, and document security, operational, and compliance risks specific to Amazon EKS clusters and workloads to ensure that appropriate controls are implemented, monitored, and improved in alignment with SOC 2 Trust Services Criteria.&lt;/p&gt;</description></item><item><title>Meet me</title><link>https://blog.pytoshka.me/en/page/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>ping@pytoshka.me (pyToshka)</author><guid>https://blog.pytoshka.me/en/page/about/</guid><description>&lt;h2 id="professional-summary"&gt;
 &lt;strong&gt;Professional Summary&lt;/strong&gt;
 &lt;a class="header-anchor" href="#professional-summary" aria-label="Permalink to this section"&gt;
 &lt;svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg"&gt;
 &lt;path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.65 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" fill="currentColor"/&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;Senior Site Reliability Engineer with 14+ years building, scaling, and maintaining critical infrastructure across diverse technology environments.&lt;/p&gt;</description></item></channel></rss>