Video tutorial: MongoDB on Amazon EKS using Percona Everest

Percona Everest
1

Hi,

You’ve already read a lot from me about Everest, I’m sure many of you have wanted to try it but didn’t have the time or a ready-made environment.

I thought you might like a video course on how to install and configure Percona Everest, from the beginning creating an EKS cluster, configuring S3 bucket, installing PMM and other components.

It’s only 30 minutes and 7 videos. If you watch them, you will have an extensive understanding of how Everest and other components work.

Full Playlist:
https://www.youtube.com/playlist?list=PLWhC0zeznqklUaogWnSNMjutkVdi8TjYl

Videos:

  1. Deploy a Kubernetes cluster on Amazon EKS
  2. Install Percona Everest and provision a MongoDB cluster
  3. Configure an S3 bucket and enable backups
  4. Install PMM and enable database monitoring
  5. Connect to MongoDB cluster created using Percona Everest
  6. Restore a MongoDB database from a backup
  7. Clear the test environment and remove the EKS cluster

I would be very grateful for feedback from you.

Video:

2

I found your videos very informative. The only complaint I have is mydbaas.labs.percona.com which is used to generate the cluster.yaml example is not working.

3

Hi, yes unfortunately the service is not working and it is not yet known if it will work.

I can share the config that the service provided to me, you need to change the parameters and run it

addons:
- name: aws-ebs-csi-driver
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
  name: dbazhenov-demo-west
  region: us-west-2
nodeGroups:
- desiredCapacity: 3
  iam:
    withAddonPolicies:
      ebs: true
      efs: true
      fsx: true
  instanceType: m5.xlarge
  maxSize: 5
  minSize: 1
  name: ng-1
  preBootstrapCommands:
  - echo 'OPTIONS="--default-ulimit nofile=1048576:1048576"' >> /etc/sysconfig/docker
  - systemctl restart docker
  volumeSize: 100
  volumeType: gp2
4

hi folks, I have a question regarding MongoDB connection. In the video was used wildcard 0.0.0.0/0 which will expose DB to the whole internet. And yeah, it works. However, when I am trying to restrict access only to the internal VPC like 10.10.0.0/16 and NLB that everest creates without SGs doesn’t allow me to connect MongoDB.

I found a way to create NLB manually with SGs and skip ranges. Is it possible to implement on the Everest side option to set a list of SGs instead of the IP range?