diff --git a/docs/billing/howto.mdx b/docs/billing/howto.mdx new file mode 100644 index 000000000..19660a95b --- /dev/null +++ b/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. diff --git a/docs/provider/awsprovider/aws-aws-key.mdx b/docs/provider/awsprovider/aws-aws-key.mdx deleted file mode 100644 index 102ddfdc0..000000000 --- a/docs/provider/awsprovider/aws-aws-key.mdx +++ /dev/null @@ -1,168 +0,0 @@ ---- -sidebar_label: AWS Keys ---- - - -import Zoom from "react-medium-image-zoom"; -import "react-medium-image-zoom/dist/styles.css"; -import { FiExternalLink } from "react-icons/fi"; - -# Getting AWS keys - -To use Sleakops, you need to provide an access key, and a secret key in the [Provider](/provider/index.mdx) creation page, -which you must obtain from the [AWS console page ](https://aws.amazon.com/console/). -These are used to make programmatic calls to the AWS API. - -## How to obtain an access key from the Console - -Root user access keys provide unrestricted access to your entire AWS account. -As Sleakops needs long-term access keys, we recommend creating a new IAM user and generating access keys for that user instead. -This is also a practice recommended by AWS. - -In this tutorial, an AWS account named **sleakops_user** was created. - -### Create an IAM user with programmatic access - -Enter the console as usual with the email and password you set for your root account. - - - AWS console main page - - -Then search for the IAM service. - - - Search the IAM service - - -Next, go to the Users section. - - - IAM management page - - -Click on Add User button. - - - IAM user page, with an arrow pointing to the button - - -Once inside the Add User stepper, give the user a name meaningful to your use case. -Also, check the button Access Key - Programmatic access. If you wish to enter the -AWS console with this user you should check that button as well. - - - First step for creating a user. - - -Go to the Attach Existing policies directly and give the user the AdministratorAccess -policy which allows access to manage all resources. -This policy gives SleakOps access to deploy all the infrastructure needed. -Review other pages of this documentation to learn more about the AWS resources we create for you. - - - Second step for creating a user. - - -If you wish you may add tags to the user. -Tags give plenty of help in organizing the resources that are created. -SleakOps make use of tags for every resource. - - - Third step for creating a user. - - -Review the details before creating the user. -When you feel that everything is ok, click on Add User - - - Fourth step for creating a user. - - -The user was successfully created, and the credentials Sleakops needs are shown and -should be introduced directly on the Provider creation page. Remember that the secret -key is only shown once, if you miss it you will need to create another pair and delete -this one. Further information on that issue will be presented in the next section. - - - Fifth step for creating a user. - - -## How to manage access keys - -Whether you created an IAM user or using the root account (not recommended), you might manage your keys following this section -Once inside the AWS console main page. Click on your username. - - - step to manage access keys. - - -Then go to security credentials. - - - step to manage access keys. - - -Enter the Access keys (access key ID and secret access key) section, where you should -see your keys if any. From here you might deactivate keys, delete them or create -new ones. - - - step to manage access keys. - - -If you need a new key click on Create new access key button. - - - step to manage access keys. - - -You successfully created the keys needed to use on the Provider creation page. -As noted on the AWS console, up to two access keys might exists at a time. -If you need more providers you might need to repeat these steps by creating more IAM users. - - - step to manage access keys. - diff --git a/docs/provider/awsprovider/index.mdx b/docs/provider/awsprovider/index.mdx index 6f2ce10bc..ffca7ce56 100644 --- a/docs/provider/awsprovider/index.mdx +++ b/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).