## Conclusion

In the world of cloud-native database management, TiDB Operator extends Kubernetes to run and manage TiDB clusters on Amazon EKS. TiDB Operator provides a declarative way to deploy, scale, and operate TiDB on any Kubernetes cluster, enabling users to leverage the full power of container orchestration for their distributed SQL database.

Key takeaways from this lab:

- **Amazon EKS** provides a managed Kubernetes control plane; TiDB runs as pods on EKS worker nodes
- **TiDB Operator** deploys TiDB as Kubernetes-native workloads (Pods, Services, StatefulSets)
- **TidbCluster** is the main Custom Resource (CR) that defines the desired TiDB cluster topology
- **LoadBalancer** (internal NLB) exposes TiDB for access from the bastion host within the VPC
- **Helm** is used to install TiDB Operator into the EKS cluster

For production deployments, scale the EKS node group and the TidbCluster with more PD, TiKV, and TiDB replicas across multiple availability zones. Refer to the [Deploy TiDB on Amazon EKS](https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/) documentation for advanced configuration.