Here at C2S Consulting Group, we have helped many customers adopt and migrate their applications into the cloud and promote how important it is to having a strategy and starting with best practices which will save you a lot of time, money, and heartache. There is a lot to learn and some pitfalls to avoid in order to make sure you lower the Total Cost of Ownership (TCO) when migrating from on-premises to the cloud. Here are the top five:
- Running your apps exactly the same way you would run them on-premises
When adopting cloud and moving from physical infrastructure to cloud many customers tend to think everything will run the same, except the way you provision instances. This is the wrong mindset and can have costly consequences. Since cloud platforms generally have pay-as-you-go models, it is imperative to evaluate your current applications to see what can be optimized and improved in the cloud. Right sizing, monitoring, and properly managing your cloud infrastructure is key to be successful in cloud adoption. A cloud strategy is imperative which can lead to re-architecting your applications and new policies and procedures for management and operations once moved over. The change is pretty significant in the cloud compared to traditional IT.
- Not having governance early in the process
Governance is very important to establish basic processes and policies. This is important to make sure the transition to the cloud and the plan is understood by all parties. An example of this is proper tagging policies in AWS. Doing this upfront is important to track spending and cloud usage. If this isn’t done at the beginning, it is difficult to find and track unrealized costs and cloud usage. AWS provides tools to create, manage, and enforce these policies in the lifecycle of your applications such as services like Config and Lambda. There are also 3rd party tools that are available to do this as well.
- Not utilizing the pay-as-you-go model
Once in the cloud, not as many people as you think, take advantage of tools such as auto-scaling and/or scheduled scaling. This services are extremely important to use for applications that need to scale up and down generally triggered by time, resource usage, and events. This lowers your TCO and keeps you from over-provisioning your applications and saves you money!
- Not cleaning up your resources
Lack of monitoring your cloud environment leads to unused resources staying on or active, costing the account owner additional costs. This pitfall is pretty clear, but happens a lot, especially in development environments. The key is to be cognizant of what resources you are using and which ones you’re not.
- Not embracing the DevOps movement
Cloud enables businesses to easily integrate DevOps best practices such as: automation, configuration, backups, deployments, and recovery. Doing this early in the process, will make administrators and developer’s lives a lot easier in keeping the system running smoothly, secure, and updated. This is vital when scaling out large, enterprise systems in the cloud.
Let us help you determine what strategy is the right fit for your company. To discuss with one of our architects please contact us at: email@example.com.