Why can happen so easy ?
Today people trens to have an higher sense or urgency and far to became a bad aspect can’t be the only orientation otherwise will guide to a dead end. This post will describe what I normally listen in practice and provide some tips on how to avoid in your deployment cloud dead ends.
Like virtualization launch cloud resource is easy. However control in the next phase with no proper plan is not the same thing even having tools.
Planing is the key
Know the objective. Conduct and guide the journey will be safe in mid long term big potential problems, blockers, lack of visibility.Cloud Solution Providers independent of services must follow a minimum guide lines.
Today of course, any head of IT will invest and look in details the following two major topics:
- Security
- Costs
- Availability
Both aspects are strong related with governance prior launch the service or any service. All Cloud Service Providers invested heavily in these areas and all of them implemented solutions that have minimum interoperability’s in some areas like authentication, but other aspects are very particular.
Know or even master one of them will not ensure a success deployment at any other.
Architect focus creating base lines on how must be done otherwise what must have will add extra times in the discussions and some frustrations.
Design the architecture considering the hard lines of “as-is” will also add three aspects:
- Lack of supportability, gray areas, unsupported scenarios
- Close the eyes for benefits of cloud economics
- Close the eye for the benefits of the specific Cloud Solution Provider
Tips
Here we have the tips to avoid common dead ends in future. First evaluate change the posture to consider:
- Be closer to Cloud Providers that invest more in patterns, guides and practices
- Ask more question and deep dive on Cloud Economics of the specific provider this will expand the investment
- There is more than one solution to accomplish the same result. Reevaluate if is adequate to our workload
- Services has lifecycle, from start to beginning to adopt the technology of your choice to manage, evaluate more than one, plan at scale and add security will simplify a lot in mid long terms.
- Never, allow unrestrictive access open, protect the people be fair adopt a minimum-security posture and continuity plan.
- Don’t use Cloud Service Provider SLA to direct define our service uptime define and use the cloud provider constructs like zones, regions. More than one when make sense using global load balancers and replications.
- Remember the data is ours, be proactive!
Enjoy!