Agile management with the CMDB

Hello! Nice to see you again! We hope that you are eager to try our Console if you have not put your hands on it yet!

We know that managing an IT infrastructure can become sometimes a hard task, which steals hours and resources, so we thought that we could give you a hand by providing an easy way to organize all your business information within just a few clicks and tabs. That’s what the CMDB application of the Rocket-Steam Console is for.

This application allows you to classify your AWS EC2 resources, complementing AWS information (like instance id, AMI id, size, status or network information) with your business logic data, such as the productive status, the project it belongs to, what software has been installed or who is responsible for managing that instance.

The database is synchronized automatically with Amazon every few minutes to keep the data as up to date as possible, and the powerful search engine will provide the information you were searching for within the blink of an eye.

cmdbb

You may have noticed in the prior capture that in the main screen of the CMDB the columns for hostname and domain are empty. This is because AWS does not provide this information by default. For AWS ready applications this information is not really important, but for enterprise systems that get migrated to the cloud, it is.

Double click on any of the EC2 instances shown, and its data sheet will appear:

FirstSteps_13

Some fields are taken automatically from AWS Tags, like Project and Description, but the others are blank for you to fill.

You will find three main sections.

1 – General

Here we have basic information regarding the usage of the EC2 instance.

1.1 – Information

  • Productive Status:
    Is the status of the instance regarding production, for instance some status could be:

    • Move to production: means that the instance is getting ready for production, but it is still not giving service to end users.
    • In production: means that the instance is running a service being used by end-users.
    • Test: instance is being used for testing purposes.
    • Development: instance is being used for testing purposes.
  • Hostname: the hostname of the EC2 instance.
  • Domain: the domain of the EC2 instance.
  • Description: a short description of the instance and its services.
  • Assigned Profile: the Scheduler profile that is assigned to this instance, if any, and a brief summary of its start and stop time rules. More on this topic will be explained in the Scheduler article.

1.2 – Responsibles

Here we can specify people within our organization which is responsible for the instance or the applications running in it:

  • You can add and manage your staff with the “Manage Staff” button and add it to the instances with the Add Responsible button.

FirstSteps_14

1.3 – Support teams

On this tab you can indicate different teams supporting the instance and/or the applications running inside. It works like the responsible teams.

FirstSteps_15

2 – Network

Here you get a list of all the subnets and interfaces related to the EC2 instance.

FirstSteps_16

3 – Software

Here you can specify the applications installed on your system, and its function, so you can find an instance for its installed application.

FirstSteps_17

And that’s it! Now you know how to categorize your instances and provide important business information through the Rocket Steam Console!

Help your company understand how your resources are distributed in systems and applications, and who to contact whenever there is an issue or keep track of the instances organized by VPC’s and subnets.

Of course, you can just leave the CMDB alone and enjoy the other applications inside the Console; it’s a matter of needs.

We’ll be glad to hear about you while you’re using the Console, feel free to contact us!

About Mari Ángeles Izquierdo