Cloud support
Compute, networking, identity and cost on the two major public clouds — including the parts that only break under load.
Who this is for: Teams running production workloads in AWS or Azure without a cloud engineer on staff.
What we support
AWS and Azure, configured and debugged.
Included
Work covered under this service, whether as a one-off request or on retainer.
- Account and subscription structure, landing zones and guardrails
- Compute, storage and managed database provisioning and sizing
- Networking — VPC or VNet, subnets, routing, security groups, VPN and peering
- IAM roles, policies and least-privilege access review
- Cost review — unused resources, wrong instance families, unattached storage
Common problems
If any of these sound familiar, this is the right service to raise a request against.
Instance unreachable after a security group or route table change
Permission denied errors that only appear for some roles or services
Cloud bill jumped and the cause is not obvious
Load balancer marks targets unhealthy with no clear reason
Backups or snapshots configured but never tested
What troubleshooting includes
Evidence we gather before proposing a change. What is available varies by environment.
- —Flow logs, route tables, security groups and NACL evaluation order
- —IAM policy simulation and effective permissions
- —Cost and usage breakdown by service, region and tag
- —Health check configuration against the actual application response
How an engagement runs
The same path every support request follows, regardless of which service it lands under.
Submit issue
You describe the problem, the environment and the impact.
Initial assessment
We review the environment and whatever evidence is available.
Investigation
An engineer investigates the affected infrastructure.
Remediation
Appropriate changes are made, with a rollback path where possible.
Verification
System behaviour is validated after the change.
Resolution and notes
You receive the outcome and the relevant notes.
Raise a request against cloud support.
Describe the environment and the symptom. Pricing is confirmed in writing before any work starts.
Get technical supportRelated services
Problems rarely stay in one layer. These are the services most often opened alongside cloud support.