One person shipping a regulated-industry asset on AWS — with an AI agent doing the heavy lifting. I wanted to know if it was real or just another LinkedIn fairytale.

🎵 Song of the day: Free Bird — Lynyrd Skynyrd. Press play. The first half is calm, reflective, “Lord knows I can’t change.” Then the guitars show up and don’t leave for four minutes. That’s basically this whole story, so set the mood.

“One person can now ship what used to take a team.”

I kept reading some version of that sentence. In talks, in threads, in every other post on my timeline. The “high-value individual contributor” — the IC who isn’t a manager but somehow moves like a whole squad. It sounded great. It also sounded like the kind of thing people say on a conference stage and never actually prove with their hands dirty.

So I stopped reading and did what I usually do. I tested it.

One project. The hardest target I could pick: a production-grade asset for a regulated financial-services workload, on AWS, with Claude Code doing the engineering volume. This isn’t me declaring I’m a high-value IC — let’s keep the ego in the garage (even though I have some to spare). It’s me telling you what happened when I tried to be one on purpose, for one project, and watched whether the thesis survived contact with reality.

Why I picked something that could hurt

A to-do app proves nothing. A landing page proves nothing. If I wanted to actually stress the idea, I needed a target where shortcuts get punished — hard.

Financial services are regulated and audited, and they do not forgive sloppiness. Security posture and traceability aren’t features you bolt on at the end while whistling — they’re the door you have to walk through before you’re even allowed in the building. My logic was simple: if one person can hold the line here, the thesis is real. If it breaks, it breaks where it matters most.

FSI was the stress test. Not the hero of the story — the thing that gets to punch the story in the face and see if it stays standing.

First, a confession: I started full extreme go horse

Let me be honest about how this began, because the polished version would be a lie.

The first weeks were pure extreme go horse. If you don’t know the term — it’s the noble engineering art of “commit now, think later, the deploy is the test.” No tickets, no plan, just me, a terminal, an agent, and the dangerous confidence of someone who’s pretty sure he remembers how OAuth works. Branches with names that I only understood. Code that worked on Friday and filed for divorce on Monday. The classic.

And here’s the thing about go horse with an AI agent in the loop: it’s faster go horse. You can now generate a beautiful mess at a speed that would make 2015-me weep. The agent happily gallops wherever you point it. The problem was never the speed. The problem was me pointing it at chaos.

The turning point wasn’t a tool. It was admitting the cowboy phase doesn’t scale past about day ten.

Then I did the unthinkable: I opened Jira

I know. I felt it too.

Jira is the cavalry of every technical person — and, mysteriously, paradise for the governance crowd. We mock it during standups and then quietly admit at 2 am that the board was right. So I swallowed my pride and put the work into tickets. Every piece of scope became a card. Every card had a definition of done. Boring. Adult. Effective.

But here’s the plot twist that made it click: once the work lived in Jira, the agent could read the backlog. The thing I hated for a decade became the input layer for an autonomous loop. The card scopes the work, the agent executes against it, and when the card transitions to Done, it’s because a real condition was met — not because I felt finished. Governance people, you can stop smirking. You were right. There, I said it. Don’t make it weird.

Go horse got me velocity. Jira got me a system. Turns out you need the second one if you ever want to sleep.

Then I organized the repositories like an adult

The last piece was the least glamorous and the most important: I stopped treating the repo like a junk drawer.

Clear module boundaries. A free core, separated from paid modules, separated from the platform plumbing. Everything in Terraform, so the whole estate was reproducible — build it, tear it down, build it again before lunch. Branch protection so even I couldn’t push something stupid straight to main at midnight. CI that ran on every change, whether I asked nicely or not.

Sounds tedious. It is. It’s also the difference between an agent that’s a force multiplier and an agent that’s a very fast intern with no map. Structure is what turns “AI wrote my code” from a confession into a strategy.

The leverage didn’t start where I expected

Here’s what surprised me most: the leverage doesn’t start with the AI. It starts with the foundation underneath it.

I went serverless-first on AWS, because that’s what makes one person owning everything physically possible:

• Lambda on Graviton — nothing to patch, nothing to babysit, cost that scales down to zero when nobody’s looking.
• Aurora Serverless v2 and DynamoDB on-demand — no capacity planning, no 3 am call because a connection pool decided to retire early.
• API Gateway, CloudFront, WAFv2, Cognito — the OAuth / OIDC plumbing, without me hand-rolling crypto like a maniac.
• Terraform for all of it — reproducible, reviewable, disposable.

Here’s the honest realization. Serverless shrinks the operational surface so much that one person can credibly own security, reliability, performance, and cost at the same time. Ten years ago, each of those was somebody’s full-time job. Four people, minimum, plus the one who owned the wiki nobody read. That collapse, on its own, is half the thesis.

The part I expected to break

Then the agent — the part I was sure would fall apart in a regulated context.

I set up Claude Code not as fancy autocomplete, but as a loop that runs on its own:

• A scheduled agent working off the Jira backlog — not sitting there waiting for me to type, like a very expensive parrot.
• Quality gates on every single change: tests, Terraform validation, security scans, and SBOM generation. In a regulated workload that last part matters more than it sounds — the compliance evidence trail builds itself, card by card.
• Merge by construction — work ships when the defined conditions hold, and the agent stops and asks me when something is irreversible or when it’s genuinely unsure. The cowboy from chapter one would never. The system does it by default.
• Custom commands and subagents for the recurring grind — IAM debugging, chaining pull requests, scoping the next card.

The shift in my own day was real. I stopped writing most of the code and started designing the system that writes and ships it safely. My job became the guardrails and the judgment calls. Everything mechanical, I handed off — including, blessedly, half the things I used to get wrong at midnight.

The moment it stopped being a theory

The thesis got real for me during the security work.

Instead of fixing risks one at a time — the way you do when you’re drowning — the AWS primitives let me close whole classes of risk by design. Short-lived STS roles instead of long-lived keys you forget exist until they leak. Secrets pulled out of connection strings and into IAM. Authenticated encryption everywhere, not just where someone happened to remember. Explicit allowlists instead of lazy wildcards. A full scanning and SBOM gate wired straight into CI.

One person, enforcing a security posture across the whole estate — because the platform made the secure path the default path, and the agent enforced it in all the places I would never have checked by hand.

That’s the sentence I keep coming back to. The platform made secure the default. The agent enforced it where I couldn’t look. And Jira, fine, Jira made sure none of it got lost.

What I actually concluded

The thesis held. But with a condition I didn’t see going in.

It is not “AI replaces the team.” Anyone selling you that is selling you something, probably a course. What I found is that the leverage is a stack:

1. A serverless AWS foundation that shrinks the operational surface until one person can hold it.
2. An agent like Claude Code that handles the volume — safely, with gates, knowing when to stop.
3. A human who spends all their attention on the irreversible and the strategic, and delegates the rest.

And underneath all three, the unglamorous trio I resisted for weeks: a backlog, structure, and the humility to ship by condition instead of by vibe. Go horse gives you a demo. The system gives you a product.

Pull out any one layer and you’re back to needing a team. Serverless without the agent is just less to manage. The agent without structure is fast code on shaky ground — a thoroughbred in a parking lot. And all of it, without a human making the judgment calls, is exactly the disaster you’re imagining right now.

Stack them, though — and yes. One person can ship something a regulator would take seriously.

So, builder to builder

Don’t argue about whether the high-value IC is real. Go test it on something that scares you a little. Start as a cowboy if you must — I did — but know the exact day you have to grow up and open the board.

And for the AWS community specifically: this is a concrete, repeatable pattern, not a thought experiment. Serverless plus agentic AI is genuinely changing what a single builder can own, end to end, even in a regulated industry where the margin for error is basically zero.

That’s not a prediction. It’s just what I saw when I tried it.

(Free Bird’s outro is probably still going. Let it.)

O re:Invent é o maior evento de nuvem da Amazon Web Services (AWS), esse é a minha sétima edição, me juntando a mais de 50.000 pessoas. Esse ano decidi fazer algo menos técnico, voltado pro público que enxerga a operação a 10.000 metros de altura.

O assunto do ano sem dúvida são dados e IA (Inteligência Artificial) Generativa (GenIA) e sua aplicabilidade. Além de toda essa nova era da Tecnologia da Informação (TI), passamos por conteúdos tão importantes quanto: qual a real motivação de ir para a nuvem, segurança, como modernizar aplicações, como manter o controle financeiro sem prejudicar a inovação, histórias de inclusão e sustentabilidade.

Generative IA

Amazon Q certamente foi o lançamento mais emblemático. Apesar de termos Bedrock com seus Large Language Models, e o Sagemaker com seus Foundation Models, o Amazon Q chegou para ser seu assistente empoderado por GenIA. A utilização vai desde descrição de produtos e serviços AWS até se conectar a seus sistemas e responder questões privadas da sua própria empresa. Passa também por recomendações e remediações do código de maneira automática. Aumento de produtividade, assertividade de código e evolução do próprio repositório de respostas estão nos pontos fortes desse produto. Já em disponibilidade geral, basta ter uma conta e começar a usar. Já tem integrações nativas com a AWS Quicksight (dashboards inteligentes) e também com o Amazon Connect (solução de atendimento ao cliente via voz).

MOTIVAÇÃO DE IR PARA A NUVEM

A AWS sempre enfatiza a importância da definição clara das principais motivações para migração e adoção de nuvem. Esse foi um ponto comum em muitas das sessões desse ReInvent, pois a definição desses motivos com clareza é fundamental para garantir que todos os stakeholders estejam alinhados com os objetivos da migração, para planejar adequadamente os recursos necessários, e para medir o sucesso da migração com base em critérios pré-estabelecidos. Além disso, ajuda a criar uma estratégia de migração mais eficiente e orientada para resultados específicos.

Na sessão Architecture-led portfolio migration and modernization (ENT236), Sibu Kutty, demonstra a importância de ter essas motivações como base para definição da estratégia de migração do portifólio de aplicações combinada com Enterprise Architecture, ou seja, chegar em uma boa estratégia para quando e como as aplicações irão passar pela estrutura dos 7Rs (refatorar, reformular, recomprar, rehospedar, realocar, reter e aposentar), já que principalmente em migrações nível enterprise, a quantidade de aplicações, interdependências e cenários possuem tamanhos e complexidades enormes, precisando de estratégia para que as fases de migração sejam encaminhadas com sucesso.

Foram apresentados cases de migração de Adidas e Petronas e os principais takeways foram:

· Tenha um approach holístico, avaliando não somente tecnologia e ferramentas, mas também: custos, pessoas, futuro e alinhamento com os resultados esperados

· Faça o primeiro nível de mapeamento de Business Capabillity, especialmente para as aplicações estratégicas

· Defina requisitos, outcomes (diretos e indiretos) da migração

· Tenha patrocínio executivo e se assegure de estar envolvendo as pessoas certas

· Invista muito em comunicação para manter essas pessoas engajadas, habilitadas e empolgadas

E finalmente execute a migração em ciclos curtos, que permitam aprendizado e ajustes, pois esses pontos serão fundamentais para ter mais acertvidade no processo e em seus resultados.

SEGURANÇA

Depois de GenIA, segurança é o principal assunto durante a feira. Seja para criar as fundações, treinamento, aplicações, autenticação e autorização entre serviços e cargas de trabalho. Segurança não é simplesmente causa e efeito.

Stephen Schmidt, Vice Presidente e CISO da AWS teve sua sessão pautada sobre como os serviços da AWS, como Bedrock e CodeWhisperer, ajudam a enriquecer os ambientes com segurança de maneira automática com GenIA.

Em uma outra sessão importante em conjunto com o Banco DBS, foram demonstradas anatomias de ciberataques e como os serviços AWS podem identificar, isolar e remediar ameaças.

Tiveram também sessões mais técnicas que envolveram como usar os princípios do Well-Architected Framework para proteger as cargas de trabalho, como desenvolver esteiras de desenvolvimento seguras e muita integração dos desenvolvedores com CodeWhisperer. Uma das sessões mais emblemáticas foi de gerenciamento de riscos com os boards das empresas. Regulações como PCI-DSS, jornadas hibridas de nuvem e compliance, onde Fernando Cardoso, da Trend Micro, trouxe uma visão clara de como abordar o tema e avançar talvez na mais importante e crítica agenda para as empresas. Uma previsão importante é que em 2026, 70% das empresas incluirão um membro no board com experiência em cybersegurança.

MODERNIZAÇÃO DE APLICAÇÕES

Gregor Hope entregou uma sessão clara e objetiva sobre dimensões na modernização de aplicações. Se olharmos em apenas uma dimensão, não temos a liberdade da escolha, ou ocultamos fatores inerentes a nuvem, como velocidade e facilidade de atualização de sistema — ou vendor- e o treinamento de time para novas maneiras de pensar e operar suas cargas de trabalho. Esses desafios estão no roadmap de todos CXO principalmente pela questão do lock-in de plataforma.

Principais takeways

- Não tente resolver considerações de aplicação (como portabilidade) apenas na camada de infraestrutura.

- Portabilidade de aplicações entre nuvens não é simples como parece. Integração, segurança, observabilidade, sensibilidade a latência são aspectos importantes no momento de ideação de como construir sua aplicação.

- Camadas lógicas não podem abstrair características físicas, como precificação, escalabilidade, latência, gerenciamento de erros e disponibilidade de serviço geográfico. Todas essas características físicas podem ser contornadas com opções, porém há sempre uma escolha que pode custar: esforço (de diversos times), custos de oportunidade (não confundir comodity com real valor agregado), complexidade (há diferentes caminhos para a mesma solução. Teste, mas erre rápido) e utilização abaixo do esperado (você precisa mesmo da infraestrutura do Netflix para o seu negócio?)

- Se utilize de plataformas de código aberto de maneira gerenciada. Você ganha tempo, agilidade e também não se preocupa com atualizações, vulnerabilidades e fardo dos seus times de produto, que podem se preocupar com o que é importante (a experiência do seu cliente final).

Adotando esses princípios, seu negócio elimina fricção com automações (Devops), você reduz o inventário do seu parque (Lean) e evita trabalho de baixo valor (o que te torna Ágil).

Tudo isso para dizer: Qual sua intenção ao escolher os produtos e serviços da sua solução?

Os principais itens ao final e que podem inspirar os líderes são:

1. reformule o pedido do desafio (qual a motivação);

2. velhas abordagens não funcionam mais (abstração de camadas técnicas)

3. repense as suas alavancas de trabalho (pense em padrões de design, não de serviços.

CLOUD FINANCIAL MANAGEMENT — FINOPS

Nos últimos anos, o “pão quentinho” era migrar para a nuvem, o que diversas empresas o fizeram. Assuntos como segurança e o Day 2 Operation (capacidade dos times de operar suas cargas de trabalho pós-migração) estavam nas agendas prioritárias dos clientes. Porém a observância do último ano nos leva a como ser mais eficientes na nuvem, controlando custos sem ofender a inovação. A agenda de Cloud Financial Management, ou Finops tem se destacado em um ano tão desafiador como esse. E para os próximos anos, está nas agendas dos CxOs como prioridade. Os principais pilares estão baseados primariamente em Pessoas (treinamento, cultura e responsabilidade), Arquitetura e Padrões (estabelecer baseline mínimo de utilização de recursos), Ferramentas (diversos “sabores” para diferentes tamanhos de empresa e workloads) e Analytics (“o que não pode ser medido não pode ser gerenciado”). Urge a necessidade de entender o novo modelo de precificação da nuvem, e suas variâncias. Podemos exemplificar o novo modelo como uma maior integração entre áreas (Finanças, Tecnologia e Negócios) além de medir dia-a-dia novas cargas de trabalho, ambientes não-produtivos e estratégias de otimização de uso (instâncias reservadas, instâncias spot e tagging de todos os recursos). Os principais pontos para a jornada são: A medição não deve ser limitada a cargas de trabalho específicas (o ecossistema completo é chave do sucesso). Entenda as necessidades dos usuários(seus clientes internos) e do negócio (o que queremos ao lançar ou modernizar um produto). E por fim: medir. Meça, analise, compare e tome ações que diferenciarão sua empresa de agora comparada há um ano atrás.

INCLUSÃO

Certamente um dos painéis que mais chamaram a atenção foi sobre neurodiversidade. Há um dado que demonstra que apenas 12% das empresas tem treinamento específico de como lidar com pessoas neuroatípicas e 43% das pessoas que possuem algum grau de autismo perderam o emprego em algum momento por falta de entendimento e suporte a suas condições. Porém ainda não há a percepção das vantagens dessa pluralidade nas empresas. Pessoas neurodivergentes são hiper-focadas, inovativas e criativas, que são características transformacionais para todo negócio. Para uma relação objetiva, as empresas devem fornecer tarefas claras para execução, planejar de maneira cuidadosa, se comunicar com clareza e sempre perguntar e não assumir que os profissionais tenham entendido seus desafios.

Como pensamento final para esse tópico, aceite, eduque, celebre e normalize a neurodiversidade.

A AWS tem um conjunto de boas práticas chamado Inclusion Powered Playbook que auxilia as empreas a lidar com a neurodiversidade.

EDUCAÇÃO

Valeria Singer apresentou um painel muito reflexivo de como criar uma força de trabalho de nível de entrada com estudantes e profissionais em transição de carreira. Esse painel teve participação de parceiros AWS que falaram sobre as vantagens de investir em educação, e assim fidelizar seus profissionais e estimular a pluralidade de pensamento e diferentes abordagens para resolver o mesmo desafio. Para isso foi criado o Tech Alliance. Essa comunidade alimenta empresas em diferentes localidades (Illinois, Nova Iorque e Espanha). Um diferencial em investir em profissionais no nível de entrada, é recrutar e acompanhar os próximos líderes em diversas áreas. Atualmente há uma janela de oportunidade onde 57% das empresas da Europa admitem que há uma necessidade de profissionais capacitados em seus negócios. Em Nova Iorque, os negócios relativos a nuvem crescem 15% ao ano. Esses dados abrem um espaço gigantesco para que AWS, Parceiros e Clientes solucionem desafios, melhorem sua força de trabalho e o mais importante, que sejam um celeiro de novos talentos.

SUSTENTABILIDADE

Incluído em 2022, o pilar de Sustentabilidade foi acrescentado aos outros cinco já existentes (excelência operacional, segurança, confiabilidade, eficiência de performance, otimização de custos) no AWS Well-Architected Framework (https://aws.amazon.com/pt/architecture/well-architected). A redução da pegada de carbono enfrenta diferentes desafios referentes a regulação em diferentes países, além de investimentos adiantados onde o ROI (retorno sobre o investimento) não é claro. Consultorias Globais em seus estudos dizem que empresas que direcionam seus esforços para a sustentabilidade podem sim ter um melhor desempenho financeiro (HBR, 2018), aumentam a retenção de talentos (Bain & Company, 2022) e aumentam a lucratividade (McKinsey, 2021). Soluções diligentes arquiteturais utilizando computação com maior eficiência operacional (Processadores AWS Graviton), massivo uso de serviços gerenciados (RDS, Opensearch, ECS, EKS, etc) desacoplamento de monolitos utilizando containers e serverless, além de medições e revisões constantes de suas cargas de trabalho, fazem a diferença diariamente. Um aliado nessa jornada é o AWS Customer Carbon Footprint Tool, onde o cliente pode ter uma visão da sua pegada de carbono baseado na utilização dos recursos em diferentes regiões. E para constante otimização, três dicas valiosas para a jornada: Tenha log de tudo (infra, aplicação, comportamento de usuário) para medição, auditoria e decisões arquiteturais. Backup de informações em armazenamento de longa durabilidade, seja por questões regulatórias e/ou reduzir dado ocioso em armazenamento mais caro.

E por fim: todo milissegundo conta. O quanto mais rápido for sua aplicação, menos energia você consome, ajudando assim a redução da pegada de carbono.

References:

Do modern cloud applications lock you in? (ARC307) — Gregor Hohpe
Working globally to build tech skills and talent pipelines (WPS104)
Building your green future today: Unlocking secrets to sustainability (COP229)
Sustainable compute: Reducing costs and carbon emissions with AWS (CMP212)
Sustainability innovation in AWS Global Infrastructure (SUS101)
Digitizing energy management for a sustainable future with Iberdrola (BIZ107) Building neuroinclusive cloud experiences (IDE201)
Inclusive design thinking in tech: Fostering innovation for all (IDE202)
Move fast, stay secure: Strategies for the future of security (SEC237)
Improving security through modern application development (SEC227)
Building a comprehensive security solution with AWS security services (SEC226)
Shipping securely: How strong security can be your strategic advantage (SEG203)
Future-proofing cloud security: A new operating model (SEC208)
The origin of cloud security challenges and a revolutionary solution (SEC231)
Cyber risk management: Bringing security to the boardroom (SEC204)
FinOps tips for optimizing your cloud infrastructure and data costs (COP224)
Reinvent your cloud strategy: Optimize performance & cut cloud costs (CON326)

***Updated*** AWS re:Invent 2022 — Complete Session Guide

Disclaimer: Not all sessions were included in this guide.

TL:DR — Ran for all 1394 available sessions on re:Invent site, and created four groups of sessions that represent what I believe could be helpful for companies and individuals that want to adopt, migrate, operate and modernize your workloads on AWS.

AWS re:Invent is the time to connect with friends, customers, and the AWS team for an entire week of knowledge and, most importantly: to share. For the 11th edition, twelve paid bootcamps, the return of 5k run and six different venues as shown.

As standard, AWS divides sessions in categories (STG for storage, COP for Cloud Operations, DAT for Data, etc.) and different difficulty levels. Reference for the levels below:

level 100 — Foundational — 37 sessions
level 200 — Intermediate — 535 sessions
level 300 — Advanced — 732 sessions
level 400 — Expert — 90 sessions

There's the official track guide from AWS Heroes and Community Builders where you can find by topic, the recommendations of sessions. Highlights for DevTools track written by Marcelo Palladino and Francisco Edilton and Machine Learning, written by Vinicius Caridá (Go Brazil!).

My session guide is humbler but I understand that it could help different stages of cloud adoption of companies. So, fasten your seatbelts, get your most comfortable pair of shoes, assure you have Carmex, Pedyalite and gallons of water for the most intense week of the year

Foundation — Should I go to AWS? (go, always!)

BOA103 — Infrastructure provisioning for your application in the cloud

BOA101 — Journey to cloud networking

BOA106 — Building observability and monitoring for your applications on AWS

BOA102 — Building secure serverless applications on AWS

BOA105 — Understanding the basics of cloud economics

TNC109 — Building the foundation for cloud governance

ENT212 — Understanding the migration journey

PRT221 — The next frontier: Driving innovation with platform standardization (sponsored by Capital One)

ARC217-L — Building modern apps: Architecting for observability & resilience

DOP201 — AWS infrastructure as code: A year in review

ENT217 — Learning at the speed of cloud: Turning employees into entrepreneurs

ENT219 — Everybody wins: Real-world business value for CIOs and CFOs with the cloud

STG213 — Choosing the right AWS storage service for the job

ARC210 — The well-architected way

AIM209 — Create & label high-quality datasets for training machine learning models

WPS205 — Lessons learned from IT modernization and transformation

SEC208 — Executive security simulation

STG206 — Data resiliency design patterns with AWS

SEC203 — Revitalize your security with the AWS Security Reference Architecture

ENT213 — How to migrate, modernize, and grow using the AWS MAP

API203 — Examples of event-driven application integration patterns

ARC205 — Establishing your cloud foundation on AWS — beyond your landing zone

BIZ208 — Deliver a resilient, personalized experience at scale with Amazon Connect

SEC204 — Analyze your network using Amazon VPC Network Access Analyzer

SEC202 — Vulnerability management with Amazon Inspector and AWS Systems Manager

COM207 — Competition of the modern workloads: Serverless vs. Kubernetes on AWS

PEX202 — TCO analysis with AWS services and Migration Portfolio Assessment

ARC201 — Advanced multi-AZ resilience patterns: Mitigating gray failures

OPN201 — An introduction to open-source monitoring with AWS

NET201 — Build highly available applications using Elastic Load Balancing

TNC211 — Create a CI/CD pipeline to deploy your application to AWS Fargate

STG207 — Data protection and governance on AWS

NFX202 — Decoupling identity, compute, and network residency on AWS

DOP204 — Provisioning, automating, and orchestrating IaC on AWS

DAT208 — Effective multi-tenant solutions using Amazon Aurora Serverless v2
CON201 — The AWS container services journey: A detailed look

NFX201 — Optimally capacity planning workloads in the cloud

FWM201 — Create engaging user experiences with real-time data using pub/sub APIs

DAT204 — Predictive analytics using Amazon Timestream

CON203 — Explore the foundations of AWS container services

COP206 — Strengthen your governance posture with AWS Control Tower

OPN203 — Get started with OpenSearch

CMP205 — HPC on AWS: Solve complex problems with pay-as-you-go infrastructure

COP204 — Proactive governance and compliance for AWS workloads

TNC208 — Running applications on Amazon EKS

COP202 — Cloud metrics strategy and customizable billing

TNC223 — AWS Partner: Building data analytics solutions using Amazon Redshift

TNC222 — AWS Partner: Building data lakes

COM206 — ID verification: Who can you trust?

SEC201 — Proactive security: Considerations and approaches

SEC211 — Disaster recovery and resiliency for AWS data protection services

DOP203 — Amazon’s DevOps culture

ANT204 — Enabling agility with data governance on AWS

ARC215 — Is your architecture as resilient as you think?

ENU202 — Modernizing enterprise architectures, featuring ExxonMobil

WPS208-L — Building for a better future: Agility, speed, and security

PRT285 — Cash is alive: How technology has enabled phygital at scale (sponsored by Capital One)

STG220 — Best practices for moving on-premises applications to Amazon EBS

DAT201 — Data modeling best practices with Amazon DocumentDB

PRT276 — Simplify and accelerate security for simple storage: Case studies

NET207–2022 AWS Threat Landscape Report

ANT212 — How JPMC, LexisNexis, and PPB modernize analytics with Amazon Redshift

ARC209 — Put your cloud cost on track

INO201 — Rapid transition from idea to solution

ENU201 — Identifying and realizing business value with AWS

COP218 — Measuring your cloud unit economics

DOP204 — Provisioning, automating, and orchestrating IaC on AWS

STP203 — Security from day one: Establishing a baseline

STG219 — Build resilient architectures with Amazon EBS

PEX211 — Data platform strategy shaping enterprise transformation agendas

COP210 — How FINRA democratized operational data using Amazon Managed Grafana

CPG203 — Kellogg’s modernization journey: A worldwide business transformation

STP212 — Simple steps to prepare your environment for compliance

STG207 — Data protection and governance on AWS

ENT218 — The architect elevator: Connecting the boardroom and IT

SEC212 — AWS data protection: Using locks, keys, signatures, and certificates

DOP207 — AWS Well-Architected best practices for DevOps on AWS

STP208 — Designing resilient architectures for startups

NET205 — Observing and diagnosing your network with AWS

FSI201 — Goldman Sachs: Accelerating time to value in data analytics

SEC207 — Simplify your existing workforce access with IAM Identity Center

NET212 — Application networking best practices

PRT235 — Best practices for AWS observability and automation (sponsored by Dynatrace)

PRT268 — Camada Zero: A real-world architecture framework (sponsored by Itaú-Unibanco)

PRT269 — How a financial company can become a cloud service provider (sponsored by Itaú-Unibanco)

NFX202 — Decoupling identity, compute, and network residency on AWS

ANT219 — Dow Jones and 3M: Observability with Amazon OpenSearch Service

ENT232 — Accelerating your migration journey

SEC210 — AWS and privacy engineering: Explore the possibilities

BOA204 — When security, safety, and urgency all matter: Handling Log4Shell

PRT206 — Cloud-native leading practices for NLP with Eli Lily and PwC (sponsored by PwC)

OPN302 — Signal correlation: The why and how

BOA302 — The serverless future of cloud data analytics

ANT310 — Build a data mesh with AWS Lake Formation and AWS Glue

BOA329 — Ideal blueprint versus reality for CI/CD pipelines

NET304 — AWS network architectures for very large environments

ENT319 — Achieve high availability and disaster recovery with SQL Server

NET302 — Advanced VPC design and new Amazon VPC capabilities

FSI307 — Advanced cross-Region disaster recovery patterns

STG321 — Advanced networking for Amazon S3

STG301 — Amazon S3 security and access control best practices

STG308 — Amazon S3 security patterns and anti-patterns

CMP308 — Build resilience in your web applications with Auto Scaling

XNT302 — Build, test, and deploy your .NET applications on AWS

ARC301 — Building a monitoring strategy

FSI302 — Building highly available systems for financial services

BOA310 — Building observable applications with OpenTelemetry

NET308 — Building secure VPCs and integrating them into your network

BOA307 — Building well-architected serverless applications

COP306 — Cloud compliance and auditing best practices on AWS

COP304 — Cloud compliance, assurance, and auditing

CMP302 — Confidential computing with AWS compute

STG315 — Configuring Amazon S3 security settings and access controls

BOA320 — Demystifying VPC IP addressing & creating a complete routing solution

DOP304 — Developing CI/CD pipelines with AWS

SVS307 — Observability for serverless solutions with AWS Lambda Powertools

COP301 — Observability the open-source way

ANT303 — Observing logs and traces with Amazon OpenSearch Service

COP303 — Provision and customize accounts using Terraform with AWS Control Tower

COP311 — Simplify continuous compliance and evidence collection with the cloud

OPN302 — Signal correlation: The why and how

STP301 — Startup security: Techniques to stay secure while building quickly

STG313 — Stay in compliance with AWS data protection services

DOP301 — The Amazon Builders’ Library: Operational excellence at Amazon

SVS305 — Understanding AWS Lambda concurrency

SVS304 — Understanding and implementing observability for serverless

STG304 — Using AWS Backup to protect your cloud resources & hybrid environments

ENT306 — SQL Server on AWS: Run with the best

BOA325 — Building a serverless Apache Kafka data pipeline

PEX304 — Building a serverless data consumption platform on AWS

STG302 — Building and operating a data lake on Amazon S3

ANT305 — Building your data strategy? Think integration first!

FSI303 — Drive business value with a multi-account data mesh

COM306 — Bringing software engineering rigor to data

ARC316 — Automating (near) zero-RPO disaster recovery across multiple AWS Regions

SVS318 — Building modern API architectures: Which front door should I use?

ANT326 — How BMW, Intuit & Morningstar are transforming with AWS and Amazon Athena

ENT323 — How to set up Microsoft identity solutions on AWS

PRT311 — Integrating optimization into your cloud journey (sponsored by Granulate)

HYB303 — Architecting and delivering low-latency applications at the edge

PEX304 — Building a serverless data consumption platform on AWS

CMP306 — Building apps to isolate & process sensitive data with AWS Nitro Enclaves

CON318 — Securing Kubernetes: How to address the main Kubernetes vulnerabilities

STG324 — Protect AWS resources with AWS Backup

COM301 — Unleash developer productivity with infrastructure from code

SEC330 — Harness the power of temporary credentials with IAM Roles Anywhere

ANT337 — Migrating to Amazon EMR to reduce costs and simplify operations

ANT303 — Security and data access controls in Amazon EMR

PRT303 — The digital transformation journey: Santander UK (sponsored by Salesforce)

API313 — Understanding design in event-driven architecture

FSI304 — Your blueprint to secure customer-facing applications on AWS

SEC332 — Build securely on AWS: Insights from the C-suite

STG327 — Building a hybrid data pipeline to Amazon S3 using AWS Storage Gateway

DAT316 — Build resilient applications using Amazon RDS and Aurora PostgreSQL

ARC301 — Building a monitoring strategy

EUC306 — Getting started with Amazon WorkSpaces

COP303 — How Global Payments scales on AWS with governance and controls

DOP314 — Governance and security with infrastructure as code

MFG304 — Connecting VW plants to the AWS Cloud at scale

ARC306 — Multi-Region design patterns and best practices

SVS302 — Architecting secure serverless applications

FSI315 — Build a capital markets data hub with Amazon FinSpace

STG334 — Build data mesh architectures using AWS Transfer Family & AWS Lake Formation

SUS303 — Delivering sustainable, high-performing architectures

FSI317 — Trading up: Fidelity Investments takes trading to the cloud

ANT301 — Democratizing your organization’s data analytics experience

STP303 — Deploying a complete machine learning fraud detection solution

API302 — Building global event-driven applications

FSI303 — Drive business value with a multi-account data mesh

COM313 — Design for reliability with the AWS Well-Architected Framework

ARC305 — Reducing your area of impact and surviving difficult days

FSI308 — Chase International: Always-on customer experience at scale

SVS311 — Practical experience with a serverless-first strategy at Capital One

SEC311 — Securing serverless workloads on AWS

STG315 — Configuring Amazon S3 security settings and access controls

FSI314 — Multi-Region workloads with AWS DevOps tools and Terraform

API314 — What’s possible with AWS Step Functions

ENU303 — Architecting for resiliency and high availability

COP315 — Building a secure and scalable environment in regulated industries

CMP302 — Confidential computing with AWS compute

SEC326 — Establishing a data perimeter on AWS, featuring Goldman Sachs

ARC314 — Publishing real-time financial data feeds using Kafka

FSI302 — Building highly available systems for financial services

STP301 — Startup security: Techniques to stay secure while building quickly

ARC328 — AWS Well-Architected best practices: Let’s talk implementation

PRT322 — Cloud FinOps: Empower real-time decision making (sponsored by VMware)

API310 — Domain-driven design and event storming

COP329 — Observability patterns for highly available applications

AIM307 — JPMorganChase real-time agent assist for contact center productivity

SEC321 — Building your forensics capabilities on AWS

DAT307 — Turbocharging your applications with AWS in-memory databases

DOP319 — Zero-downtime deployment strategies

ARC318 — Best practices for disaster recovery of workloads on AWS

DAT302 — How Wiz uses graphs to gain security insights with Amazon Neptune

SVS321 — Are you ready? Essential strategies for Kubernetes adoption

SEC323 — Data discovery and classification on AWS

ARC309 — A real-world resilience evolution in the cloud framework

FSI313 — AIG: Transforming catastrophe modeling on AWS

ARC317 — Architecting security and governance across your multi-account environment

API312 — How to select the right application integration service

COP337 — Prescriptive guidance for scaling your resource and application management

SEC318 — Scaling the possible: Digitizing the audit experience

ARC321 — Using a multi-account strategy to enable hyperscale

DOP320 — Building a self-service developer portal

ARC319 — Designing a multi-account environment for disaster recovery

SEC333 — Designing compliance as a code with AWS security services

ARC315 — Designing resilient serverless architectures

ANT331 — Understanding TCO for different Amazon EMR deployment models

SUP309 — AWS Well-Architected Framework security pillar: Cloud security at scale

COP312 — Commonwealth Bank’s cloud compliance journey

API303 — Application integration patterns for microservices

SUP311 — Design with operations in mind

PRT306 — FinOps: Intersecting cost, performance, and software license optimization (sponsored by Flexera)

COM312 — Set up governance guardrails across your multi-account environment

NET306 — Building resilient networks

STP306-R1 — Evolving your security capabilities through key growth stages

ANT336 — Building data mesh architectures on AWS

ARC327 — How to optimize cost in your multi-tenant architecture

PRT319 — Navigating decentralized futures (sponsored by Capgemini)

FSI310 — NYSE: Protecting markets through real-time data processing

STG338 — Beyond 11 9s of durability: Data protection with Amazon S3

COP313 — How Goldman Sachs flipped the cloud center of excellence on its head

DAT401 — Build a web-scale application with purpose-built databases & analytics

XNT402 — Designing cloud-native .NET applications

CON401 — From zero to production with Amazon EKS Blueprints

OPN401 — Observing logs and traces with OpenSearch

ENT401 — Run Windows containers on Amazon EKS, Amazon ECS, and AWS Fargate

PRT401 — State of cloud: The shift from consumers to creators (sponsored by Pluralsight)

AIM402 — Extract AI-driven customer insights using Post-Call Analytics

ARC401 — Achieving extreme resiliency through recovery-oriented architectures

DOP402 — Implementing DevSecOps pipelines with compliance in mind

SUP401 — Building resilient multi-site workloads using AWS global services

COM402 — Why build a cloud center of excellence?

CMP406 — Run Spark applications for less with Amazon EMR and Amazon EC2 Spot Instances

SEC403 — Protecting secrets, keys, and data: Cryptography for the long term

DOP403 — Multi-account and multi-Region deployments at scale

SEC405 — Zero Trust: Enough talk, let’s build better security

Migration — Pretty straightforward. Get your stuff and move to AWS.

ENT205 — How to save costs and optimize Microsoft workloads on AWS

DAT202 — Top 5 patterns to unblock complex relational database migrations

TNC226 — AWS Partner: Migration business case development

ENT224 — Migration made simple: Aon’s cloud transformation with VMware Cloud on AWS

STG214 — Accelerate secure data migrations at scale with AWS DataSync

SUP203 — Accelerate your migration and modernization with AWS Support

DAT209 — Best practices for migrating to Amazon DocumentDB

WPS206 — Learn how to migrate mission-critical systems to AWS

PEX214 — Building a successful migration & modernization practice for AWS Partners

DAT202 — Top 5 patterns to unblock complex relational database migrations

ENT233 — Faster migrations with VMware Cloud on AWS

HYB205 — AWS Snow Family: Bringing AWS to the rugged, mobile, and disconnected edge

CMP202 — Move your first application to the cloud with Amazon Lightsail

STG210 — Best practices for moving data to AWS, online and offline

DAT218 — What’s new with database migrations

PRT207 — Assuring and securing AWS migrations with NETSCOUT visibility (sponsored by NETSCOUT

PRT229 — Crawl/walk/run: Migrating to the cloud with Kong and AWS (sponsored by Kong)

RET301 — Core elements of digital transformation

ENT321 — Secrets to a successful migration at scale

PEX302 — Accelerate migrations with AWS Migration Hub Orchestrator

DAT303 — Top 5 things to know when migrating from Oracle to PostgreSQL

ENT303 — Use Terraform to build Microsoft infrastructure on AWS

ENT305 — Operate Windows Server workloads at scale by using automation

STG318 — Migrate your on-premises data to AWS storage using AWS DataSync

PEX302 — Accelerate migrations with AWS Migration Hub Orchestrator

WPS301 — Migrating sensitive Oracle workloads to AWS

DOP308 — Develop AWS CloudFormation templates to manage your infrastructure

BOA313 — How to use Terraform to deploy AWS security solutions

DAT308 — Proven playbook for migrating from SQL Server to Amazon Aurora

DAT309 — Migrate relational databases to Amazon RDS or Aurora using AWS DMS & SCT

STG333 — Migrate your on-premises Hadoop data lake to Amazon S3 using AWS DataSync

FSI312 — Nasdaq: Moving mission-critical, low-latency workloads to AWS

DAT306 — Migrate from a relational database to Amazon DynamoDB

ENT318 — Replatforming a mainframe application to AWS with Micro Focus

ENT311 — Migrate and modernize Oracle E-Business Suite on AWS in 5 steps

COM309 — Become a full-stack developer: Migrating a company from GCP to AWS

STG329 — AWS Transfer Family: The future of managed file transfer

BOA326 — Lift and shift a web application to serverless: Yes, it’s possible!

ENT320 — Go hybrid: Migrate and modernize with VMware Cloud on AWS

ENT316 — Migrate the AWS Well-Architected way

ENT313 — AWS Migration and Modernization GameDay

HYB311 — How to simplify your hybrid cloud migration strategy with AWS

COP325 — Migrate AWS accounts like an expert

OPN303 — Modern data exchange using AWS data streaming

TLC303 — Verizon Connect transformation through their journey to the cloud

ANT314 — Why and how to migrate to Amazon OpenSearch Service

EUC308 — Best practices for migrating on-premises VDI workloads to the cloud

DAT327 — How Intuit migrated Apache Cassandra workloads to Amazon Keyspaces

DAT318 — Migrate and modernize multi-tenant databases using Amazon Aurora

ENT322 — Migrate and modernize at scale

COM311 — Migrating 600 databases to AWS and making them better, faster, and cheaper

ENT315 — Migrate and modernize at scale with a cloud migration factory

ENT325 — Migrating to the cloud: What is the cost of doing nothing?

SAS306 — SaaS migration: Inside a real-world multitenant transformation

Day 2 Operations — Alright, workloads migrated. Now, how do I operate it?

BOA105 — Understanding the basics of cloud economics

TNC107 — Use Amazon SageMaker Canvas to make your first ML model

COP224-L — Transform with AWS Cloud Operations: From vision to reality

SEC206 — Security operations metrics that matter

COP215 — Visualizing AWS Config and Amazon CloudWatch usage and costs
COP223 — Data-driven application performance monitoring with Amazon CloudWatch

STG204 — Optimize price and performance with Amazon EBS

COP201 — Gain visibility with AWS Cloud operations dashboards at scale

COP203 — Manage and control your AWS costs

CMP204 — Cost management with zero-waste computing

ARC202 — Putting cost optimization into practice

TNC214 — Secure your account during an active event

COP205 — Simplify your AWS cost estimation

NET203 — Successfully manage overlapping IP address ranges

STP201 — Success secrets for mergers and acquisitions

IMP203 — Manage the costs of mission applications in the cloud

COP222 — Get a 360-degree view of your observability data

STG212 — Protect data and lower costs with Amazon EBS snapshots

PRT289 — Reliable, secure, and efficient cloud operations (sponsored by Spot by NetApp)

TNC214 — Secure your account during an active event

COP216 — Why is continuous compliance important?

SEC209 — Continuous innovation in AWS threat detection & monitoring services

COP208 — Optimize other services: Save money by looking beyond traditional services

COP217 — Ways to avoid cost surprises

SUP201 — AWS Incident Detection and Response

COP214 — Streamline your audit log management and evidence reporting

COP209 — Automate to thrive: An evolutionary approach to operating in the cloud

CMP213 — Building a budget-conscious culture at Standard Chartered Bank

NET213 — How to build network observability for better experiences

STP210-R1 — AWS optimization: Actionable steps for immediate results

STP207-R1 — Automating and evidencing key compliance security controls

SUP305 — Hands-on AWS Support operational and resilience readiness

COP310 — Automate operations management on AWS

NET307 — Become a network support expert: We break it, you fix it

SUP301 — Automating threat detection and incident response

COP305 — Best practices for centralized operations management on AWS

STG337 — Best practices for managing Amazon S3 data at scale

STG312 — Build a disaster recovery solution with AWS storage services

SUP304 — Continuous cost and sustainability optimization

DOP310 — Continuous integration and delivery on AWS

BOA328 — Manage your infrastructure with Terraform and GitHub Actions

NET305 — Network operations, management, and governance best practices

API301 — Operational best practices for event-driven architectures

COP308 — Set up observability and monitoring on your Amazon EC2 and other resources

COP307 — Track and visualize your AWS cost and usage KPI targets

ENT302 — Troubleshoot Windows instances via AWS Systems Manager Fleet Manager

SUP302 — Troubleshooting from the perimeter

COP336 — Visualize, understand, and manage your AWS costs

COP320 — Complete operations management on AWS

COP341 — Get to know your application with OpenTelemetry and AWS X-Ray

COP333 — Building AWS Config rules to meet your custom compliance needs

COP306 — Cloud compliance and auditing best practices on AWS

CMP324 — Spot the savings: Use Amazon EC2 Spot to optimize cloud deployments

SUP303 — Intelligently automating cloud operations

SEC328 — Learn to create continuous detective security controls using AWS services

DAT304 — Optimize your Amazon Aurora resources to reduce costs

COP330 — Scale with managed open-source observability

COP318 — Setting up controls at scale in your AWS environment

WPS307 — Proactively protect critical applications

COP328 — Using Amazon EKS Observability Accelerator to collect signals on Amazon EKS

CON311 — Best practices for deploying microservices on Amazon ECS

COP324 — Extend your multi-account governance with automation

DAT321 — How Yahoo cost optimizes their in-memory workloads with AWS

NET324 — Manage your network using infrastructure as code

BOA324 — Resilient and well-architected applications with chaos engineering

ARC324 — Testing resiliency of AWS workloads using chaos engineering

COP319 — Automating patch management and compliance using AWS

SEC309 — Threat detection and incident response using cloud-native services

COP340 — Monitor end user experience with Amazon CloudWatch

COP309 — Accelerate AWS observability for your containers

STG335 — How to use Amazon S3 Storage Lens to gain insights and optimize costs

CON324 — Optimizing Amazon EKS for performance and cost on AWS

NET307 — Become a network support expert: We break it, you fix it

STG305 — Data protection & application recovery strategies for ransomware events

SEC301 — Threat detection and response workshop

SEC303 — AWS CIRT toolkit for automating incident response preparedness

SUP307 — Cloud optimization with Trusted Advisor and the AWS Well-Architected Tool

COP327 — Monitoring for business outcomes through SLO/SLI

NFX304 — Optimally capacity planning workloads in the cloud

COP322 — How to remediate and automate operational changes

STG331 — Remove the challenge of managing tape infrastructure with AWS Tape Gateway

COP316 — How to monitor applications across multiple accounts

COP342 — Become a dashboard expert

COP305 — Best practices for organizing and operating on AWS

ENT309 — Building a disaster recovery strategy with VMware Cloud on AWS

COP343 — Observability best practices at Amazon

STG341 — Proactively protect critical applications

COP307 — Track and visualize your AWS cost and usage KPI targets

SEC322 — Transform builder velocity with security

SUP302 — Troubleshooting from the perimeter

SUP312 — Deep dive into optimizing your use of AWS Trusted Advisor

COP308 — Hands-on experience with AWS observability services

NET305 — Network operations, management, and governance best practices

COP321 — How to manage hybrid resources with AWS Cloud Operations

WPS305 — Mitigate ransomware risk using AWS security controls

COP302 — Developing an observability strategy

CON308 — Reduce your operational and infrastructure costs with Amazon ECS

AIM331 — Optimize, secure, deploy, and monitor models at the edge

COP311 — Simplify continuous compliance and evidence collection with AWS

STP304 — Habits to reduce your cloud costs

SVS325 — Operating Kubernetes clusters at cloud scale

SUP305 — Hands-on AWS Support operational and resilience readiness

ANT316 — How to build dashboards for machine-generated data

PRT326 — Security incident monitoring, mitigation, and metrics using feature flags (sponsored by Datadog)

ARC325 — Well-Architected reliability: Best practices you can use today

SEC401 — AWS Identity and Access Management (IAM) policy evaluation in action

STG405 — Best practices for operating at scale with Amazon EBS and EBS snapshots

SEC402 — The anatomy of a ransomware event targeting data residing in Amazon S3

DOP404 — Proactive security and compliance for infrastructure-as-code resources

CON404 — Disaster recovery, high availability, and resiliency on Amazon EKS

SEC404 — A day in the life of a billion requests

CMP404 — AWS Nitro: Enhancing security and future-proofing your instances

OPN401 — Observing logs and traces with OpenSearch

CMP412 — Proactive auto scaling for optimal cost and availability

ANT403 — Event detection with Amazon MSK and Amazon Kinesis Data Analytics

CON405 — How to monitor and reduce your compute costs

Modernization — My stuff is good, but it can be better!

STG205 — Modernize your data archive with Amazon S3, featuring Stripe

SVS201 — Thinking serverless: From business problem to serverless solutions

CON202 — Containers and serverless: An application modernization journey

ANT205 — Achieving your modern data architecture

ENT208 — The journey of a billion messages: SQL Server on the cloud

CON202 — Containers and serverless: An application modernization journey

API202 — Decoupled microservices

PEX205 — Improving your solutions with AWS Partner technical validation

TNC218 — Evolution of a website: Going from single server to serverless

API204 — Model your business process with AWS Step Functions

ANT206 — What’s new in Amazon OpenSearch Service

ENT211 — Value of Blu Age automated refactoring with AWS Mainframe Modernization

ENT215 — Gain value from AWS Mainframe Modernization Replatform with Micro Focus

DAT217 — Modernize apps with purpose-built databases, featuring Liberty Mutual

CON208-L — Kubernetes virtually anywhere, for everyone

PRT265 — What to know before adopting Arm: Lessons learned at Datadog (sponsored by Datadog)

PRT222 — Why operationalizing data mesh is critical for operating in the cloud (sponsored by Capital One)

ARC206 — Reliable scalability: How Amazon.com scales in the cloud

ARC213 — Create a scalable mobile service for enterprise success

SVS205 — Thinking asynchronously: Integration patterns for microservices

COP207 — Moving from paying for what you use to paying for what you need

STP204 — Refactoring the product and engineering relationship

ENT207 — Unlock mainframes with AWS augmentation patterns

STP211-R — Scaling on AWS for your first 10 million users

ENT229 — MillerKnoll: Modernizing on AWS to move at the speed of business

ENT214 — Building and scaling a modernization strategy

CMP210 — Modern applications: An infrastructure perspective

ARC207 — Modern cloud applications: Do they lock you in?

ANT306 — Beyond monitoring: Observability with operational analytics data

BOA315 — Adopting microservices: Decompose, apply Strangler pattern, repeat

XNT305 — Modernize .NET Framework applications with AWS tools

SVS308 -AWS serverless developer experience: A day in the life of a developer

STG303 — AWS storage for containers and serverless applications

DOP303 — AI for DevOps: Modernizing your DevOps operations with AWS

CON301 — Amazon ECS blueprints: Modernize in minutes

API303 — Application integration patterns for microservices

SVS302 — Architecting secure serverless applications

BOA317 — Building containerized apps: From development to production

API306 — Building event-driven architectures

BOA314 — Decode user requirements to design well-architected applications

CON305 — Deploy .Net Core using AWS App Runner for web applications at scale

CON302 — Deploy containerized applications in a hybrid cloud environment

BOA306 — Designing and delivering cloud-optimized Java applications

SVS310 — From “server full” to serverless Java with AWS Lambda

TNC304 — How to speed up your AWS Lambda functions

SVS301 — Refactoring to serverless

BOA324 — Resilient and well-architected applications with chaos engineering

SVS309 — Securing serverless applications

BOA321 — Modernize and decouple your data model with change data capture

ANT301 — Democratizing your organization’s data analytics experience

API311 — Building next-gen applications with event-driven architectures

STG343 — Deep dive on accelerating HPC and ML with Amazon FSx

COP301 — Observability the open-source way

SEC329 — AWS security services for container threat detection

STG325 — Advanced data protection for your hybrid file storage

PRT330 — Key strategies to simplify your application journey (sponsored by Fortinet)

CON310 — Best practices for a container management platform

MKT306 — Build or transform to an AWS Well-Architected SaaS using AWS Control Tower

STP302 — Startup optimization: Tuning app performance for maximum efficiency

ENU304 — Modernizing HPC workloads using AWS services

CON313 — Migrating from Amazon EC2 to Amazon ECS for application modernization

CMP326 — The convergence of HPC and ML on AWS

API301 — Operational best practices for event-driven architectures

ENT312 — Modernizing your workload for speed and flexibility

EUC302 — No refactoring required: Turning legacy applications into SaaS

CMP318 — Scaling performance and lowering cost with the right choice of compute

FSI301 — Optimizing database resilience in a multi-Region universe

ENT319 — Achieve high availability and disaster recovery with SQL Server

CMP305 — Best practices for high performance computing in the cloud

FSI309 — Global Payments: From mainframes to microservices

CON307 — Protecting production with Amazon ECS security features

PRT310 — From strategy to delivery: Modernize your applications and cloud (sponsored by Kyndryl)

GHJ305-R1 — AWS Modernization & DevOps Jam

ENT301 — Babelfish: Efficiently modernize SQL Server to Amazon Aurora

ANT324 — Modernize your data warehouse

ENT317 — Automated refactoring of a mainframe application with AWS Blu Age

NET316 — APIs: Critical for data transfer, but how do you keep them secure?

WPS304 — Modernize your applications with the DoD DevSecOps approach

SUP308 — Optimize your AWS workloads with best-practice guidance

ENT324 — How Koch Industries accelerated application modernization

PRT316 — Ready, set, modernize: Accelerant for your applications and data (sponsored by Onica by Rackspace Technology)

SVS402 — Serverless stream processing with AWS Lambda, Amazon Kinesis & Kafka

XNT405 — Don’t overthink it: Identifying services for modernized workloads

SVS401 — Best practices for advanced serverless developers

SVS403 — Effectively using Java on serverless

BIZ401 — Build a resilient, scalable contact center on Amazon Connect

SVS401 — Best practices for advanced serverless developers

ARC402 — AWS Well-Architected Framework: Improve performance with caching

CMP410 — Framework for adopting AWS Graviton–based instances

XNT405 — Don’t overthink it: Identifying services for modernized workloads

SVS402 — Serverless stream processing with AWS Lambda, Amazon Kinesis & Kafka

CON408 — Deploy containerized web applications in minutes using AWS App Runner

Bonus Round — Sustainability Sessions

SUS203 — Carbon emissions reporting using modern data architecture on AWS

SUS207 — Patterns for obtaining insights from sustainability data

FSI205 — How Moody’s uses serverless and microservices for ESG scores

PEX201 — Building a sustainable practice for tomorrow

SUS209 — Optimizing architectures for sustainability

CMP204 — Build a cost-, energy-, and resource-efficient compute environment

SUS201 — Detecting deforestation with geospatial images and Amazon SageMaker

SUS208 — Utilizing sustainability data at scale

COM201 — Being ethical in tech: Sustainability tips for work and life

SUS203 -Carbon emissions reporting using modern data architecture on AWS

SUS206 — Sustainability and AWS silicon

SUS204 — Sustainability in AWS global infrastructure

STP213 — Scaling global carbon footprint management

SUS205 — Architecting sustainably and reducing your AWS carbon footprint

SUS302 — Accelerating decarbonization and sustainability transformation

CMP328 — Lower your IT carbon footprint with AWS compute services

Hope that you find this guide useful! For those who will attend the event in person, drop a message, meet you there! Feedbacks are encouraged!

TL;DR: How to massively certify people in AWS in your company.

As an AWS Ambassador and AWS Community Builder, part of my duty (and pleasure) is sharing nuggets of my experience with professionals interested in enhancing their capabilities.

I have worked for a company partnered with AWS since 2019, and today we detain the Advanced Partner Tier. The ambition is to evolve to the highest partnership level (Premier). To achieve this level, there are some prereqs like commercial opportunities launched, customer satisfaction review, technical validations/competencies (today we are one of 53 in a 100.000 partner ecosystem that detain the Financial Services Competency), and undoubtedly, people certified.

But Why is that important?

Certifications are a way to validate knowledge across professionals. Undoubtedly not the most important. It indicates that at least you dedicated time to see the contents and remembered on the day of the exam. It enables you to do different scenario analysis but do not assure you to solve the problem at first sight. It brings you more clarity to understand various challenges but does not bring an immediate answer to all of them,

Some customers and companies use the certification attestation as a prereq to hire services and people to work. You’re mistaken. I interviewed more than two hundred people in the past three years. I met all kinds of professionals, from those with 7+ certifications who had no depth in discussing real-life challenges to those with foundational certification and debated how to purge logs from complex structures to reduce cluster costs. Generally speaking, we want people with scars from previous battles that can contribute with respect, transparency, and will.

My four valid certifications are AWS Solutions Architect Professional, AWS Security Specialty, Solutions Architect Associate, and Cloud Practitioner. In the past, the Developer and Sysops Associate. But I must confess my endless meetings and presentations have taken more time than I planned, and I couldn’t revalidate them.

Pursuing the Premier tier and demonstrating our interest in AWS, we developed a task force to certify our professionals, upskilling them and raising our numbers in front of AWS.

THE PoC

We’re a 9000 professional company across 15 different countries. Mobilizing all of these people would be madness. So we found a way to start small, fail fast and create a repeatable model for other countries if they were interested. We used Brazil as the pilot light project.

With 3000 professionals and at least 50% of customers using AWS, we understood that is a good starting point.

In the past, we tried to certify people in Associate exams directly, but we took more time (almost five months) and low adherence (from 117, only 53 kept the studies, and 38 were successful). To make it different, we started from the bottom, even knowing it would take more time and investments.

Some respected instructors say that the AWS Cloud Practitioner exam (here called CCP) shouldn’t be the first certification regarding the depth of the questions and the time spent to pass.

I disagree and commit explaining some factors why I believe this should be the path:

-The CCP is the cheapest certification AWS has (100USD)

-it will enable 50% off your next exam (associate exams will cost 75 dollars instead 150, and professional/specialty will cost 150 instead 300USD).

-The exam will give the candidate comfort in understanding how it works, the dynamics of the exam (flag questions, return, finish the attempt), how to adjust the time box, and the behavior of the proctoring (if it’s online) and manage the adrenaline.

-It will increase the professional's confidence regarding certification exams. In my 20ish years of a tech career, I still have monsters that wake up before a certification exam. So why would it be different for those just lifting off?

-Preparation time is shorter, and results are simpler to measure by adjusting materials, instructor, and dynamics (fail fast, remember?)

-The professional will be bitten by the “certification bug” and will encourage the following steps (Associate, Professional, and Specialty).

The Materials

We rely on the material from AWS Skill Builder Portal. The materials are beneficial and straightforward. Some professionals understood that the materials did not touch some points touched by Stephane Maarek's course. So as complementary material, we recommend after the free training path, complete Maarek’s course.

AWS Partner — Accreditation Business
https://explore.skillbuilder.aws/learn/course/internal/view/elearning/2427/aws-partner-accreditation-business-digital

AWS Partner Accreditation — Technical
https://explore.skillbuilder.aws/learn/course/internal/view/elearning/1096/aws-partner-accreditation-technical

AWS Cloud Practitioner Essentials — Final Assessmenthttps://explore.skillbuilder.aws/learn/course/internal/view/elearning/3010/aws-partner-aws-cloud-practitioner-essentials

Stephane Maarek — Ultimate AWS Certified Cloud Practitioner — 2022
https://www.udemy.com/course/aws-certified-cloud-practitioner-new/

The Timeline

Once the goal was reaching the most considerable amount of people from all departments, we established one month to study and have live practices from sample questions to schedule the exam. We recommended two hours per day to have the chance to review all of the content and clarify possible doubts.

The Dynamics

We created a channel in our IM platform where everyone had access to materials and coworkers, tracking progress, solving doubts, and sharing experiences.

In the third week of the month, we started our practice exams instructor-led. Our finest Solutions Architects took turns to spend one hour each day answering and commenting on around 10 to 15 questions and interacting with 100+ people.

Those questions were previously inserted into forms platform for more significant interaction amongst the professionals and were released live to generate conversations and reach more people simultaneously.

The Result

More than happy to announce that we successfully certified 127 people in four months. This is the result of the effort and dedication of a committed team and each professional that dedicated their time to reach the goal. More than twenty thousand dollars were invested, more than 30 hours of video were generated, and repeatable formula to certify people was created. It doesn’t matter the country or the number of people. We learnt how to do it.

Lessons learned

During the process, we learned some important lessons that I share below:

-Make yourself clear, formalize communication and make it available to anyone in your company.

-Fast responses create engagement. Engagement brings more people and more people interested achieve great things.

-People want the different. The non-trivial. If you have a chance, have one different professional per day addressing doubts and the exact composition for practice exams week.

-Assure interaction. There are different profiles. There are introverts, talkers, and funny guys. To ensure everyone is working at the same pace, create ways to everyone interact, and the form with the ten questions of the day was our exit.

-Create rules and get attached to them. Do not open exceptions. Trust the process.

-Encourage the professionals approved to share and celebrate the goal.

-People fail all the time. For those who failed the exam, bring them closer. Spend more time, create specific agendas and wait 15 days. Do it again until you get it.

-Have fun.

Next Steps

Once presented with the certification first step, I aim to engage people to move further to other certifications and arouse their creativity and curiosity in different matters.

See you soon!

P.S. If you have any comments or doubts, please feel free on the comments box. Share is care!

So, once everything was set on AWS, I had the idea to use Amazon Connect. Creating the environment and integrating it with other AWS services like S3, Polly was innovative.

The idea was to create an Amazon Connect flow with fundamental interactions, validations on our user database, record everything, and process documents. Amazon Connect is already a great product, and its integrations with AWS products and third-party companies bring reliability and agility to the business. But the most significant driver was how to process documents and add intelligence with cutting-edge technology.

Amazon Connect: Connect is an easy-to-use omnichannel cloud contact center that helps you provide superior customer service at a lower cost.

Amazon Transcribe: Amazon Transcribe makes it easy for developers to add speech-to-text capabilities to their applications.

Amazon Comprehend: Amazon Comprehend is a natural-language processing (NLP) service that uses machine learning to uncover information in unstructured data.

Amazon Quicksight: Amazon QuickSight is a scalable, serverless, embeddable, machine learning-powered business intelligence (BI) service built for the cloud.

AWS Lambda: AWS Lambda is a serverless compute service that lets you run code without provisioning or managing servers, creating workload-aware cluster scaling logic, maintaining event integrations, or managing runtimes

AWS S3: Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance.

The description of High-Level Design follows:

1. Amazon Connect processes call.
2. The call ended, the recording is stored in an S3 bucket.
3. A lambda trigger invokes Amazon Transcribe API
4. After Transcribe process the document, the result is stored in another S3 bucket.
5. The stored transcribed document will invoke another Lambda that will call Amazon Comprehend API.
6. After Comprehend process, the document will store the results on a Data Store S3 bucket.
7. The results will be consumed by Amazon Quicksight dashboards that will give insights to enrich data on your site, reducing calls.

Needless to say that encryption, logging and monitoring must be put in place. From this HLD, the enhancements can run through the infinite. Things like NPS evaluation that could evolve into a gamification platform for the best problem-solvers, create ML models to drive the customer to the right choice without humans, a solid and detailed knowledge base…

Have fun!

“Mainframes are dead in the next years.”

Mainframes won’t die. Retail, Banking, Insurance, Government, and Airlines rely their operations on mainframes. And it won’t be different for the following years. Until those companies understand and unlock cloud superpowers to their systems, each tech professional’s responsibility is to integrate mainframes into new architectures and modern designs.

The primary motivators to modernize mainframes are:

• skills
• cost reduction
• flexibility
• agility
• innovation
• risk mitigation

All of those motivators are fair from a business perspective. Skill shortage is a fact. The appeal to learn Cobol is hugely smaller than others like Python, Java, and C#. Most of the professionals are aging, and new professionals want to know about modern platforms.

To meet the increasing demand around consumption on existing systems, MIPS needs to be the map to forecasts (believe me, it’s not cheap).

On the other hand, mainframes are solid blocks with fixed capacity that will lock money through less demanding year periods.

Accomplishing new business challenges on the mainframe is not easy, so the cloud is essential for this digital transformation. One example is this amazing 2018 re:invent session where HSBC presented a piece of work bonding mainframes and notification services through AWS using one of my favorite services (Kinesis). I was there, and still today, it’s impressive.

For those drivers, AWS present different strategies to modernize it. There are hardware emulation, a traditional lift and shift of workloads, indicated in mainframe shortage/decomission, middleware emulation taking advantage of API integrations, Automated refactoring using tools that will move Cobol to Java (automagically), repurchase to SaaS platforms and Manual rewrite. To know each one of those strategies in further detail, this great article brings more details of each.

Below is a graphic representation of what paths, average time and cost of each of the approaches.

That said, the mobilization for a modernizing journey is huge. The recommended approach is to create a business plan, but still a journey of some million dollars. To create confidence of C-level, there are some sweet spots to start, like mainframe backups.

A piece of experience: back in 2017, I was working for a large brokerage firm, and for audit reasons, we needed a backup of 4 years back. The Traditional Ops team requested the backup maintainer the tape with the backup. Then, the courier suffered an accident on an express route to our office, and a TRUCK ran over the motorcycle and destroyed the tape. The fine was high, and we weren’t able to present the data to regulators.

All companies need backups. They must be reliable, and the most important taking the narrative I gave: It must be accessible, reliable, and fast retrieval.

Beyond lines of code, we have databases. And those databases, even compressed, use a lot of space and time to be written.

Including costs must consider backup software, tape machines, the tapes or virtual appliances, and personnel to keep everything running. Long-term retention policies like accountant and tax (10 years) demand a high effort and different ways to maintain it. Some studies say that using LTO tapes and a good storage location is cheaper than moving to the cloud. But then we fall into agility, innovation, and risk mitigation. Not valid; try again.

In my research and experiences, I’ve reached Model9 (please sponsor me), an Israeli company with an exciting approach. Using zIIP mainframe processor, the agent compress and send data to AWS S3. AWS Direct Connect can make this connection due to data amounts or VPN (recommended for redundancy). All data will reside on S3, and its intelligence can make this burden incredibly cheap.

This approach can be the turning point for your company to pivot from mainframes to AWS. Costs will be reduced, and agility will increase. You’ll have 99.999999999% of durability and paying in the best case scenario 0.004 per GB / Month. Seems fair to use AWS and Model9 to lay your head on the pillow at night having all secured.

This approach will generate engagement from operations and certainly will draw the attention of C-level and financial teams to thrive the cloud journey, unleashing the most innovative ideas (remember that we can unlock a bunch of achievements).

References

• Padrões e melhores práticas para modernização do mainframe com a AWS | Amazon Web Services
• Habilitando a criação e implantação automatizada de código do mainframe para Instituições Financeiras utilizando os serviços AWS e soluções da Micro Focus | Amazon Web Services
• Como decompor um mainframe para microsserviços da AWS com a Blu Age | Amazon Web Services
• Desmistificando as opções de Migração do Legado para a AWS | Amazon Web Services
• Fast-Tracking Agility for Mainframe Workloads | Amazon Web Services
• Yes, You Should Modernize Your Mainframe with the Cloud | Amazon Web Services
• High-Performance Mainframe Workloads on AWS with Cloud-Native Heirloom | Amazon Web Services

Sugui Digest. SE01EP23 — Hiatus

Hello Everyone. Hope you´re safe. This episode is to say that is the season finale. For 22 weeks we had a weekly meeting where I share some of my experiences and some of my fears. Was good to be with you. But it´s time to have a break. Reorganize the purpose of this digest and use my time to focus in the challenges ahead (believe me, they´re huge). Sometime soon I´ll come here again to talk to with you, share some news and get along.

Until here, my most sincere thank you, with votes to you spend more time with your families, friends, beloved ones in general.

If you could, share what did you like most and what you dislike. This is important to the second season.

Keep safe and hope to see you soon!

Hello everyone! Hope you´re safe and sane. As I said last week, I needed a recharge, provided by my family and a weekend out of my regular diet. This week was rough as all have been essentially since one chinese had the great idea to eat a bat without cooking properly but it was easier with great feedbacks and some dreamings coming true. Sad but happy for a team member leaving, happy for some newcomers and happy overall.

This week the main theme of this digest is traditions. Yesterday I was remembering that each saturday morning, I´d used to go to one of my favourite bars around the world, Adega Gauchao placed in SBC. Every saturday, at 9AM I was there with friends, driking cachaça, beer and eating grilled meat, pork belly and kind of boteco food. Other tradition is the sunday pasta (with rotisserie chicken) that follow me up for almost 25 years with my parents interspersed with all-day barbecues. What are yours? Leave a comment, remember your good old-times and let me know what traditions you´re creating amidst this shit era we´re living to give you strenght and keep you moving forward!

If you support this digest, please share with your friends! See you next week!

Trailer of the week: 007 — No time to die

Docuseries of the week: Netflix High Score. For living all the history told, I got a sentimental bond with that. Six episodes, easy, fast, nice.

*IaC is mandatory to every architect, sysadmin or professionals moving their careers. My suggestion to all companies I´ve been talking is to adopt it from the root and do it with Terraform for a few reasons, but the main is curving learn to talk one language for multiple cloud providers, infrastructure, network and database. But there´s a few reasons to use Terragrunt (I ain´t saying) but must be considered.

Git of the week: Terragrunt

*Pregnancy is such a magic thing. My three nephews prove me that. But normally, first pregnancy test is made with the girl peeing on a pharmacy-test. That piece of plastic has so much power of processing than a XT286.

*Learning repeatedly is one of the most requiredof individuals nowadays. One of most famous Alvin Toffler quotes: “The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn. ” With that said, Find out a compilation of: 5 Best Cloud Computing Courses to learn in 2020, The Top 10 Programming Blogs in 2020 and The Top 16 Websites to Learn Programming in 2020.

*One of applications of High Processing Computing (HPC) is to create Monte Carlo Simulations. Using HPC you need to create a cluster, provision bids to use spot instances, configure batch, a repository to consume it to get the result. This is the traditional way. Tim Lou, PhD Bring to you a way to use this parallel simulations on BigQuery for free. If you have a PoC using Monte Carlo Simulations, this is the article you must read!

*Last week I talked about Neuralink, a chip implanted on human´s brain. Some scientists has defeated some of Neuralink achievements (natural). But check out the newest evolution of Neuralink on the video below.

*Undoubtedly podcasts has been part of my daily info basis. But with several subjects (comedy, tech, news, leadership, management, etc) sometimes I get lost to make it more productive. All of this to give you tips to organize your listenings. In my case I make it simple: use Spotify with playback speed at 2x normally listening every early morning during my walks or cycling.

*What´s the best Wireless headphone nowadays? Last week I´ve been cycling, one of headphones fall down on the street and a car ran over it. Lucky me that I was using my 20-dollar airdots. Certainly if it was a 250 dollar headphone I´d be pissed.

*I´ve been following the chess championships on Twitch since the pandemics started (shy, but week or other I just have a peek). Hikaru Nakamura is the star of this show and you can follow him on his channel that has streamed more the 9 MILLION chess hours. Certainly so much better than see teenagers calling theirselves as e-sportists playing League of Legends on TV.

*Over the past weeks the cloud lock-in subject has reached the stage again. Always, in every company, you have at least one tech lock-in. Move on, get a life. But if you don´t want to use (the most famous lock-in) AWS Lambda, or Azure Functions or GCP Cloud Functions, try Knative. Deploy your K8s, cluster, install Knative, install Istio, Knative Cli and deploy your functions, test and make your point. OR install your fav cloud provider SDK (or a few clicks on console) and get a life.

*Some people has been consulting me to be their development manager, which I´m honored and flattered. And in our meetings, I´ve always bring my experience (good and bad) to give a perspective of a north to them. This week in a coincidence I reached the 23 Alternative Career Paths that Software Developers Can Grow Into. I´d just change Software Developers to tech people.

*We´re advancing to the end of Google Next 2020. Last week the theme was App Modernization and as waited, massive Anthos, Istio, GKE and Mainframe Modernization. My highlights are: Cost optimization on Google Cloud, Anthos Deep Dive, Part 1 and Part 2, and obviously Mainframe Modernization.

*Google has released its 6 mo course that intend to replace colleges around the world for 300USD.

*At education, Microsoft has a great article to all tech careers ilustrated with relevant data regarding how technology can empower people.

*Talking in Microsoft, for the second year their compensation spreadsheet was revealed with some nice insights about career x money.

*Finally Brazil will have AWS billing in local currency, with taxes grouped in the same invoice. Changes start November 1st 2020 and you must change your tax settings on your payer account. For more info, visit the offical FAQ site.

*The AWS Cost Explorer has some interesting improvements over its APIs.

*For hands-on experience on AWS, visit the Awesome AWS Workshops. It has more than a 100 workshops in different subjects. Take a look and absolutely give a chance.

*For more convenient, easy and fast deployments, people sometimes use community images for their servers and containers. Needless to say it´s more than lazy, is dangerous. This is the main reason why you need to build your own images.

*Need a contact center with all functionalities of onprem deployments, all custom, with ML, NLP, automations, observability, auditable, fault-tolerant? AWS Connect can provide it to you and more. Check the blog post and some use of data include transcriptions of calls, NLP models over that trancript to understand for example the NPS of your product or company.

*AWS has some partners to Mainframe Modernization. Please check it out how BluAge move Cobol programs into Lambda functions on this Twitch video.

*Amazon CloudFront announces support for TLSv1.3 for viewer connections

*AWS X-Ray launches anomaly detection-based actionable insights in preview

*Save the date! September 29th the AWS Summit Americas lands virtually at 9AM BRT.

*For FSI strenght regulation, check this AWS blog post that shows how to create a flow to compliance demands for the industry.

TL;DR
A Deep Dive into Serverless Tracing with AWS X Ray & Lambda
Optimized shot-based encodes for 4K: Now streaming!
Develop and sell a Python API — from start to end tutorial

Sugui Digest. SE01EP21 — Exhaustion

Hope you enjoy this digest this week. Be safe. I´ll recharge my batteries this week with my family. Hope to see you next week! If you support this digest, please share and feel free to let you feedbacks at the comments session.

Git of the week: Troposphere

*Check out the opinion of Paula Piccard of the 10 Best Data Science Platforms.

*Centralized logging and audit is a pre-req for all companies and environments. This guide will show you how to Seamlessly Join a Linux Instance to AWS Directory Service for Microsoft Active Directory

*I´m not a soccer fanatic, but still a fan. Using the analogy of Santos F.C. believing in young talents, I´ll let here 4 reasons to invest in entry-level cloud talent.

*One more testimonial of How to pass the AWS Solutions Architect Associate exam.

*Not on architecture? Developer? Top 5 Online Courses to become AWS Certified Developer Associate in 2020. (check Jon Bonso material, high level).

*Amazon has launched Amazon Halo, a wristband with steroids! Certainly in my wishlist. Some of the features based on privacy has amused me. And clearly so much better than tacky iwatch. The Verge brings a great overview of this new solution.

*Pick a time to read the full report of FBI regarding a russian cyberattack to Tesla Gigafactory.

*Once again, Raspberry Pi is mentioned here in this tutorial for begginners. You should try.

*While at home or during endless calls, power up your glutes.

*Developers, please, read it. We´re not obligated to light up our crystall balls to understand what the hell you want with your code.

*Quick guide to overview what is AIOps and MLOps.

*Check it out why AgileData.io has chosen GCP as their infrastructure platform.

*Talking in GCP, check it out what happen this week on Next2020.

*Tensorflow vs Pytorch. Nuff said.

*Shame of the week: 350 MILLION records opened in a misconfigured S3.

*With all Data articles, dropped here, what are the best BI tools to consume all this?

*Starting in development now (like me?). Rookie Git mistakes you should avoid.ta

TL:DR
We Need A Blockchain Act for Every Country
My Week of Radical Transparency at a Chinese Business Seminar
The robot revolution has arrived
Microservices Adoption in 2020
Why People Can’t Stand Tech Journalists: An Interview With Casey Newton

Sugui Digest. SE01EP20 — anger

Hello everyone. Thank you to come with me at the 20th edition. Hope you´re great and most important: safe. This week we talk about cloud, security, space, career, data and coffee.

Anger is a feeling that is present (almost) every single day of my life. Since I was a kid struggling on my PE classes till my daily routine. Stupid questions, lies, endless pointless conversations, incompetence, nonsense, centralization, political views, news, covid, they´re all gasoline to my anger engine. It costs me more in the past, such like work positions (“how can you say if it does even have logs?”) to good old friends (“if you wanna be stupid to pick a side, pick hers and go f*ck yourself”). The important lessons here is what´s the balance of all that? You could be anger (I´d say that you deserve have anger) but you must understand that you always lose when you express your anger. Your limbic system needs only 6 seconds to you take the control again. So get mad (anger is a hell of a fuel, believe me) but count to 10, and then and go on.

Have a great week. If you support this digest, please share it and feel free to leave a comment.

This week, Deafheaven is the soundtrack with the album Sunbather. Highlight to opening track DreamHouse.

Comedy Show of the Week: Comedians in Cars Getting Coffee. Jerry Seinfeld bonds cars, coffee and comedians telling more what they think and some great stories. Last week I let the Bill Burr stand-up special and this week I reccommend the “Late Night Espresso” season and the episode “Bill Burr Smoking past the band”. In addition to everything I mentioned, this episode brings cigars and acidic comments. My mood this week.

Git of the week : tfsec

Git of the week (extra): Hedy

*Manage passwords is such a piece of work. I have some complex passwords but I must confess I´ve been letting Chrome manage some of them. For that, check this wired list of best password manager and do not forget to enable your MFA app-based (not SMS!).

*Starlink, SpaceX project to provide internet from satellites has its firsts tests. Considering the tech and how it work, it presented great results.

*I strongly recommend the Strategic Seventeen: NIST Cyber Security Framework from Logan Daley. Not just for security pros but for everyone who is involved to production systems.

*While we wait the Top Gun: Maverick debut, check this AlphaDogFight powered by AI (!)

*You should always check this 12 steps to assure your developers aren´t screwing your project.

*My driver license is suspended till the end of november due to 106 points (max 20) of my “adventures”. Most of them, for weekly rotation plate infractions and some for speed. Long story to admit my guiltyness. But a security researcher got a big problem doing some joke. He registered the plate “NULL” and now have more than 12 thousand dollars in tickets.

*When I was 18, I promised to myself that when I was 40 (my boss age at that time) I just wanted to be different from him, in many aspects. The way he faced the work, people, money and experience. Getting 40 soon, I´m sure that I´m whole different from him and way more happy. This is curious, to set a goal and work for that, and in more than 20 years, how things change. For that, this week Harvard Business Review dropped an article on How to Reimagine the Second Half of your career.

*Blue Origin has delivered to Nasa a Moon Lander prototype. If it works, I´d pay to send some people in this debut (even if it have some problems).

*I said repeatedly that AWS Kinesis might be my fav service of AWS. And we already discussed the SQS vs Kinesis, but never before Kinesis vs Kafka. In this detailed article with the benchmark we see Kafka wins in proposed scenarios, but the magic of cloud managed services comes with just a question: What the effort to put up running a high available kafka cluster, training people, manage connections, maintain it running 24x7? In Kinesis, I just setup an endpoint to development team and let them work.

*MultiCloud Agnosticity is bullshit. So, Should You Really Be so Worried about Cloud Lock-in?

*Great time of our weeks we´ve been connected to endless meetings, pointless presentations, an hour-long useless talks. Check this guy, who recorded himself to his meetings for a week.

*Rishab Kumar bring you notes to get certified in AWS. A great material to have base to entry-level and Associate certifications. Choose a cert, read the material, study, get certified, don´t bother me.

*True solutions architects must detain a set of skills and one of the more important is to understand the K8s x Serverless paradox. Both are great, but why use K8s instead serverless?

*An article regarding security on Wordpress. If you don´t want to read the whole article, you can have my top greatest security hint about it: do not use Wordpress.

*Upcoming next month, Microsoft Ignite, with their two-day virtual technical days. Let´s see what´s coming next (and may copies of some stuff).

*List of new AWS Hero is live. I suggest to follow them on social media, always good stuff.

*One of the things I´d like the most of my old job was after lunch take a cold brew in a Starbucks nearby. But after pandemics, things on the stores may be different negatively.

*Recently with some incitement I started to brew my coffee in other level, since the choose of grains, grinding, different ways to prepare and then, to drink it up. But Ratio took it too serious and bring the Ratio Eight Coffee Maker, evaluated by Wired.

TL;DR
Cloud Adoption in 2020
What is Data Science?
Business Data Science
The 3D-Printed Gun Isn’t Coming. It’s Already Here.
Zero to Jupyter with Docker on Amazon Web Services
From Analog to Digital and Back
Monumental Failure

Keep strong, be patient, count on me. The bear won´t win.