#general - November 2025

Hi everyone! should we start a "Dev Talk" or a knowledge-sharing session within the team? We can share interests, trending, a failure or a cool concept.

Anyone here interested in having their infrastructure and SaaS dependencies mapped out in OSCAL? I've recently found myself working with multiple clients doing GRC automation work and I have a feeling there are definitely orgs here that have a sprawling mess of third party dependencies that would (or do) make their CISO have nightmares.

I've actually built my own special tooling stack for this, but if you want me to help you manage your third-party dependencies and map your infra, shoot me a DM and let's talk.

hey 👋
I’m Awantika, working with a team building self-improving AI agents.

Also co-hosting a solo builders community focused on startup marketing and revenue strategies.

really excited to be here to learn, share, and meet other folks building cool stuff
https://discord.gg/mAGZAQwSxR

What opinion do you have about having all public facing ingress components in a separate aws account?

Hello everyone,
I have a quick question. Our team is currently evaluating Terraform VS OpenTofu. At present, our entire infrastructure is managed using Terraform, but we are exploring whether OpenTofu may be a suitable option for the future.
In this context, I would like to understand Cloud Posse’s long-term roadmap. Specifically, will CloudPosse continue to support both Terraform and OpenTofu particularly with respect to module compatibility over the long term?
Thank you in advance for any insight you can provide.

is there an Q&A section?

Hey everyone
I was brown too.

Hello everyone — I am a 22-year Technical Operations executive who pivoted into AI in 2023. I have completely automated the SDLC chain; built and designed extensive NLQ AI AWS tooling, including a Well-Architected Framework vs. actual-analysis engine; designed cost-center analysis and cost-anomaly detection with RCA; full DevOps automation; IaC automation; and MCP design. I am an expert in Claude Code, Codex, OpenAI, Gemini, prompt engineering, and QE automation. Ping me if you want to talk AI DevOps automation.

AWS Well Architected Framework detailed analysis

# AI-Powered AWS Well-Architected Framework Scanner

## TL;DR
Built an open-source tool that combines *Claude AI with AWS infrastructure scanning to provide natural language cloud architecture reviews. Ask questions like "What security issues need immediate attention?"* instead of parsing through endless
CLI output.

---

## The Problem

Every cloud architect knows the drill:
- Run 50+ AWS CLI commands
- Parse JSON output manually
- Cross-reference against Well-Architected best practices
- Repeat for every region, every account

*It's tedious. It's error-prone. It doesn't scale.*

---

## The Solution: LLM-Powered Infrastructure Analysis

I built a scanner that evaluates your AWS environment against all *6 Well-Architected Framework pillars*:

| Pillar | AI-Enhanced Analysis |
|--------|----------------------|
| *Security* | Intelligent threat prioritization, attack surface analysis |
| *Reliability* | Failure mode detection, resilience scoring |
| *Performance* | Bottleneck identification, optimization recommendations |
| *Cost* | Waste detection, right-sizing suggestions |
| *Operational Excellence* | Automation gap analysis, runbook recommendations |
| *Sustainability* | Carbon footprint estimation, Graviton migration paths |

It beats reading the PDF

Yes — the AI compares your design creativity against the AWS Well-Architected Framework by scanning your entire buildout.