Cloud · AWS consulting
AWS consulting partner in Saudi Arabia: migration, EKS, monitoring and cost, from one team
Interkey is an AWS partner and works as an AWS consulting partner for organisations in Saudi Arabia. The work is the programme around the platform: deciding where each workload should run, building the landing zone, migrating in dependency order, running Kubernetes on Amazon EKS, monitoring with Datadog and reviewing the bill every month. One engineering team in Riyadh does all of it, in Arabic and English, so the people who design your AWS estate are the people who operate it afterwards.
In short
- Who: Interkey, an AWS partner, with its engineering team in Riyadh.
- What: assessment and placement, landing zone, AWS migration services, Kubernetes on Amazon EKS, Datadog monitoring, AWS cost optimisation reviews and operation after go-live.
- What decides placement: the classification of each workload's data, not a preference for a provider.
- Pricing: per scope, with AWS consumption shown separately.
At a glance: what Interkey does on AWS
The usual parts of an AWS programme. A first engagement is often one or two rows; the assessment decides which.
| Service | What you get | When it fits |
|---|---|---|
| Assessment and placement | A placement decision and a reason for every application, including those that stay | Before any migration |
| Landing zone as code | Accounts, identity, network and guardrails that can be rebuilt and extended to a second Region | Before the first workload, or when the current one was built by hand |
| AWS migration services | Rehost, replatform or rewrite decided per workload, moved in dependency order | A data-centre exit or an estate worth modernising |
| Kubernetes on Amazon EKS | Cluster design, upgrades with rehearsed rollback, capacity and admission policy | Containers whose data may run in an AWS Region |
| Monitoring with Datadog | AWS accounts connected, alerts tuned, licences supplied | Production on AWS without one view of it |
| AWS cost optimisation | A monthly review of idle resources, sizing, tagging and commitments | A bill growing faster than the business |
| Operation after go-live | Patching, capacity, identity hygiene and a monthly report, on an agreed scope | When your team cannot staff the platform for years |
What an AWS consulting partner in Saudi Arabia should do
AWS runs the Regions, the hardware and its managed services. It does not decide which of your applications may leave the Kingdom, design the account structure your teams will live in, or check that last night's backup restores. That layer is the work an AWS consulting partner is brought in to do.
In Saudi Arabia the work starts with the data. Some classes can sit in a Region outside the Kingdom, some need in-Kingdom infrastructure, and some may not leave systems you operate. Those answers differ between applications in the same estate, so a useful partner settles them workload by workload before recommending an architecture.
Read more
Interkey works on AWS alongside in-Kingdom hosting and your own data centre, because the classification decides the target.
Questions to ask any AWS consulting partner
Whichever supplier you choose, these questions separate a programme from a hosting quote:
- Will every application get a placement decision and a reason, including the ones that stay?
- Is the landing zone delivered as code that our team can read and change?
- How is the cut-over for each workload agreed with its owner, and when is the old system switched off?
- Who operates the estate after go-live, and what does the handover include if that changes?
- Are AWS consumption and licences shown apart from the partner's own work?
AWS Saudi Region readiness
AWS has announced its first infrastructure Region in the Kingdom and says it is on track to launch in December 2026. On 2 November 2026 it was not yet in AWS's list of available Regions. Until it is live, AWS's Middle East Regions are in Bahrain and the UAE.
Readiness is work you can do now, so each move can start once the services it needs are there:
Read more
- Classify the workloads held back by their data, and list the AWS services each one uses.
- Write the landing zone as code, so extending it to a new Region is a change you can review and test.
- Plan each move as a migration: a cut-over, a data transfer and a period of running in two places.
The full status and a placement worksheet are on AWS in Saudi Arabia, updated when the Region goes live.
RelatedAWS in Saudi Arabia
AWS migration services: one decision per workload
A migration is not one decision. It is one decision per application, and programmes go badly when one answer is applied to the whole estate. For each workload the assessment chooses one of five answers: leave it, retire it, rehost it, replatform it onto managed services, or rewrite it.
The move runs in dependency order, and the old environment stays available until the new one is proven. A migrated application is done when it is monitored, supported and the old one is switched off. Our cloud migration practice sets out the phases and the costs first estimates miss, and applications moving to containers follow the Kubernetes migration path.
Relatedcloud migration practice
Kubernetes on Amazon EKS
Amazon EKS takes the Kubernetes control plane off your hands. It still leaves you the node groups, version upgrades, add-ons, policies and the cost of what runs on the cluster. Interkey designs the cluster for its workloads and operates the platform layer: upgrades with a rehearsed rollback, node capacity, admission policy, image hygiene and platform incidents. Your applications and their releases stay with your teams unless an agreement says otherwise.
EKS fits when the data on the cluster may run in an AWS Region. Where residency rules keep a workload in the Kingdom, the cluster is self-managed on infrastructure there, and Interkey operates it the same way.
Monitoring and AWS cost optimisation
Monitoring AWS with Datadog
Datadog reads CloudWatch through its AWS integration and puts it next to host, container, trace and log data from the Datadog Agent, so EC2, EKS, Lambda, RDS and S3 can be read on one screen. Interkey sells Datadog licences in Saudi Arabia, connects your AWS accounts, tunes dashboards and alerts so each alert reaches the team that can act, and provides technical support from Riyadh. Monitoring is set up during the migration, not after it. See AWS monitoring with Datadog for what it covers service by service.
Read more
AWS cost optimisation reviews
AWS bills rarely grow because of price. They grow because of an environment nobody switched off, storage never tiered, data crossing a boundary that charges for it, or capacity sized for launch and never revisited.
The monthly cost review finds these items, names an owner for each and tracks the result; budgets and the decision to buy commitments stay with you. Where cost needs to be read beside performance, Datadog Cloud Cost Management sits on the same platform as the monitoring.
RelatedAWS monitoring with DatadogDatadog Cloud Cost Management
How an AWS engagement with Interkey runs
-
Assess.
Every application, its dependencies, data classification and owner, with a placement decision for each.
-
Land the foundations.
Accounts, identity, network and guardrails written as code.
-
Migrate in dependency order.
Each workload moved on a cut-over agreed with its owner, monitored from day one.
-
Decommission.
The old environment switched off on a date.
-
Operate.
Interkey, your team or both, with each side's part written down.
What drives the cost of AWS consulting
Each engagement is quoted from its scope. These are the inputs that move the price.
| Driver | Why it matters |
|---|---|
| Number of applications | Each one needs its own classification, decision and cut-over |
| Dependencies between them | Tangled estates move in more, smaller steps |
| Replatform and rewrite share | Adapting applications to managed services takes more work than rehosting them |
| State of the landing zone | An account structure built by hand is rebuilt as code first |
| Operation after go-live | Coverage hours and the platforms in scope set the managed service |
| Licences and consumption | AWS consumption and Datadog licences are billed separately from Interkey's work |
Working with a partner based in Riyadh
Interkey's engineers are in Riyadh, work in Arabic and English, and follow the Saudi working week, Sunday to Thursday, in your time zone. Out-of-hours or round-the-clock cover is designed and priced in the agreement where a platform needs it. Monitoring data and runbooks are placed where your data residency policy allows. When the platform is live, managed cloud services keep it patched, monitored and costed.
Relatedmanaged cloud services
Questions buyers ask about AWS consulting
What does an AWS consulting partner in Saudi Arabia actually do for us?
Interkey, an AWS partner, decides with you where each workload may run, builds the landing zone, migrates in dependency order, runs Amazon EKS, sets up Datadog monitoring and reviews the AWS bill monthly, on a written scope.
Can Interkey prepare our AWS accounts for the Saudi Region before it launches?
Yes. Classification, a landing zone written as code and migration plans can be ready before launch. AWS says the Region is on track to launch in December 2026; each workload moves once the services it needs are offered there.
How is AWS consulting from Interkey priced in KSA?
From the scope: the number of applications, their dependencies, how many are replatformed, the state of the landing zone and any operation after go-live. AWS consumption and Datadog licences are shown separately.
How long does an AWS migration project take?
It depends on the size of the estate, the dependencies between applications and their owners' change windows. The inventory and a decision per workload are scoped first, and the rest is quoted from them.
Can we run Kubernetes on Amazon EKS and still keep some data in the Kingdom?
Yes. Workloads whose data may sit in an AWS Region run on EKS; those that must stay in the Kingdom run on a self-managed cluster there. Interkey operates the platform layer of both.
Can Interkey cover AWS monitoring and the Datadog licences as well?
Yes. Interkey sells Datadog licences in Saudi Arabia, connects your AWS accounts, tunes dashboards and alerts, and supports it from Riyadh.
Next
Read next
Next step
Scope your AWS programme
Tell us what runs where today, which data your policy keeps in the Kingdom and what you want from AWS. We will reply with the questions that decide placement and a proposed first phase.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia