MariaDB on AWS and Azure, engineered for production.

KineticSkunk helps teams assess, migrate, build, protect, optimise and operate MariaDB on AWS, and run self-managed MariaDB on Azure.

Professional services establish the platform and operating controls; managed operations keep it secure, recoverable, observable and maintained.

Talk to a Cloud Platform Engineer

Explore AWS Database Solutions

MariaDB logo

MariaDB capability connected to our AWS platform work.

KineticSkunk is a MariaDB partner focused on MariaDB workloads running on AWS. The relationship adds database-platform capability to the AWS environments we design, migrate, transition and operate.

MariaDB Partner

Our MariaDB relationship supports customer conversations around MariaDB platform design, migration, implementation and ongoing operations.

Database-platform conversations start from a recognised MariaDB relationship.

AWS-first delivery

MariaDB is treated as part of the AWS platform it depends on: compute, storage, networking, security, recovery and observability are considered together.

The database is engineered alongside the AWS foundation it runs on, not in isolation.

Managed-platform destination

Professional services can solve the immediate database-platform requirement and establish the controls needed for ongoing managed operations.

Focused platform work leads into recurring managed operations when ongoing ownership is required.

The database is part of the AWS operating model.

A production database does not operate in isolation. Availability depends on infrastructure, security, recovery, observability and clear operational ownership. We engineer MariaDB in that wider AWS context.

AWS foundation

Compute, storage, networking, identity and security provide the foundation the database depends on.

MariaDB platform

MariaDB provides the relational data platform, configured around the workload's availability, recovery and operating requirements.

Managed operations

Monitoring, backup, recovery, lifecycle, security, capacity and incident management become recurring operational responsibilities.

Focused on the database platform.

KineticSkunk

KineticSkunk engineers and operates MariaDB and the AWS environment around it.

  • AWS infrastructure
  • MariaDB platform configuration
  • availability
  • security
  • backup and recovery
  • observability
  • capacity
  • patching
  • lifecycle
  • platform operations

Shared

Some responsibilities are coordinated with the customer's teams.

  • migration windows
  • RTO/RPO
  • capacity requirements
  • application dependencies
  • change coordination
  • incident investigation
  • production validation

Application team

Application teams continue to own the application and its data design. Where application SQL or schema behaviour creates a platform issue, KineticSkunk may identify and evidence the issue, and remediation requiring application or database development remains with the customer's development team.

  • application code
  • schema and data modelling
  • SQL development
  • stored procedures
  • ORM changes
  • business logic
  • application-level remediation

MariaDB on AWS services we support

Start with the database-platform responsibility that needs attention. Each engagement can solve a focused problem and establish the controls required for ongoing managed operations.

AssessMariaDB on AWS Assessment
A prioritised database-platform and operating plan.

Understand the architecture, risks and operating gaps before changing the platform.

Review the MariaDB workload in the context of its AWS environment.

Explore AWS Database Solutions
  • deployment architecture
  • versions and lifecycle
  • AWS compute and storage
  • availability and replication
  • backup and recovery
  • security controls
  • observability
  • resource utilisation and capacity
  • patch posture
  • operational ownership
Migrate & ModerniseMariaDB Migration & Modernisation
MariaDB operating on an AWS foundation designed around the required operating model.

Move MariaDB onto AWS or improve an existing MariaDB-on-AWS platform.

Scope may include the discovery, planning and transition work needed to land the database safely.

Explore AWS Database Solutions
  • current-state discovery
  • dependency identification
  • target AWS architecture
  • infrastructure preparation
  • migration planning
  • replication strategy
  • cutover planning
  • rollback planning
  • platform validation
  • operational transition
Build & SecureMariaDB Platform Engineering
A production-ready MariaDB platform with clear operational controls.

Engineer the AWS and MariaDB platform around production requirements.

Scope may include the infrastructure, configuration and security controls the workload depends on.

Explore AWS Database Solutions
  • AWS compute and storage
  • VPC and network controls
  • MariaDB installation and configuration
  • Amazon RDS for MariaDB where appropriate
  • availability architecture
  • access controls
  • secrets management
  • encryption
  • logging
  • patch baseline
  • monitoring foundation
Protect & RecoverMariaDB Resilience & Recovery
Database recovery behaviour that is understood, documented and validated.

Make database recovery part of the wider AWS recovery model.

The proposition stays about tested recovery and operating confidence, rather than merely enabling backup features.

Explore AWS Data Protection & Recovery
  • backups
  • retention
  • snapshots
  • point-in-time recovery
  • replication
  • failover
  • RTO/RPO alignment
  • restoration procedures
  • recovery testing
  • DR runbooks
  • recovery evidence
Optimise & ObserveMariaDB Performance, Capacity & Observability
Better evidence for performance, capacity and infrastructure-cost decisions.

Make platform behaviour visible and keep resources aligned to workload demand.

The focus is platform-level signals and resource decisions, not application change.

Explore AWS Database Solutions
  • CPU
  • memory
  • storage behaviour
  • connections
  • replication health
  • locks and contention visibility
  • database configuration
  • capacity trends
  • AWS resource sizing
  • metrics
  • logs
  • alerts
  • Datadog integration
  • AWS cost visibility
ManageManaged MariaDB on AWS
MariaDB operated as part of the AWS platform, with clear ongoing ownership.

Move agreed database-platform responsibilities into ongoing managed operations.

This is the destination for recurring database-platform ownership, where agreed responsibilities become a continuing service rather than a one-off project.

Explore AWS Managed Platform
  • monitoring
  • alert response
  • backup operations
  • recovery validation
  • availability monitoring
  • patching
  • version lifecycle
  • security operations
  • capacity management
  • platform performance monitoring
  • incident management
  • problem management
  • MariaDB escalation
  • reporting
  • continual improvement

MariaDB connects to the AWS and Azure disciplines around it.

MariaDB is engineered and operated alongside the cloud disciplines it depends on, on AWS and on Azure. These are the connected solutions.

SMB solution
AWS Database Solutions iconAWS Database Solutions

Where MariaDB work belongs on AWS

Assess, migrate, engineer and operate MariaDB as part of the AWS platform.

Explore solution
SMB solution
AWS Database Solutions iconAzure Database Solutions

Where MariaDB work belongs on Azure

Assess, migrate, engineer and operate self-managed MariaDB as part of the Azure platform.

Explore solution
SMB solution
AWS Managed Platform iconAWS Managed Platform

One managed operating relationship

Move ongoing MariaDB and AWS operating responsibilities into one managed relationship.

Explore solution
SMB solution
AWS Managed Platform iconManaged Azure Platform Operations

Recurring MariaDB ownership on Azure

Move ongoing MariaDB and Azure operating responsibilities into Managed Azure Platform Operations.

Explore solution
SMB solution
Data Protection and Recovery iconAWS Data Protection & Recovery

Recovery you can evidence

Connect database backup and restoration to the wider AWS recovery architecture and recovery-evidence model.

Explore solution
SMB solution
AWS Cost Optimisation and FinOps iconAWS Cost Optimisation & FinOps

Cost visible as demand changes

Keep database infrastructure sizing and AWS resource cost visible as workload demand changes.

Explore solution

Professional services establish the platform. Managed operations keep it ready.

Whether MariaDB is already running on AWS, being moved or built on AWS, or running self-managed on Azure, professional services establish the platform and operating controls, and managed operations keep it ready.

Already running on AWS

Already running MariaDB on AWS?

Stabilise and establish operational control.

Talk to a Cloud Platform Engineer
  1. 1

    Assess the current platform

    Review architecture, configuration, availability, recovery, security, observability and ownership.

    Known platform condition

  2. 2

    Prioritise operational gaps

    Separate immediate platform risks from planned improvements.

    Prioritised operating plan

  3. 3

    Stabilise and improve

    Address the agreed availability, security, recovery, monitoring and lifecycle requirements.

    Agreed risks addressed

  4. 4

    Establish operating controls

    Put monitoring, recovery routines, runbooks, ownership and escalation paths in place.

    Operational controls in place

  5. 5

    Transition into managed operations

    Move the agreed recurring responsibilities into the KineticSkunk operating model.

    Managed MariaDB on AWS

Moving or building on AWS

Moving or building MariaDB on AWS?

Design operations into the platform from the beginning.

Talk to a Cloud Platform Engineer
  1. 1

    Define workload requirements

    Understand availability, recovery, security, capacity and operating expectations.

    Clear workload requirements

  2. 2

    Design the target platform

    Define the AWS and MariaDB architecture required to support them.

    Target platform design

  3. 3

    Build or migrate

    Implement the platform and execute the agreed migration or deployment plan.

    Platform built or migrated

  4. 4

    Validate production readiness

    Verify monitoring, backup, recovery, security and operational procedures.

    Production readiness verified

  5. 5

    Transition into managed operations

    Move agreed database-platform responsibilities into recurring service ownership.

    Managed MariaDB on AWS

Running or moving on Azure

Running MariaDB on Azure, or moving it there?

Engineer and operate self-managed MariaDB on Azure infrastructure.

Talk to a Cloud Platform Engineer
  1. 1

    Assess or define the requirement

    Review an existing self-managed MariaDB on Azure, or define the workload requirements for a move onto Azure, including migration off the retired Azure Database for MariaDB service where relevant.

    Known condition or clear requirements

  2. 2

    Design the target Azure platform

    Define the Azure Virtual Machines, managed disks, networking and security model for self-managed MariaDB.

    Target Azure platform design

  3. 3

    Build or migrate

    Implement the Azure platform and execute the agreed migration or deployment plan.

    Platform built or migrated

  4. 4

    Validate production readiness

    Verify monitoring, backup, recovery, security and operational procedures on Azure.

    Production readiness verified

  5. 5

    Transition into managed operations

    Move agreed database-platform responsibilities into Managed Azure Platform Operations.

    Managed MariaDB on Azure

Make MariaDB part of a better-operated AWS or Azure platform.

Whether MariaDB is already running on AWS or Azure, needs to move, or is being introduced into a new platform, start with the operating outcome that needs attention.

Talk to a Cloud Platform EngineerExplore AWS Database Solutions