Whitepaper 'FinOps y gestión de costes para Kubernetes'
Considere darle a OptScale un Estrella en GitHub, es 100% de código abierto. Aumentaría su visibilidad ante los demás y aceleraría el desarrollo de productos. ¡Gracias!
Ebook 'De FinOps a estrategias comprobadas de gestión y optimización de costos en la nube'
OptScale FinOps
OptScale - FinOps
Descripción general de FinOps
Optimización de costos:
AWS
MS Azure
Nube de Google
Alibaba Cloud
Kubernetes
MLOps
OptScale - MLOps
Perfiles de ML/IA
Optimización de ML/IA
Perfilado de Big Data
PRECIOS DE ESCALA OPTICA
cloud migration
Acura: migración a la nube
Descripción general
Cambio de plataforma de la base de datos
Migración a:
AWS
MS Azure
Nube de Google
Alibaba Cloud
VMware
OpenStack
KVM
Nube pública
Migración desde:
En la premisa
disaster recovery
Acura: recuperación ante desastres y respaldo en la nube
Descripción general
Migración a:
AWS
MS Azure
Nube de Google
Alibaba Cloud
VMware
OpenStack
KVM

How to reduce your
cloud bill yourself

Preparing a detailed article about cloud cost optimization scenarios I decided not to wait for another month or so and share a few steps you can easily implement now to save some cash. Some of them are simple and obvious, but some are not.

First of all, you need to clearly understand that implementing some of these scenarios will require you to remove resources so you should understand what you do, and what consequences will follow. I just give some instruments, but it’s up to you to use them properly.

Please remember that you need to check and implement the steps for all the cloud regions in your account.

How-to-reduce-your-cloud-bill-yourself-article

So, let’s start, top 5 steps you can take

Paso 1

List all the stopped instances in your account. Filter the ones that are stopped longer than some period (one or three months etc.), think if they are still needed and remove them otherwise.

Here are some AWS SDK queries to get list of stopped instances:

How to reduce your cloud bill yourself article image

Paso 2

List all the unattached volumes and snapshots not used for any of the machines. Remove the unused.

Paso 3

Clean up your S3 buckets. I’ve never seen an account (including ours at Hystax) without some thrash files and objects, duplicates, etc. If you need something, keep it in S3 or move into Glacier to save money.

Paso 4

Identify unused IAM users and list their resources. There is a high probability of getting some of unnecessary cloud resources left when people quit. Think whether you still need them.

Step 5

Check whether you have cross-region traffic and, if yes, think if you really need it. It’s one of the top cloud expenses, but people actually forget about it. If there is no reasonable cause to stay in different regions, consolidate resources under one region.

And TAG, TAG, TAG your resources. Or, at least, have a proper naming policy. It’s common when every engineer names resources as he or she wants, and later it’s impossible to identify an owner.

Please, feel free to read my recent article ‘Cost projection to reduce cloud costs’ aquí.

Noticias e informes

Descubra el potencial de adopción de FinOps de su empresa

Una descripción completa de Hystax OptScale como plataforma de habilitación de FinOps: características, beneficios y funcionalidad del producto.

Informe de uso de la nube pública

Excelentes conocimientos críticos sobre los puntos de referencia, las tendencias y las mejores prácticas de gestión de la nube híbrida.

Optimice su uso de la nube con Hystax OptScale

Descubra cómo analizar las métricas de la nube y obtener recomendaciones de optimización de la nube en función de su uso.