AWS lança programa Guardiões do Japi focado em segurança hídrica
A Amazon Web Services (AWS) anunciou o lançamento do programa Guardiões do Japi, iniciativa ambiental que reúne inteligência de dados, educação e preservação da natureza na Serra do Japi, São Paulo. O anúncio foi feito nessa quinta-feira (3) durante o AWS Summit São Paulo.
A Amazon Web Services (AWS) anunciou o lançamento do programa Guardiões do Japi, iniciativa ambiental que reúne inteligência de dados, educação e preservação da natureza na Serra do Japi, São Paulo. O anúncio foi feito nessa quinta-feira (3) durante o AWS Summit São Paulo.
Em contexto
- Tema: Cloud y Arquitectura — Nube pública, híbrida, costos y decisiones de infraestructura.
- Fonte: IT Forum
- Publicado: 05/09/2026
Continuar lendo na fonte original →
Trecho publicado automaticamente pelo radar do site. O texto completo pertence ao veículo e está vinculado acima.
Why it matters
After a few years, nearly every organisation that migrated discovers the same thing: the bill grows faster than the business. Not because the cloud is expensive, but because nobody switches off what is no longer used and nobody has the incentive to check.
What I look at in these announcements is portability. The more comfortable a platform is, the harder it usually is to leave, and that comfort gets paid for in negotiating power three years later, exactly when renewal comes up and there is no credible alternative left.
What usually goes wrong
What I see fail most is the literal migration. The system gets moved exactly as it was, nothing redesigned, and you end up paying hourly for what used to be paid once. It works the same, costs more, and two years later somebody asks why it was done. Lift and shift is not modernising.
What to watch
- What happens when the provider has an outage, because it will, and what keeps running meanwhile.
- Three-year total cost with real growth, not the first-year promotion.
- How hard it would be to leave or move a piece to another provider, which is future negotiating power.
How I read this entry
What I would install alongside any move to the cloud is the discipline of switching things off. Tag everything by owner, review monthly what is running unused, and give somebody the authority to turn it off. Without that, waste eats the promised savings within two years.
The original story is published in another language; the excerpt is quoted as the publisher delivers it and the commentary is written in English.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
