WIP: clean unused doc and added doc about billing and lambda cost all…

docs/billing/howto.mdx

@@ -0,0 +1,20 @@
+---
+sidebar_label: How to calculate the billing ? 
+sidebar_position: 0
+---
+
+
+Usamos cost allocation tags para todos los recursos que son generados desde sleakops, para poder categorizarlos y relacionar los recursos dentro de AWS con las entidades que maneja Sleakops. 
+
+Podes ver todos los costos extras, como son el uso de la API de cloudwatch, o crear algun otro recurso por fuera de sleakops como apartado "otros" dentro de la pantalla billing en Sleakops 
+
+## Cost allocation tags:
+
+Para poder usar estos tags, es necesario activarlos previamente. Esto se hace en la cuenta root del cliente. 
+Para que estos tags se puedan usar como tags de costos, se debe esperar al menos 24hs despues de asignar el tag a algun recurso. 
+Por esto, desde sleakops, cuando integramos el provider. Dejamos una lambda dentro de la cuenta root con el proposito de activar estos tags. 
+Esta lambda intenta 3 veces, sino puede la lambda se elimina y la responsabilidad queda del lado del cliente. 
+
+
+#### ¿ Que pasa sino se activan esos tags? 
+La infra va a seguir funcionando. No podrias ver los costos de tu infra estructura dentro de sleakops. 

docs/provider/awsprovider/index.mdx

@@ -7,7 +7,12 @@ import TabItem from '@theme/TabItem';
 
 ## Provider Creation
 
-To begin the installation of your application, we first need to connect to your AWS Management account. This is accomplished by creating a special access rule within your IAM Roles in your main account, which we'll name "SleakopsIntegrationRole." This role will enable us to access the resources required from our system, thereby facilitating a quicker and smoother installation process across all 4 accounts (Production, Development, Management, and Security). Upon completion of the installation, we'll promptly remove this access rule from your main account, ensuring that everything remains safe and secure for our clients.
+To begin the installation of your application, we first need to connect to your AWS Management account. 
+This is accomplished by creating a special access rule within your IAM Roles in your main account, which we'll name "SleakopsIntegrationRole." 
+This role will enable us to access the resources required from our system, thereby facilitating a quicker and smoother installation process across all 4 accounts (Production, Development, Management, and Security). 
+Upon completion of the installation, we'll promptly remove this access rule from your main account, ensuring that everything remains safe and secure for our clients.
+
+Agregar aca que le instalamos una lambda al cliente para activar los  [costs allocation tags](/billing#Cost-allocation-tags).
 
 <Zoom>
 <img