Who is Fernando F. Azevedo?

Fernando F. Azevedo is a Senior Solutions Architect at Banco Itaú with 16+ years of experience across AWS, event-driven architecture, DevSecOps, Data Mesh, AI and financial systems.

What technical topics does Fernando work with?

Fernando works with AWS, Kubernetes, Kafka, Data Mesh, Amazon Bedrock, RAG, DevSecOps, observability, financial systems and architecture communication using C4, ADRs and trade-off analysis.

Is Fernando available for professional conversations?

Fernando is currently building at Banco Itaú and is open to thoughtful conversations about architecture, cloud, AI, engineering leadership, community, podcasts and technical collaboration.

What is the AWS Well-Architected self-check?

A free, interactive self-assessment across the six AWS Well-Architected pillars — Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization and Sustainability — that returns a scorecard and prioritized next steps. It runs entirely in your browser and is not an official AWS review.

What are the six pillars of the AWS Well-Architected Framework?

Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization and Sustainability.

Interactive tool · Ferramenta interativa

AWS Well-Architected self-check

Answer a short set of senior-level questions across the six pillars and get an instant scorecard with prioritized next steps. Runs in your browser — nothing is stored or sent.

0/24 answered

Operational Excellence

Is all infrastructure defined as code (Terraform/CloudFormation/CDK) across environments?

Do you have centralized logs, metrics and traces with actionable alarms?

Are routine operations and incident response automated or runbook-driven?

Do deployments run through CI/CD with automated tests and safe rollback?

Security

Is access least-privilege, with no long-lived keys and MFA on human access?

Is data encrypted at rest and in transit everywhere, with managed keys (KMS)?

Is the network segmented with edge protection (WAF) for public surfaces?

Do you have centralized audit (CloudTrail), guardrails (Config/SCPs) and threat detection (GuardDuty)?

Reliability

Are critical workloads Multi-AZ (and Multi-Region where the impact justifies it)?

Are backups automated with tested restores and defined RTO/RPO?

Do you use health checks, auto-scaling and graceful degradation under load?

Do you validate resilience with failure testing or game days?

Performance Efficiency

Is compute matched to the workload (serverless/managed where it fits)?

Do you cache hot paths (CDN/edge and application caching)?

Are spiky or slow operations decoupled (async/event-driven)?

Do you monitor performance continuously against defined SLOs?

Cost Optimization

Do you have cost visibility per team/workload (tags, budgets, alerts)?

Do you use right-sizing plus Savings Plans/Spot where appropriate?

Are idle resources and old data cleaned up via lifecycle policies?

Is cost a first-class input in architecture decisions (FinOps)?

Sustainability

Do you maximize utilization with managed/serverless instead of idle capacity?

Do efficiency/Region choices factor in carbon impact?

Do you avoid storing/processing data you don't need (lifecycle, sampling)?

Is efficiency tracked as a KPI for your workloads?