In this Project I have demonstrated the Provisioning of AWS Architecture using HashiCorp Tool Terraform,also associated a lock using S3 object store and DynamoDB for serving the Terraform automation backend which is basically used to store the terraform state file called tfstate as Terraform maintains a state file inorder to track the services being deployed in AWS. Terraform is written in Go Language and the workflow in the backend includes API calling in-order to deploy resources in AWS or in other words the go language makes API calls to AWS API's to deploy necessary services and resources written by the user using Terraform. I have also made use of GitOps Technology which is bacically the ArgoCD which is a Declarative Gitops based approach to deploy applications in kubernetes and also managing them. One of the greatest advantage of ArgoCD is that it maintains the state of deployment in Kubernetes. The deployments are version controlled and provides continuous deployment.Argo CD follows the GitOps pattern of using Git repositories as the source of truth for defining the desired application state. Argo CD automates the deployment of the desired application states in the specified target environments. Application deployments can track updates to branches, tags, or pinned to a specific version of manifests at a Git commit
Also I have mentioned the provisioning of EKS architecture along with EFS,KMS and RDS in AWS private subnets using gitlab for automating the provisioning of Architecture by Terraform.
Also I have made use of aws-auth inorder to provide access of the cluster to other users. When we create a Cluster generally in Amazon EKS, the user or the IAM Entity who creates the cluster is granted administrative permissions in the cluster's RBAC configuration in the control plane i.e "system:masters" and thereby we can't find this in the Cluster's ConfigMap or any other visible configurations.To grant additional AWS users or roles the ability to interact with the cluster, we must edit the aws-auth ConfigMap within Kubernetes. The aws-auth is initially created to allow our nodes to join our cluster, but we also use this ConfigMap to add RBAC access to IAM users and roles.
Gitlab is used because:-
1.ease of configuration
2.source code security
3.pipeline automation
4.DevOps maturity feedback
5.deployment scheduling
Architecture
