AWS Database Consultant
Auckland & ANZ
Senior AWS database help for teams that need production-safe decisions across Aurora PostgreSQL, Amazon RDS, DMS, RDS Proxy, DocumentDB, migration planning, HA/DR and operational resilience. You work directly with Dipak Rijal — Oracle Certified Master, AWS PostgreSQL SME and Auckland-based senior cloud database engineer.
Available immediately for contract & partner subcontracting · Auckland / Remote ANZ
When to call me
This page is for teams that already have a live AWS database concern or a migration decision that needs senior judgement, not generic cloud advice.
RDS or Aurora is under pressure
Slow queries, rising latency, lock waits, storage growth, connection storms or failover concerns are starting to affect business confidence.
- Triage before risky changes
- Clear root-cause path
- Rollback-aware recommendations
Oracle, PostgreSQL or on-prem migration needs a safer path
You need realistic scope, DMS/SCT strategy, validation design, cutover sequencing and stakeholder-ready explanation before committing.
- Assessment first
- Cutover and rollback plan
- Post-migration tuning
Your delivery team needs senior database depth
Useful for AWS partners, consulting teams and internal platform teams needing a specialist for bids, design reviews or escalations.
- White-label friendly
- NDA available
- Written scope and outputs
What I check first
Workload and architecture posture
Instance class, storage behaviour, parameter groups, failover design, connection patterns, wait events, backup posture and observability gaps.
- Performance signals
- Availability design
- Cost and capacity posture
Replication and cutover risk
Source constraints, schema complexity, DMS task design, full-load and CDC behaviour, validation checkpoints and rollback readiness.
- AWS DMS/SCT
- Validation plan
- Business continuity
Runbooks and support model
Whether the team can detect, diagnose and recover from common RDS/Aurora incidents without depending on tribal knowledge.
- Incident playbooks
- Monitoring checks
- Handover documentation
Typical deliverables
For technical teams
- Architecture or workload review
- Bottleneck summary and prioritised remediation plan
- Parameter, query, index or migration recommendations
- Rollback-safe change sequence
- Monitoring and validation checklist
For managers and partners
- Plain-English risk summary
- Written scope and expected outcomes
- RCA or readiness report suitable for stakeholders
- Handover notes and runbook material
- Clear next-step options by urgency and budget
Best-fit outcomes
- Stabilise live workloads
- Prepare migration or cutover
- Improve HA/DR confidence
- Reduce cloud database cost waste
- Support partner bids and delivery spikes
How the engagement works
First I confirm the problem and urgency. Then I provide a scoped path: rapid triage, fixed-scope review, migration readiness assessment, or longer contract/subcontracting support. The goal is senior judgement quickly, without changing the rest of your delivery model.
Why this is different from generic cloud advice
Database-first AWS judgement
The advice starts from database behaviour: workload shape, recovery needs, query patterns, replication design and operational ownership. AWS service choices then support the database outcome, not the other way around.
Useful for both builders and decision makers
Technical teams receive practical next steps and runbooks. Managers receive risk, trade-offs and decision-ready summaries that help justify scope, sequencing and investment.
Built for live environments
The work assumes production constraints: change windows, rollback, stakeholder confidence, security, confidentiality and handover to the people who will operate the platform after the engagement.