<p><strong>Why This Role Matters</strong><br>Open-source intelligence is now a primary feed for mission decisions, not a supplement. The volume of publicly available information has outrun the ability of analysts to exploit it by hand. Mission teams need AI systems that ingest, enrich, and reason over that data, and they need those systems to run where the mission runs.</p><p>That includes the hard places. Disconnected enclaves. Degraded networks. Air-gapped regions with no route to the public internet. The architecture that works in commercial AWS does not survive contact with a denied environment. Someone has to design the version that does.</p><p><a href="https://himalayas.app/companies/bluestaq">Bluestaq</a> builds on AWS across every classification level, from GovCloud to the Secret and Top Secret Regions. This role sets how we use that platform for AI-enabled OSINT. You decide how models, data, and pipelines run on AWS, connected or not. You own the structural decisions this capability is built on, from day one.</p><p><strong>The Role</strong><br>As the Principal Solution Architect for <a href="https://himalayas.app/companies/bluestaq">Bluestaq</a>'s OSINT mission capability, you design the AWS systems that turn open-source data into mission intelligence. You work at the intersection of AWS cloud architecture, applied AI, and intelligence tradecraft. You translate analyst requirements into AWS service selection, model design, data pipelines, and deployment patterns that hold up in defense environments.</p><p>This is an ownership role, not a coordination role. You are the technical authority for how these systems are built on AWS and where they run, and you are building that capability from the ground up. When the architecture holds under load and across classification levels, you are the reason. When it drifts, you are the first to flag it and the first to arrive with a plan.</p><h3>What You Will Own</h3><ul><li>Set the AWS reference architecture for AI and ML systems that ingest, enrich, and exploit open-source and publicly available information at scale.</li><li>Architect around the service gaps and parity differences between commercial AWS and the government and classified regions.</li><li>Build the AI stack on Amazon Bedrock and Amazon SageMaker, including model access, Bedrock Guardrails, Knowledge Bases, and managed endpoints.</li><li>Design retrieval pipelines using Amazon OpenSearch, S3 data lakes for governed, least-privilege access.</li><li>Orchestrate workflows with AWS Step Functions and AWS Lambda, and define CI/CD with infrastructure as code using AWS CDK and Terraform.</li><li>Extend services and capabilities to the edge for disconnected and DDIL operations and local model serving.</li><li>Define the deployment pattern for fully air-gapped enclaves, including mirrored registries, signed model imports, and local vector stores.</li><li>Define data movement patterns and cross-domain solutions across classification levels and coa