Mount S3 Bucket onto Linux Folder : s3FS : FUSE - Filesystem in Userspace

https://levelup.gitconnected.com/how-to-mount-s3-bucket-on-an-ec2-linux-instance-df44c7885aae

https://medium.com/tensult/aws-how-to-mount-s3-bucket-using-iam-role-on-ec2-linux-instance-ad2afd4513ef

S3FS

An S3 bucket can be mounted in an AWS instance as a file system known as S3fs. S3fs is a FUSE file system that allows you to mount an Amazon S3 bucket as a local file system.

Filesystem in Userspace (FUSE) is a simple interface for userspace programs to export a virtual file system to the Linux kernel.

• Install S3FS
• vim /etc/passwd-s3fs [Enter AccessKey/Secret Key of AWS having full S3 Permissions]
• Mount Bucket to a Linux Folder

          mkdir /mys3bucket

         s3fs your_bucketname -o use_cache=/tmp -o allow_other -o uid=1000 -o mp_umask=002 -o multireq_max=5 /mys3bucket

Convert Postman to OpenAPI

https://www.apimatic.io/dashboard?modal=transform

Lombok : What it does

https://www.geeksforgeeks.org/introduction-to-project-lombok-in-java-and-how-to-get-started/

https://javabydeveloper.com/lombok-data-annotation/#0-1-what-is-lombok-data-annotation

EKS : Kubernetes : AWS : Install Kubernetes on Control Plane and Configure EKS with kubectl

https://www.cyberciti.biz/faq/linux-unix-running-sudo-command-without-a-password/

visudo

703250313 ALL=(ALL) NOPASSWD: ALL

eks                ALL=(ALL) NOPASSWD: ALL

https://unix.stackexchange.com/questions/73484/how-can-i-set-vi-as-my-default-editor-in-unix

export VISUAL=vim

export EDITOR="$VISUAL"

https://docs.docker.com/engine/install/ubuntu/

https://kubernetes.io/docs/setup/

https://kubernetes.io/docs/setup/production-environment/tools/

> Bootstrapping clusters with kubeadm

> Installing Kubernetes with kops

> Installing Kubernetes with Kubespray

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/

Installing kubeadm, kubelet and kubectl

""""""""""You will install these packages on all of your machines:"""""""""

kubeadm: the command to bootstrap the cluster.

kubelet: the component that runs on all of the machines in your cluster and does things like starting pods and containers.

kubectl: the command line util to talk to your cluster.

https://kubernetes.io/docs/tasks/tools/included/optional-kubectl-configs-bash-linux/

apt-get install bash-completion

source /usr/share/bash-completion/bash_completion

type _init_completion

echo 'source <(kubectl completion bash)' >>~/.bashrc

kubectl completion bash >/etc/bash_completion.d/kubectl

kubectl completion bash

https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/

> sudo snap install kubectl --classic

> kubectl version --client

https://unix.stackexchange.com/questions/47814/searching-command-history

history | grep SEARCH_STRING

https://docs.aws.amazon.com/eks/latest/userguide/install-aws-iam-authenticator.html

curl -o aws-iam-authenticator https://amazon-eks.s3.us-west-2.amazonaws.com/1.21.2/2021-07-05/bin/linux/amd64/aws-iam-authenticator

chmod +x ./aws-iam-authenticator

mkdir -p $HOME/bin && cp ./aws-iam-authenticator $HOME/bin/aws-iam-authenticator && export PATH=$PATH:$HOME/bin

echo 'export PATH=$PATH:$HOME/bin' >> ~/.bashrc

aws-iam-authenticator help

https://www.geeksforgeeks.org/find-command-in-linux-with-examples/

find ./path/subpath searchFileName

Syntax :

$ find [where to start searching from]

 [expression determines what to find] [-options] [what to find]

 

 

 Instead of manually making 1 node as Kubenetes Master and rest as worker using "kubeadm" manually

 We go for EKS approach

 

 kubectl cluster-info

 kubectl 

 kubectl get pods

 

 

 eks@GRDLUSAWSJS01:~$ kubectl get deployment  -n fda

NAME                 READY   UP-TO-DATE   AVAILABLE   AGE

analytics            1/1     1            1           378d

business-rules       1/1     1            1           330d

case-management      1/1     1            1           330d

classifiy-rule       1/1     1            1           378d

cora-mail            1/1     1            1           378d

data-processor       1/1     1            1           330d

doc-conversion-api   1/1     1            1           323d

eaas-service         1/1     1            1           378d

email-segmentator    1/1     1            1           378d

flowable             1/1     1            1           330d

genex-runtime        1/1     1            1           378d

ief-classification   1/1     1            1           377d

ief-extraction       1/1     1            1           377d

ief-tensorflow       1/1     1            1           377d

ml-webapp            1/1     1            1           332d

modelserver          1/1     1            1           378d

nlu-service          1/1     1            1           378d

ocr-nuance           1/1     1            1           378d

output-generation    1/1     1            1           330d

platform             1/1     1            1           330d

slot-modelserver     1/1     1            1           368d

slot-serving         1/1     1            1           368d

trainer              1/1     1            1           378d

usaaddress           1/1     1            1           330d

vea-cc               1/1     1            1           378d

vea-nlp              1/1     1            1           378d

eks@GRDLUSAWSJS01:~$ kubectl rollout history deployment vea-cc -n fda

deployment.apps/vea-cc

REVISION  CHANGE-CAUSE

1         <none>

2         <none>

3         <none>

4         <none>

eks@GRDLUSAWSJS01:~$ kubectl get nodes

NAME                            STATUS   ROLES    AGE    VERSION

ip-10-102-25-101.ec2.internal   Ready    <none>   151d   v1.17.9-eks-4c6976

ip-10-102-25-105.ec2.internal   Ready    <none>   274d   v1.17.9-eks-4c6976

ip-10-102-25-142.ec2.internal   Ready    <none>   69d    v1.17.9-eks-4c6976

ip-10-102-25-143.ec2.internal   Ready    <none>   179d   v1.17.9-eks-4c6976

ip-10-102-25-149.ec2.internal   Ready    <none>   330d   v1.17.9-eks-4c6976

ip-10-102-25-186.ec2.internal   Ready    <none>   260d   v1.17.9-eks-4c6976

ip-10-102-25-247.ec2.internal   Ready    <none>   260d   v1.17.9-eks-4c6976

ip-10-102-25-29.ec2.internal    Ready    <none>   302d   v1.17.9-eks-4c6976

ip-10-102-25-31.ec2.internal    Ready    <none>   326d   v1.17.9-eks-4c6976

ip-10-102-25-40.ec2.internal    Ready    <none>   260d   v1.17.9-eks-4c6976

ip-10-102-26-106.ec2.internal   Ready    <none>   330d   v1.17.9-eks-4c6976

ip-10-102-26-111.ec2.internal   Ready    <none>   330d   v1.17.9-eks-4c6976

ip-10-102-26-55.ec2.internal    Ready    <none>   179d   v1.17.9-eks-4c6976

ip-10-102-26-58.ec2.internal    Ready    <none>   233d   v1.17.9-eks-4c6976

ip-10-102-26-74.ec2.internal    Ready    <none>   179d   v1.17.9-eks-4c6976

ip-10-102-26-88.ec2.internal    Ready    <none>   164d   v1.17.9-eks-4c6976

eks@GRDLUSAWSJS01:~$ kubectl cluster-info

Kubernetes master is running at https://23BB04FB3E3508D16899825B2B3F38FA.yl4.us-east-1.eks.amazonaws.com

CoreDNS is running at https://23BB04FB3E3508D16899825B2B3F38FA.yl4.us-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

Metrics-server is running at https://23BB04FB3E3508D16899825B2B3F38FA.yl4.us-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

eks@GRDLUSAWSJS01:~$

https://rafay.co/the-kubernetes-current/getting-started-with-amazon-eks/

Linux : PING - Internet Speed Test : 8.8.8.8 - Google DNS

https://wisetut.com/best-ping-test-ip-addresses-google-dns-8-8-8-8-cloudflare-dns-1-1-1-1/

The network connection to the 8.8.8.8 Google DNS service can be tested with the ping command like below.

$ ping 8.8.8.8

The output is like below as we can see that the time or RTT is very low.

Linux : Ubuntu - APT vs SNAP

https://phoenixnap.com/kb/snap-vs-apt

Linux:/etc/shells or /etc/os-release

 eks@GRDLUSAWSAMUT01:~$ cat /etc/os-release

NAME="Ubuntu"

VERSION="18.04.6 LTS (Bionic Beaver)"

ID=ubuntu

ID_LIKE=debian

PRETTY_NAME="Ubuntu 18.04.6 LTS"

VERSION_ID="18.04"

HOME_URL="https://www.ubuntu.com/"

SUPPORT_URL="https://help.ubuntu.com/"

BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"

PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"

VERSION_CODENAME=bionic

UBUNTU_CODENAME=bionic

eks@GRDLUSAWSAMUT01:~$ cat /etc/shells

# /etc/shells: valid login shells

/bin/sh

/bin/bash

/bin/rbash

/bin/dash

/usr/bin/tmux

/usr/bin/screen

eks@GRDLUSAWSAMUT01:~$