OSIRIS JSON

If you use AI, expensive consultancies or paid service to get your infrastructure visibility probably you don't know 𝗢𝗦𝗜𝗥𝗜𝗦 𝗝𝗦𝗢𝗡. The 𝗢𝗦𝗜𝗥𝗜𝗦 𝗽𝗿𝗼𝗱𝘂𝗰𝗲𝗿 𝗳𝗼𝗿 𝗔𝗺𝗮𝘇𝗼𝗻 𝗔𝗪𝗦 is now available as v0.1.0 It collects 𝘂𝗻𝗱𝗲𝗿 𝘆𝗼𝘂𝗿 𝗳𝘂𝗹𝗹 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 over 60 resource types across all major AWS service categories like networking, compute, data services, storage, security, and identity, emitting a single portable topology document per region. The challenge has never been a lack of AWS data. The modern challenge is that the architectural truth of an AWS environment is spread across accounts, regions, VPCs, subnets, security boundaries, managed services, and service-specific APIs that are difficult to retrieve and translate into an end-to-end report and topology view at a single point in time. The OSIRIS JSON producer for AWS turns that fragmented view into one portable topology document that can be validated, reviewed, diffed, and reused entirely outside your AWS infrastructure. A few highlights: • 60+ AWS resource types collected • 40+ explicit topology relationship types • Support for single-region, multi-region, CSV batch, and interactive CLI workflows • AWS IAM Identity Center SSO support through OIDC device flow • Documentation mode for clean topology output • Audit mode for deeper resource properties • Optional raw AWS SDK payloads for selected audit use cases • Read-only by design The OSIRIS JSON producer requires: • 𝗻𝗼 SaaS or consultancies • 𝗻𝗼 AI platforms or agents • 𝗻𝗼 MCP servers • 𝗻𝗼 intermediary third-party APIs You simply download it and execute it on-premises or locally under your full control using your personal or service account credentials, and it generates the precise OSIRIS JSON document of your AWS infrastructure. 𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗹𝗮𝘂𝗻𝗰𝗵 𝗽𝗼𝘀𝘁: https://lnkd.in/eK8ezAu7 #AWS #CloudArchitecture #OpenSource #DevOps #InfrastructureDocs #InfrastructureTopology #SolutionArchitecture #OSIRISJSON

Seeing 𝗢𝗦𝗜𝗥𝗜𝗦 𝗝𝗦𝗢𝗡 recognized in the 𝗝𝗦𝗢𝗡 𝗦𝗰𝗵𝗲𝗺𝗮 𝗟𝗮𝗻𝗱𝘀𝗰𝗮𝗽𝗲 is a truly meaningful moment for me. What began as a deeply personal effort to push beyond silos, tribal knowledge, and fragmented infrastructure visibility is now being acknowledged by a community I sincerely and deeply respect. 𝗢𝗦𝗜𝗥𝗜𝗦 𝗝𝗦𝗢𝗡 was born from a simple belief: the understanding of infrastructure should not depend on who holds the knowledge, which vendor is involved, or which team owns a specific domain. It is a perseverance commitment to transparency, high quality documentation and the firmly belief that even the most complex systems can be understood if we wear the right glasses through a shared, open, vendor-neutral language that helps people see the bigger picture with clarity. I’m genuinely grateful to the 𝗝𝗦𝗢𝗡 𝗦𝗰𝗵𝗲𝗺𝗮 community for this recognition. Without open standards and the people who support them, ideas like this would remain only drafts in someone’s head. With the right community, they can become something real, useful, shared and possibly make an impact. This is only a beginning, but it is an exciting one. Thank you to everyone who has supported, encouraged, challenged, and believed in this journey. #OSIRISJSON #JSONSchema #OpenStandards #Infrastructure #Topology #Automation #IT #OT #DocsAsCode

OSIRIS JSON a new journey beyond silos and tribal knowledge Beyond the silos: The soul behind OSIRIS JSON For twenty years, my mission has been to bridge the gap between siloed tribal knowledge and operational clarity. I’ve evolved from the manual era of painstakingly mapping fragmented topologies to building a solution that delivers a comprehensive, end-to-end snapshot of the infrastructure landscape. My goal building OSIRIS JSON is simple: to provide the big-picture visibility that empowers IT and OT professionals to make the right decisions with confidence. In the world of infrastructure, we often settle for fragments. We see a server here, a cloud instance there, a facility sensor somewhere else. But my goal, no matter with who and for who I have been working for, has always been to achieve an end-to-end view of the entire infrastructure, seeing how every piece breathes together in one interconnected map, this for a very simple reason to achieve multiple goals: 1. eradicate silos, feudal thinking and critical context living in people heads embracing open standard Documentation as Code (Docs as Code) culture 2. providing an easy way for architects and IT/OT professionals to understand end-to-end the infrastructure in a fast up-to-date state in time 3. allowing fast troubleshooting maintaining a clear up-to-date infrastructure documentation and topology 4. allowing fast snapshot in time end-to-end of the infrastructure without complications or third-party scanning softwares making OSIRIS JSON a great allies under audit sessions provide an accurate standardized baseline for LLMs allowing to understand the infrastructure landscape providing enhanced reasoning and automation. Continue reading on: https://lnkd.in/d9KFvFcU

What an OSIRIS JSON producer is expected to do OSIRIS JSON producers are where the standard becomes real. The producer guidelines and producer SDK documentation make that explicit. A producer is not just a parser that happens to emit JSON. It is the boundary where proprietary inventories are translated into a deterministic, portable, and safe OSIRIS snapshot that other tools can trust. https://lnkd.in/dcJxF9Bz

Validate OSIRIS JSON documents OSIRIS JSON validation is no longer just an implied part of the specification. It now has a documented model, a canonical engine boundary, and a CLI contract designed for real tooling. The current validation guidance is spread across three draft documents published in February 2026: the Validation Levels Guidelines, the Toolbox Core internals guide, and the Toolbox CLI guide. Together, they define how OSIRIS documents should be validated consistently across local development, editor integrations, and CI pipelines. https://lnkd.in/dveCHJXT

OSIRIS JSON is live 🚀 Open Specification for Infrastructure Resource Interchange Schema, defines a vendor-neutral JSON format for describing infrastructure resources, properties, metadata and topology relationships across heterogeneous IT, OT, cloud and on-premises environments. OSIRIS JSON is a neutral interchange specification. It is designed to normalize infrastructure data exported from diverse domains and enable portable consumption by tools without requiring every consumer to develop and maintain vendor-specific parsers. Get started on: https://osirisjson.org/ #opensource #infrastructure #topology #documentation