Add FivexL Newsletter February 2026 and update .gitignore

.gitignore

@@ -7,4 +7,7 @@ scratchpad.md
 node_modules
 
 # Local Netlify folder
-.netlify
+.netlify
+
+# macOS
+.DS_Store

AGENTS.md

@@ -0,0 +1,7 @@
+# Newsletter Blog Posts
+
+When creating or editing a newsletter blog post (`content/blog/*newsletter*/index.md`), always follow the template at `templates/NEWSLETTER.md`.
+
+- Read `templates/NEWSLETTER.md` before generating or reviewing any newsletter content.
+- Use the section order, formatting rules, tone guidelines, and checklist defined there.
+- Do not deviate from the template structure unless explicitly asked.

content/blog/fivexl-newsletter-february-2026/index.md

@@ -0,0 +1,80 @@
+---
+title: 'FivexL Newsletter, February 2026'
+author_id: FivexL
+date: 2026-03-06
+description: 'FivexL Newsletter for February 2026 - Latest updates, blog posts, and insights from our cloud engineering team.'
+author: FivexL
+author_link: https://fivexl.io/
+category: Newsletter
+panel_image: fivexl-newsletter-white-logo.png
+tags: ['Newsletter', 'AWS', 'Cloud Engineering']
+---
+
+Greetings!
+
+FivexL kept its usual pace in February: two new case studies for our happy customers, AWS re:Invent 2025 recap webinar, a round of open-source releases, and two podcast episodes covering security patches and agent-native infrastructure. Here's the rundown.
+
+<!--more-->
+
+## Events
+
+If you care about building an organisation where security is a habit, not a hero moment, this webinar is for you.
+
+We're hosting a webinar with Rusty Atkinson, Senior Vice President, Technology at Clearway Health and author of "The Integrity Edge: Unlocking the Hidden Power of Ethical Leadership", on how to translate leadership values into real security decisions and build audit-ready architecture.
+
+Topic: "From Leadership Values to Security: How to Build Audit-Ready Architecture" <br />
+Date: Wednesday, 18 March 2026 <br />
+Time: 10:00 AM EDT / 3 PM CET <br />
+Duration: 1 hour <br />
+
+Join live and stay for the Q&A, where you can ask Rusty and our FivexL principal consultants questions directly.
+
+[Sign up for the webinar](https://lnkd.in/eT7k9pPh)
+
+Want to get a feeling of our webinars? Last month [Andrey Devyatkin](https://fivexl.io/specialist/andrey-devyatkin/), [Guilherme Ferreira](https://fivexl.io/specialist/guilherme-ferreira/), and [Vladimir Samoylov](https://fivexl.io/specialist/vladimir-samoylov/) went through the 500+ announcements from AWS re:Invent 2025 and picked the ones that actually matter for day-to-day work. The conversation covered what's worth adopting now, what to keep an eye on, and what's safe to ignore. If you missed the live session, the [recording is on YouTube](https://www.youtube.com/watch?v=-POnrk4phR0).
+
+## Updates
+
+### Open-source project updates
+
+We keep a lot of the tooling we build for client work open source so you can plug it into your own environments. In February we shipped updates to our CloudTrail-to-Slack Terraform module and to lprobe, our secure local-only health check tool.
+
+- **[terraform-aws-cloudtrail-to-slack 4.5.0](https://github.com/fivexl/terraform-aws-cloudtrail-to-slack/releases/tag/4.5.0)**  
+  Terraform module that parses AWS CloudTrail events and sends selected ones to Slack. This release adds SNS fan-out support for CloudTrail S3 notifications, so multiple consumers can process the same CloudTrail events while keeping S3 batching intact. New inputs include `enable_s3_sns_fanout`, `create_s3_sns_fanout_topic`, and `s3_sns_fanout_topic_arn`. Existing setups using direct S3-to-Lambda delivery require no changes.
+
+- **[lprobe v0.1.8](https://github.com/fivexl/lprobe/releases/tag/v0.1.8)**  
+  LProbe is a small CLI for running HTTP/TCP health checks against localhost inside container images (ECS, Docker) - a safer alternative to shipping curl or wget in every image. This release bumps CI tooling and Go to 1.26, keeping the tool aligned with current runtimes.
+
+### Blog post and case study updates
+
+- **[Sirob Technologies Case Study](https://fivexl.io/case-studies/sirob-case-study/)**  
+  Sirob Technologies had a working AI product powered by Amazon Bedrock but no production infrastructure to run it on for real customers. FivexL built a secure, multi-tenant AWS platform - Landing Zone, zero-standing-access, security monitoring, and a productized Bedrock deployment on ECS - in under two months. If you're building an AI-native product and wondering how to get from prototype to production without a year-long infrastructure project, this one's for you.
+
+- **[Neverless Case Study](https://fivexl.io/case-studies/neverless-case-study/)**  
+  Neverless, a London fintech, needed to expand into AWS while keeping their existing Google Cloud environment running. FivexL delivered a secure, audit-ready AWS foundation via RightStart so the team could start building on AWS immediately without rethinking the basics. Worth reading if you're running multi-cloud or planning a migration and want to see how to set up the AWS side without slowing down your product work.
+
+- **[AWS News You Can Actually Use In 2026](https://fivexl.io/blog/aws-news-you-can-use-2026/)**  
+  AWS made 500+ announcements at re:Invent 2025. We went through all of them and pulled out the features that are actually worth adopting this year - things like ECS tmpfs support, Transfer Family web apps, and multi-region IAM Identity Center. If you don't have time to read every changelog but want to know what's changed, start here.
+
+- **[FivexL Newsletter, January 2026](https://fivexl.io/blog/fivexl-newsletter-january-2026/)**  
+  Missed last month? Catch up on the January edition - open-source releases, a practical guide to getting AWS credits, and two podcast episodes on AI in dev workflows and Kubernetes vs managed services.
+
+### Podcast: DevSecOps Talks
+Our co-founder [Andrey Devyatkin](https://fivexl.io/specialist/andrey-devyatkin/) hosts the DevSecOps Talks podcast together with Paulina Dubas and Mattias Hemmingsson. Paulina is an independent Lead DevOps Engineer/Architect who spent the last decade building and shaping cloud platforms. Mattias is a former CISO at a car rental company, a certified pentester, and a cloud engineering enthusiast. Together they use the show to sanity-check new trends, share what actually works in the field, and translate "DevSecOps" from buzzword back into day-to-day practice.
+
+In February, they released two new episodes: one on the January security landscape, and another featuring a guest deep-dive into agent-native infrastructure.
+
+#### Episode #91 – January Security Roundup: CVSS 10 in n8n, Self-Hosted AI Scares, and Nonstop Patching
+
+This episode kicks off with a CVSS 10 vulnerability in n8n, then looks at self-hosted AI assistants with weak defaults and prompt injection risks. The crew talks through what happens when a self-hosted bot has access to your API keys, inbox, and drives - and what your team should rotate, patch, and lock down before it becomes a problem.
+
+[Listen the full episode](https://devsecops.fm/episodes/091-january-security-roundup-cvss-10-in-n8n-self-hosted-ai-scares-and-nonstop-patching/)
+
+#### Episode #92 – From System Initiative to SWAMP: Agent-Native Infra with Paul Stack
+
+What can you automate with SWAMP today, from AWS to a Proxmox home lab? In this episode, the team talks with Paul Stack about how skills, scripts, and reusable workflows plug into your stack - and whether this could be the missing guardrails for your infrastructure agents.
+
+[Listen the full episode](https://devsecops.fm/episodes/092-from-system-initiative-to-swamp-agent-native-infra-with-paul-stack/)
+
+
+Made it till the end? Liked this newsletter? Forward it to a teammate or friend who lives in AWS as much as you do! Sharing is caring!

templates/NEWSLETTER.md

@@ -0,0 +1,163 @@
+# FivexL Monthly Newsletter — Template & Guidelines
+
+Use this document when generating or reviewing a monthly newsletter blog post.
+The newsletter lives at `content/blog/fivexl-newsletter-{month}-{year}/index.md`.
+
+---
+
+## Front Matter
+
+```yaml
+---
+title: 'FivexL Newsletter, {Month} {Year}'
+author_id: FivexL
+date: {YYYY-MM-DD}          # publication date — usually within the first two weeks of the following month
+description: 'FivexL Newsletter for {Month} {Year} - Latest updates, blog posts, and insights from our cloud engineering team.'
+author: FivexL
+author_link: https://fivexl.io/
+category: Newsletter
+panel_image: fivexl-newsletter-white-logo.png   # alternate with fivexl-newsletter-black-logo.png each month
+tags: ['Newsletter', 'AWS', 'Cloud Engineering']
+---
+```
+
+### Front-matter rules
+
+- `title` always follows the pattern `FivexL Newsletter, {Month} {Year}`.
+- `date` is the actual publication date, not the last day of the covered month.
+- `panel_image` alternates between the white-logo and black-logo variants.
+- `tags` stays fixed unless a genuinely new top-level theme is added.
+
+---
+
+## Section Order
+
+Include sections in this order. Sections marked *optional* are only added when there is content for them.
+
+1. `## Intro`
+2. `## Events`
+3. `## Updates`
+   1. `### Open-source project updates`
+   2. `### Blog post and case study updates`
+   3. `### Podcast: DevSecOps Talks`
+   4. `### Top {N} articles from the team` *(optional)*
+4. **Closing line** (no heading)
+
+Never reorder or nest these differently. If a section has no content for the month, omit it entirely — do not leave empty headings.
+
+---
+
+## Section Details
+
+### 1. Intro
+
+- Use `## Intro` as the heading.
+- **Always open with "Greetings!"** on its own line right after the heading, followed by a blank line before the body text.
+- 1–3 short paragraphs after the greeting.
+- Make the opening energetic and engaging — the reader should feel like there's something worth scrolling for. Tease the most interesting highlights up front so curiosity pulls them in.
+- Summarise the month's highlights at a glance: what shipped, what's new, what changed.
+- Do **not** open with "it was a busy month" or similar — we've overused that framing. Instead, lead with what FivexL shipped or what changed, and let the volume speak for itself.
+- Seasonal or timely context (holidays, re:Invent, end-of-year) is fine when it adds something, but keep it brief.
+
+### 2. Events
+
+- Use `## Events` as the heading.
+- This section covers both upcoming and past events/webinars. Include whichever apply for the month — one or both.
+- **Upcoming events:** Tease the next webinar or event. Name the presenters and link to their specialist pages (`https://fivexl.io/specialist/{slug}/`). Encourage joining live for Q&A — "that's the part you can't get from a recording." Link to the registration page or, if not yet available, to the FivexL LinkedIn page (`https://www.linkedin.com/company/5xl`) with "Stay tuned for the full announcement."
+- **Past webinars:** Name presenters with links to their specialist pages. Briefly describe what was covered. Link to the recording (usually YouTube).
+
+### 3. FivexL Updates
+
+This is the main container heading. All subsections below live under it.
+
+#### 3a. Open-source project updates
+
+- Open with a short intro sentence about FivexL keeping client tooling open source (vary the wording slightly each month to avoid sounding robotic, but keep the idea).
+- List each release as a bullet:
+
+  ```markdown
+  - **[project-name vX.Y.Z](https://github.com/fivexl/{repo}/releases/tag/vX.Y.Z)**  
+    One-sentence description of what the project is. What changed in this release. Why / when it matters.
+  ```
+
+- Mention concrete inputs, flags, or behaviour changes — readers should understand the diff without clicking through.
+- If no changes require action from existing users, say so explicitly ("Existing setups require no changes.").
+
+#### 3b. Blog post and case study updates
+
+- Use heading `### Blog post updates` (when there are no case studies) or `### Blog post and case study updates` (when there are).
+- Bullet list — blog posts and case studies together in one section, case studies first when present.
+- For **case studies**, use this format:
+
+  ```markdown
+  - **[Customer Name Case Study](https://fivexl.io/case-studies/{slug}/)**  
+    Customer's challenge → what FivexL delivered → who should read it.
+  ```
+
+  End each case study description with a line aimed at the reader: "If you're doing X, this one's for you" / "Worth reading if you're planning Y."
+
+- For **blog posts**, same bullet format:
+
+  ```markdown
+  - **[Blog Post Title](https://fivexl.io/blog/{slug}/)**  
+    2–4 sentences — what the post covers and who benefits.
+  ```
+
+- **Always include a link to the previous month's newsletter as the last item**, with a short "Missed last month? Catch up on…" nudge.
+
+#### 3c. Podcast: DevSecOps Talks
+
+- Start with the **standard boilerplate paragraph** (copy from the block below and keep it verbatim):
+
+  > Our co-founder [Andrey Devyatkin](https://fivexl.io/specialist/andrey-devyatkin/) hosts the DevSecOps Talks podcast together with Paulina Dubas and Mattias Hemmingsson. Paulina is an independent Lead DevOps Engineer/Architect who spent the last decade building and shaping cloud platforms. Mattias is a former CISO at a car rental company, a certified pentester, and a cloud engineering enthusiast. Together they use the show to sanity-check new trends, share what actually works in the field, and translate "DevSecOps" from buzzword back into day-to-day practice.
+
+- Follow with a transition sentence: "In {Month}, they released {N} new episode(s): {brief one-liner per episode}."
+- Then one sub-section per episode:
+
+  ```markdown
+  #### Episode #{number} – {Title}
+
+  2–3 sentence summary of the conversation: topic, key takeaways, what the listener will walk away with.
+
+  [Listen the full episode]({url})
+  ```
+
+#### 3d. Top articles from the team *(optional)*
+
+- Heading: `### Top {N} articles from the team` (N is typically 3 or 10).
+- Optional one-line intro explaining the curation (e.g. "From everything our team shared internally this month…").
+- Numbered list; each item is a link followed by an optional 1–2 sentence annotation or "Use case:" blurb.
+
+### 4. Closing Line
+
+Use one of these two variants (alternate or pick whichever fits):
+
+- `Made it till the end? Liked this newsletter? Forward it to a teammate or friend who lives in AWS as much as you do! Sharing is caring!`
+- `Liked this newsletter? Forward it to a teammate or friend who lives in AWS as much as you do.`
+
+---
+
+## Tone & Style
+
+- **Conversational but professional.** Write the way you'd talk to a peer engineer over coffee — direct, specific, no filler.
+- **No emojis** in the newsletter body.
+- **Practical framing.** Describe things in terms of what a reader can *do* with them: adopt, test, watch out for, skip.
+- Prefer "you" over "users" or "engineers."
+- Avoid marketing superlatives ("groundbreaking", "game-changing"). Say what changed and why it matters.
+- Keep paragraphs short — 2–4 sentences max.
+- Use bold for project/release names inside bullet lists. Use `code formatting` for variable names, flags, and CLI commands.
+- Link team members to their specialist pages on fivexl.io, not to LinkedIn or GitHub profiles.
+
+---
+
+## Checklist Before Publishing
+
+- [ ] Front matter fields are complete and `date` reflects the actual publish date.
+- [ ] `panel_image` alternates from the previous newsletter.
+- [ ] Intro paragraph does not use "busy month" or equivalent.
+- [ ] Every release, blog post, case study, and episode has a working link.
+- [ ] Podcast boilerplate paragraph is present and unchanged.
+- [ ] Previous month's newsletter is linked under "Blog post updates."
+- [ ] Closing line is present.
+- [ ] No empty sections or headings without content.
+- [ ] Spell-check and link-check pass.