Security Identity Engineer

Summary

AWS partners with the client's Site Reliability Engineering (SRE) team to build out Project Omni - AWS's next-generation observability capability - within the client's environment. The two Forward Deployed Engineers build Omni end-to-end: integrating the API layer with AWS IAM Identity Center (IdC), enforcing data boundaries across SRE, Application teams, and Business Units, automating cross-account data routing, and deploying the underlying infrastructure as code across the client's AWS estate. This role sits embedded within the client's observability/SRE team, working on behalf of SRE to enable Omni.

The client is a long-standing AWS identity-federation customer with an established credential-vending model and existing IdC adoption for console access, so a central part of the identity work is integrating Omni into that existing federation and entitlements landscape rather than building it from a blank slate. Success is defined by deep AWS identity/access-management expertise combined with the ability to deliver features end-to-end across the AWS infrastructure, API, and infrastructure-as-code layers at enterprise scale.

Note: Project Omni is an unreleased AWS service currently in Private Beta; work is carried out in non-production environments.

Role Scope

• Identity & Entitlements: Integrate the API layer with AWS IAM Identity Center (IdC) and build a policy engine to enforce data boundaries (SRE vs. App Team vs. Business Unit). This includes integrating Omni into the client's existing identity-federation model - an established custom credential-vending / SAML broker on the primary landing zone plus existing IdC adoption for console access.
• Cross-Account Data Routing: Implement and automate links to aggregate logs, metrics, and traces across multiple AWS Organizations.
• End-to-End Feature Delivery: Build, test, and deploy features from the AWS infrastructure layer (CloudWatch / Omni / IAM) up through the API layer that serves the UI, using CloudWatch cross-account capabilities. May include writing high-performance APIs (in Go, Python, or Java) to query CloudWatch, CloudTrail, and flow logs, and implementing efficient caching strategies.
• Infrastructure as Code (IaC): Automate the deployment of all resources using Terraform or AWS CDK, leveraging AWS CloudFormation StackSets to deploy source links to 15,000 accounts.
• Enablement: Produce clear architecture and integration documentation and enable the client's teams to operate and extend the Omni identity and routing model, working as an embedded SME alongside the client's SRE and observability leadership.

Core Skills

Identity and access management is the primary skill for this role, paired with the ability to deliver features end-to-end from infrastructure through the API layer.

Required Depth & Technologies

Advanced. AWS IAM Identity Center (IdC), SAML/OIDC federation, and integration with an existing enterprise federation / credential-vending model. Attribute-based access control (ABAC) and fine-grained authorization engines such as AWS Verified Permissions or Open Policy Agent (OPA).

Advanced. AWS Organizations, CloudFormation StackSets, and Org-level APIs and policies. Able to automate resource provisioning at a scale of 15,000 accounts.

Proficient. Python, Java, or Go. Building high-performance REST/API services to query CloudWatch, CloudTrail, and flow logs, with efficient caching strategies and asynchronous data fetching.

Advanced. CloudWatch (Metrics, Logs, Alarms, Contributor Insights), CloudWatch cross-account observability / OAM (sink and source configuration), CloudTrail, and flow logs.

Advanced. Terraform or AWS CDK, with CI/CD pipelines (e.g. GitLab CI) for automated infrastructure deployment.

General Requirements

• AWS Professional or Specialty certification preferred (e.g. Security Specialty, Solutions Architect Professional, or DevOps Engineer Professional, as relevant to the role).
• Prior delivery experience in a large, regulated enterprise environment (financial services strongly preferred); comfortable operating under change-control and audit scrutiny.
• Able to produce clear written documentation (architecture decision records, runbooks, design docs) suitable for client Tech Risk review.
• Strong stakeholder communication; can work directly with client engineering, security, and SRE teams as an embedded SME.
• Works to the stated engagement location / time-zone overlap and follows AWS ProServe and client onboarding, security, and vetting requirements (CV submission, AWS + client interview, tollgate onboarding).