When you are dynamically provisioning PVC you don’t need to create PV at all. Kubernetes will auto create it

Step 1 : Check the storageClass you have in eksctl

kubectl get storageclass

Since, gp2 is listed you can directly use it as storageClass

Step 2 : Create pvc file

apiVersion: v1 
kind: PersistentVolumeClaim 
metadata:
  name: aws-pvc 
spec:
  accessModes:
    - ReadWriteOnce 
  resources:
    requests:
      storage: 5Gi 
  storageClassName: gp2

kubectl apply -f aws-pvc.yml

Step 3 : Update deployment.yml to use aws-pvc.yml

apiVersion: apps/v1 
kind: Deployment 
metadata:
  name: mongo-deployment
spec:
  selector:
    matchLabels:
      app: mongo-pod 
  template:
    metadata:
      labels:
        app: mongo-pod 
    spec:
      containers:
        - name: mongo-pod 
          image: mongo:latest 
          command: ["mongod","--bind_ip_all"] # runs db server
          ports:
            - containerPort: 27017 
          volumeMounts: # mongodb data at /data/db will persist outside this container at volume nfs-volume
            - name: aws-volume 
              mountPath: /data/db # where mongo stores its database files
      volumes:
        - name: aws-volume 
          persistentVolumeClaim:
            claimName: aws-pvc # attach this pvc 

kubectl apply -f deployment.yml

• Pod may take some time to be created. Since pvc needs to be associated with pv . AWS may be taking time to create block storage pv and automatically provision it to pvc
• You can monitor pv creation by following command

kubectl describe pvc aws-pvc

Step 4 : You need to install AWS ECS CSI Driver

Why you need the EBS CSI Driver

• Kubernetes itself does not know how to talk to AWS APIs to create EBS volumes.
• The EBS CSI driver is an add-on that runs in your cluster and provisions/manages EBS volumes when PVCs request them.

Without it, dynamic provisioning will never succeed.