Cloud & IaC

AWS Support

Remote AWS troubleshooting and support for production problems across compute, networking, storage, databases, permissions, monitoring, backups, billing and security.

AWS problems we handle

Support for real production issues, not just generic cloud advice

Instances, applications or load-balanced services are unavailable, unstable or failing health checks
Access errors, IAM permissions, S3 policies or KMS settings are blocking normal operations
Networking, DNS, certificates or CDN configuration is causing downtime, redirects or origin errors
AWS spend is increasing and you need unused resources, storage, data transfer or scaling reviewed

How we approach AWS work

We trace the issue across the services involved

Map the affected service path: user request, DNS, CDN, load balancer, compute, app and database
Check logs, metrics, alarms, permissions, recent changes and deployment history before changing anything
Use scoped access where possible, starting read-only for reviews and requesting write access only when needed
Provide clear notes on what was found, what changed and what should be monitored or improved next

Major AWS services

AWS areas we can help troubleshoot and improve

Production AWS problems often cross multiple services. We look at how the pieces fit together so the underlying cause is not missed.

EC2, EBS & snapshots

Instance failures, disk pressure, volume growth, backup snapshots, recovery planning, security groups and server-level reliability.

VPC, subnets & security groups

Routing, firewall rules, public/private subnet layout, NAT gateways, peering, blocked ports and connectivity problems.

Load balancers & target groups

ALB/NLB health checks, listener rules, certificates, target failures, 502/504 errors and unstable backend services.

Route 53, ACM & DNS

DNS cutovers, hosted zones, records, certificate validation, failed renewals and routing issues.

CloudFront & CDN behaviour

Cache hit rates, origin errors, cache-control headers, invalidations, SSL settings and slow edge/origin responses.

S3 & object storage

AccessDenied errors, bucket policies, lifecycle rules, backups, public access settings, storage class choices and application upload failures.

IAM, roles & KMS

Least-privilege access, broken permissions, stale keys, role assumptions, encryption keys and service-to-service access errors.

RDS & database services

Connectivity, performance symptoms, storage growth, backups, maintenance windows, security groups and reliability checks.

ECS, ECR & containers

Task failures, image pulls, service deployments, logs, networking, task roles and containerised application issues.

Lambda & API Gateway

Function errors, timeouts, permissions, environment variables, API routing, logs and integration failures.

CloudWatch, CloudTrail & alarms

Missing logs, weak alerting, unclear metrics, audit trails, failed alarms and operational visibility gaps.

AWS Backup & recovery

Backup plans, restore checks, snapshot coverage, retention, recovery risk and evidence that backups can actually be used.

CloudFormation & IaC

Stack failures, drift, rollback issues, parameters, permissions and safer repeatable infrastructure changes.

Billing, cost and usage

Unused resources, storage growth, data transfer, snapshots, load balancers, NAT costs and cost-aware improvements.

WAF, Shield & security controls

Basic edge protection, rule review, logging, exposure checks and security posture improvements.

SES, SNS & SQS

Email sending issues, queues, notifications, permissions, delivery failures and operational messaging workflows.

Common symptoms

Examples of AWS issues customers ask us to investigate

Application uploads fail because S3 permissions, KMS keys or bucket policies do not match the app workflow
CloudFront returns origin errors or poor cache hit rates after a deployment, DNS change or header change
An EC2-hosted application works internally but fails through the load balancer or CDN
RDS or database access breaks after a security group, subnet or credential change
Costs rise because old volumes, snapshots, NAT gateways, data transfer or oversized resources were left running

Useful details to send

What helps us understand the problem quickly

The affected AWS service or user-facing symptom, plus the region and account area if known
Recent changes: deployment, DNS update, security group edit, IAM change, migration or billing event
Relevant error messages, screenshots or log excerpts with secrets and account numbers removed
Whether the issue is live production, planned improvement, cost review, security review or migration support

Safe access

AWS access should be temporary and scoped

We do not need root credentials. For reviews, read-only access is often enough. For changes, permissions should be limited to the services involved and removed after the work is complete.

Read-only review first

For audits, cost reviews and risk checks, read-only access can usually confirm what is running and what needs attention.

Scoped implementation access

For fixes, we confirm the services involved before requesting write access for the specific work required.

IAM user, role or Identity Center

Access can be provided through temporary IAM users, IAM Identity Center or cross-account roles depending on how your account is managed.

Remove access after completion

After handover, temporary users, keys or roles should be removed and any shared secrets rotated where appropriate.

Process

Practical AWS support from problem to handover

Confirm the issue, affected services, business impact and recent changes
Review metrics, logs, configuration, permissions and dependencies before making changes
Apply agreed fixes or produce a prioritised action plan for review-style work
Send a clear handover covering findings, changes, remaining risks and recommended next steps

Relevant stack

Services commonly involved

EC2EBSVPCSecurity GroupsALB/NLBRoute 53ACMCloudFrontS3IAMKMSRDSECSECRLambdaAPI GatewayCloudWatchCloudTrailCloudFormationAWS BackupWAFSESSNS/SQS

Related services

Other focused AWS and infrastructure pages

FAQ

AWS Support FAQ

Common questions before starting AWS troubleshooting, review or support work.

Can you help with existing AWS accounts?

Yes. We can review or troubleshoot existing AWS setups, including compute, networking, storage, permissions, databases, monitoring, backups, billing signals and security risks.

Do you need AWS root access?

No. Root access should not be shared. For reviews, read-only access is usually enough. For implementation, we confirm the scoped permissions required before changes are made.

Can you fix S3 AccessDenied or upload problems?

Yes. These often involve IAM policies, bucket policies, KMS keys, application credentials, public access settings or region/configuration mismatches.

Can you help with AWS cost problems?

Yes. We can review common sources of waste such as unused resources, snapshots, oversized instances, storage growth, NAT gateways, data transfer and weak lifecycle rules.

Can you help with CloudFront, Route 53 or certificate issues?

Yes. We can help troubleshoot DNS routing, origin errors, SSL/TLS certificate validation, cache behaviour, redirects and CDN configuration problems.

How much does this type of work usually cost?

AWS and cloud review work usually starts from $999. Cost optimisation reviews usually start from $1,299.

After the fix

Reduce the chance of the same issue returning.

After an AWS issue is resolved, we can also help with monitoring, backups, restore testing, security hardening, cost review or ongoing infrastructure support where it makes sense.

View support options

Next step

Need AWS support?

Send the symptom, affected services and any recent changes. We will suggest the right starting point and access method.

Contact us