“I’ve hugged a lot of servers in my life, and believe me, they do not hug you back.”

Werner Vogels, Amazon CTO

Cloud Solutions
Strategic, experienced, technical.

Cloud Solutions
Strategic, experienced, technical.

Olikka’s 10 Steps to Amazon Web Services

Step 1. AWS Security and Governance


Getting security and governance sorted before you migrate your applications and data to the cloud is critical.  AWS Security and Governance is the first project in the Olikka 10 Steps to Cloud Program.

Through a mix of collaborative workshops and one on one meetings, we work through the detail of each of the below topics in relation to security and governance.

Step 2. AWS Design


With AWS Security and Governance sorted, it’s time to get started on the design of AWS.  A detailed, well thought out AWS design which is crucial to ensuring your AWS environment will address your business needs.

Step 3. Cost Management and Optimisation


Most organisations primary concern when moving to cloud is cost or ensuring costs don’t get out of control. Project 3 Cost Management and Optimisation focuses on implementing the right processes and tools to ensure you are in control of your costs, whilst also optimising costs by Right-Sizing servers and services where you can.


Step 4. Backup


Migrating your applications, servers and data to cloud requires a rethink of your backup strategy.  Typically, most organisations either choose to, extend their existing backup solution to AWS or implement a cloud native backup solution on AWS.

Step 5. Server Migration Analysis


Migrating to AWS is a lot more than simply lifting and shifting your current server fleet to AWS, every organisation should consider multiple factors such as:

  • Is this server relevant to migrate?
  • Do I need to migrate, or can I rebuild?
  • Should I or can I re-platform?

Step 6. VDI Review


Nearly every organisation has some form of VDI implementation, whether it is its Citrix XenApp or XenDesktop or VMware Horizon view.  Historically, these solutions have enabled your staff to access either a corporate desktop or application from any place at any time.  Typical design best practices also recommended placing VDI solutions close to backend applications or services they present or host.

Step 7. SQL Services


How do you address SQL or your enterprise database when migrating to AWS?  How will your current architecture and operational procedures be impacted?

These are common questions our customers ask us when it comes to migrating enterprise databases to AWS. There are so many different database choices in AWS today such as RDS which includes six database engines such as Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle, and Microsoft SQL Server. AWS also offers its NoSQL database service with single-digit millisecond latency named DynamoDB. It’s understandable why a lot of enterprises hold off on migrating SQL.

Step 8. DR as a Service


With all of your apps and servers moving to AWS, it’s most likely that your current DR solution needs to be reviewed, updated or even replaced.  A lot of today’s DR solutions include proprietary technology or are locally hosted.

Step 9. AWS Migration Cutover


Based on the results of Project 5 – Server Migration Analysis, we will migrate your servers to AWS, but not before optimising and right sizing them to suit cloud.

Olikka leverages AWS Server Migration Service to replicate live server volumes to AWS and create Amazon Machine Images(AMI). We create a customised replication schedule according to business application criticality and ensure there’s none or minimal business and network impact whilst doing so.

Step 10. On Premises Architecture


What do you do with what’s left?  You would be foolish to assume there will never be a need to have any services located onsite, so that means you need to have a plan to deal with them.