Trusted Images - MariaDB 10.11 on Debian 12 AMI

This AMI is maintained by Trusted Images and includes open source software packages for the target operating system.

MariaDB 10.11 on Debian 12 provides a maintained, hardened AMI for MariaDB relational database workloads on Debian 12. Instead of starting from a generic operating system image and manually installing packages, hardening the host, collecting scan evidence, and writing usage documentation, you can launch a reviewed base image and apply your environment-specific configuration.

• Faster time to a maintainable baseline: launch with the MariaDB 10.11 package set installed and basic command/service validation completed during image preparation.
• Reduced image maintenance burden: monthly rebuilds and priority rebuilds for important upstream security updates help shorten the time spent tracking base image drift.
• Audit-ready evidence: supported AMI versions include SBOM data, package inventory, source and root filesystem scan output, runtime hardening status, and validation logs.
• No hidden defaults: the AMI is delivered without default application credentials, seeded users, private keys, or customer-specific secrets.

A platform team needs a repeatable database server baseline for AWS environments. The team launches this AMI, restricts security groups to the minimum required ports, enables EBS encryption, connects centralized logging, and applies its own application configuration, credentials, backup policy, and monitoring controls. This gives the team a documented starting point while preserving control over production settings.

• MariaDB 10.11 package set installed on Debian 12
• Command and service validation where applicable
• Trusted Images Linux hardening baseline and runtime hardening checks
• Package inventory, SBOM evidence, source scan output, and root filesystem scan output for supported AMI versions
• Monthly rebuild process for operating system and package security updates

• No default application passwords, user data, certificates, private keys, or customer credentials are installed.
• SSH access uses the AWS key pair selected at launch and the default user admin.
• IMDSv2 is required where supported by the AMI baseline.
• Open only the MariaDB port you intend to use, commonly TCP 3306, to trusted sources.
• Enable EBS encryption, backups, host logging, and monitoring according to your AWS account standards.
• You remain responsible for application configuration, credential rotation, network access policy, data protection, and compliance validation in your environment.

1. Subscribe and launch the AMI in your target VPC.
2. Connect as admin with your AWS key pair or approved SSM access path.
3. Review installed package versions and service status.
4. Apply your configuration, credentials, data paths, backup policy, and logging setup.
5. Restrict security group ingress to the ports and sources required by your deployment.
6. Validate the service from an allowed client before using it for production workloads.

Supported AMI versions include SBOM data, package inventory, scan output, runtime hardening status, and validation evidence. Evidence for supported AMI versions can be requested at support@trusted-images.com .

Trusted Images rebuilds supported AMIs monthly and when important upstream security updates require an earlier rebuild. The published AMI version reflects evidence artifacts retained for support records.

Trusted Images provides email support at support@trusted-images.com . Support covers launch guidance, AMI packaging questions, package/version questions for the delivered image, security patch and rebuild inquiries, Marketplace image issues, refund requests, and billing questions. Support does not include customer production operations, ongoing monitoring, custom application code, customer data migration, or third-party integrations.

Subscribe and launch the AMI to evaluate it in your AWS account. For hardening evidence, deployment guidance, or Marketplace support, contact support@trusted-images.com .

Not affiliated with, endorsed by, or sponsored by MariaDB Foundation, MariaDB plc, and Debian projects.