Most IT leaders today face a growing set of challenges related to managing an evolving IT infrastructure, and delivering IT-as-a-Service (ITaaS). The management and integration of private and public cloud infrastructures can become a mixed bag where multiple tools can lead to inefficiencies and be prone to increased costs.
To maximize your investment, benefits and the agility of cloud computing, it’s important to invest in a Cloud Management Platform (CMP) that is designed for cloud governance and has methods in place to optimize costs across different infrastructures.
Below are six best practices to improve your cloud governance, while reducing public cloud and private infrastructure costs:
- Control Reserved Instance purchase recommendations. Controlling the instance types your developers can use keeps the number of instance types down to a manageable minimum, allowing you to gain economies of scale and more fully take advantage of Reserved Instance purchases. Look for a CMP with the capability to provide extensive flexibility across your various service offerings, while still enforcing instance type consistency and governance.
- Enforce policy-based AWS tags. Public cloud enforcement best practices ensure your AWS instances have appropriate tags, guaranteeing your instances have been assigned the metadata important for your organization and are being properly tracked.
- Drive power scheduling. AWS tags help drive power scheduling recommendations so dev/test workloads are powered off during non-prime hours, ensuring you don’t pay for inactive resources. A flexible CMP will enable you to make policy enforcements as strict or lenient as you like. For instance, you can choose to either report on those instances not following your corporate AWS tagging rules, or be more restrictive and ensure they are always powered off or even run custom workflows that can perform any task you’d like upon detection of an offending instance.
- Obtain a consolidated cost view across private and public cloud consumption. In many organizations, public cloud consumption started in one or more pockets of engineering teams. Eventually, these application workloads will need to be properly managed just like your private cloud assets. They require inventory management, patching, backup, DR and sprawl prevention to name just a few. Look for a solution that will give you visibility to both your private and public cloud assets, providing that single pane-of-glass required to properly manage your hybrid cloud infrastructure.
- Compare real private/public cloud costs. Public clouds are an important part of your hybrid cloud strategy – they’re powerful, scalable and highly available. They can also be very expensive; it’s possible to get a surprise bill at the end of the month that’s several times more than you planned for. Be sure you have a cloud cost comparison tool in place so you can determine where workloads are best suited to run.
- Use automated lifecycle decommissioning processes for short-term instances. Many public cloud application workloads are deployed by engineering teams for short-term use, but then languish and continue to run (in some cases indefinitely) because there is no lifecycle monitoring or enforcement. Leverage a CMP that enables you to fully automate a lifecycle decommissioning process, and easily target only those areas of public cloud consumption that are specific to R&D (such as accounts, regions or VPCs).
Despite their benefits, hybrid cloud environments can be difficult to manage. As new cloud services emerge to meet specific business needs, they create organizational and operational inefficiencies, making it critical for technology leaders to make informed decisions about which products, services and payment models deliver the best results. By following the best practices outlined above, you’ll achieve the proper level of control while enabling engineering teams the freedom to consume public cloud resources as they are needed.
For more on hybrid cloud governance, check out the replay of our latest webinar.