Role: AWS FinOps Architect with FinOps Certifications
Location: Atlanta, GA
Reviews of Reservations (supplemented by IT Operations data)
Adjustments to Baselines & Savings Plans
Product and Service switches to optimize sourcing and Savings/Discount plans
- Work with IT Operation and Cloud Operations teams to identify the type activities/interventions that could address actions identified by above controls
- Work with stakeholders (engineering, application, business, audit, sourcing, budgeting & forecasting, and operations teams) to establish appropriate OCM (Operational Change Management) avenues to promote FinOps culture in their planning and actions
- Governance and Review forums
- Architecture and Roadmaps (incl. Patterns/Template/Blueprints)
- Automations and Standard Operating Processes
- Establish and evolve Tagging Standards to ensure appropriate tracking and usage/spend baselines can be established to support / differentiate
- existing Public Cloud workloads
- future migrated Public Cloud workloads
- changes to existing public cloud workloads due to new releases, approved changes, and organic growth
- Establish (with client FinOps team) detailed data streams for near real-time (and real time) costs and consumption for engineering, application, and business teams.
- spend and usage/allocations (from billing data)
- breakdown by accounts, by applications, by line of business (business functions) discounts and credits cross leverage Observability/Instrumentation (e.g., OTel) to enhance information that could be provided that influence spending/consumption patterns
Create Dashboards and Visualizations to support contextual Reporting for:
o Governance
Cost Management (Including Baseline Cost Tracking)
o IT Operations
o Program Management
• Establish and evolve relevant controls to be integrated into provisioning and operational processes
- Detective controls - identify and report errors and irregularities – e.g., Incomplete tagging, unallocated assets, underutilized assets, deviations from WAF/Roadmap standards
- Corrective controls - correct errors or irregularities that have been detected – e.g., correct tagging
- Preventive controls - taken before a threat to reduce the chance of it happening and the impact it has – e.g., ensure provisioning can’t proceed without complete data/parameters
- Deterrent controls – Method or control to discourage a potential bad actor – e.g., highlight and dissuade configuration/provisioning outside defined pipelines or change activities