The process is quite simple. We meet, we analyse, we prioritise and we execute. You contact Cloudremote.io and we agree a virtual meeting where we gather information about the challenge at hand and agree where we should focus. Once we agree the period to use (typically 2-3 weeks), then Cloudremote.io will examine your AWS landscape and prepare the recommendations-backlog. Once we are done we will present the backlog to you and discuss prioritisation and how you want the items executed. The final part is that we, our large network of qualified AWS consultants or your IT team deliver on the recommendations.

Contact us: support@cloudremote.io

We pride ourselves in our screening process and ensuring we have certified professionals who have deep technical knowledge and experience in implementing AWS solutions in large enterprises. As this is our entry criteria, our consultants tend to be senior consultants who are used to navigating in large IT landscapes. We get the job done.

As we work remotely, we can utilise a global network of professional consultants. We start with consultants local to the client looking for a match to the task at hand, then look in the same timezone as the client and finally globally. We are more interested in getting the correct resource that can solve the task at hand, than staying local.

With our detailed technical description of each backlog item it makes it easier to match with an experienced professional.

CloudWare is suite of methodologies, best practices and tools that we use to investigate an AWS infrastructure and create a recommendations-backlog. CloudWare allows us to focus on a specific area of an IT landscape and propose optimisations to our clients. By using CloudWare, we can focus our efforts and advise accordingly. See CloudWare for details.

No. We require a read-only policy attached to a role which we can assume, that allows us to analyse your infrastructure. Once we need to implement the backlog items, more access will be required, but initially we just require read-only access. We will provide the instructions for adding the policy to a role manually or using a public CloudFormation template. You can review the access given and revoke it at any time.

Once we get access to your AWS accounts and understand what you have and what you want to improve, we will create a recommendations-backlog. This is effectively a list of detailed items with proposals for improvements. It will be possible to give some of the items to your own IT staff so that they also join in implementing the backlog items. Each item will be detailed with the suggested implementation and with estimates and detailed technical proposals.

We try to get as much information as possible in the first meeting, so we are clear about the priorities. There will be a need to get answers to questions during the analysis. We usually do this by having a chat channel open where we can chat with relevant resources and get answers to our queries. We can agree at the first meeting how we will do this in practice, including when we can and can not disturb your resources.

Once we have the recommendations-backlog ready we will present it at a virtual meeting. Each item will be detailed and estimated so that it will be possible for you to see how long it will take to implement. It should be noted that this is an estimation for CloudRemote.io resources to implement and not necessarily the same if you decide to implement yourself.

You prioritise the items and we will support with technical advise about dependencies and other considerations needed in connection with prioritisation.

Depending on the estimation and the speed at which you need to implement the recommendation items, CloudRemote.io will gather a team and submit a proposal for the implementation containing main objectives, scope, schedule, ways of working, assumptions, deliverables and price. You will need to approve before any work is initiated.

Send an email to invoice@cloudremote.io