Now that you’ve reached the end of your new connectivity route and started to deploy cloud generation technology, you will want to manage this environment.
Management of the cloud is arguably more important than on-premise management. The reason is that you – the customer – now gets to utilise an architecture that is dispersed, covers multiple geographies, has ‘soft edges’, is difficult to contain, runs on multiple cloud platforms, and is all supplied by different vendors.
In our previous article, we discussed the management considerations for connectivity and product choice/solutions when moving from an on-premise world into the cloud. So, if a customer is now enjoying all the ‘new’ aspects that the cloud delivers, why do they manage this brand-new environment with an on-premise mentality?
A fairly simple answer to this is that early management options in the cloud arrived in the form of familiar on-premise solutions. SIEM tools are an intricate part of data centre management posture, and so it seemed like a great idea to copy that posture to the cloud. However, to get the best out of the architectures that cloud providers offer, they need to evolve. Why, I hear you ask?
The fundamental answer to this is that the architecture of a cloud configuration is very different to that of the ones we are used to seeing in the data centres around the world. Therefore, the management of the cloud needs to follow suit.
On-premise solutions are contained, whereas cloud is not. On-premise architectures don’t need to consider internal bandwidth charges or worry about placing agents in every corner of their data centre. Both of these are, however, important considerations in the cloud. On-premise management tools have the luxury of sitting outside the fences, calling in, and demanding every last scrap of data (in the form of large log files from

View Entire Article on