> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/installation-guide/infrastructure-setup/aws/3.-provision-infrastructure.md).
# 3. AWS - Provision Infrastructure
## Overview
The image below illustrates the multiple components deployed. These include the EKS, Worker Nodes, Postgres DB, EBS Volumes, and Load Balancer.
.png?alt=media)
## Steps
1. Clone the DIGIT-DevOps repository:
```
git clone https://github.com/egovernments/DIGIT-DevOps.git
```
2. Navigate to the cloned repository and checkout the kubernetes-1.31 branch:
```bash
cd DIGIT-DevOps
git checkout kubernetes-1.34
```
3. Check if the correct credentials are configured using the command below. Refer to the attached doc to [setup AWS Account](https://core.digit.org/v/2.9-lts/guides/installation-guide/production-setup/aws/3.-setup-aws-account) on the local machine.
```
aws configure list
```
*Make sure that the above command reflects the set AWS credentials. Proceed once the details are confirmed. (If the credentials are not set follow Step 2* [*Setup AWS account*](/platform/guides/installation-guide/infrastructure-setup/aws/2.-setup-aws-account.md) *)*
4. Choose either method below to generate SSH key pairs
* a. Use an online website (not recommended in a production setup. To be only used for demo setups):
* b. Use openssl:
```
openssl genpkey -algorithm RSA -out private_key.pem openssl rsa -pubout -in private_key.pem -out public_key.pem
```
5. Add the public key to your [GitHub account](https://www.youtube.com/watch?v=9C7_jBn9XJ0).
6. Open input.yaml file in vscode. Use the below code to open it in VS code:
`code infra-as-code/terraform/aws/input.yaml`
*If the command does not work, open the file in VS code manually. Once the file is open, fill in the inputs. (If you are not using vscode, open it in any editor of your choice).*
7. Fill in the inputs as per the regex mentioned in the comments.
8. Go to *infra-as-code/terraform/aws* and run *init.go* script to enrich different files based on *input.yaml*.
```
cd infra-as-code/terraform/aws
go run ../scripts/init.go
```
### Terraform Execution: Infrastructure Resources Provisioning
Once we are complete declaring the resources, begin with deploying all resources.
Run the terraform scripts to provision infra required to Deploy DIGIT on AWS.
1. CD (change directory) to the following directory and run the below commands to create the remote state.
```
### Create the remote-state first, remember that the state name should be unique
### You may need to use sudo incase you don't have requisite permission
cd remote-state
terraform init
terraform plan
terraform apply
```
Once the remote state is created, it is time to provision DIGIT infra. Run the below commands:
### Once the remote state is created, you can create the DIGIT Infra
cd ..
terraform init
terraform plan
terraform apply
**Important:**
* **DB password is asked for in the application stage. Remember the password you have provided. It should be at least 8 characters long. Otherwise, RDS provisioning will fail.**
* **The output of the apply command will be displayed on the console. Store this in a file somewhere. Values from this file will be used in the next step of deployment.**
2\. Use this link to [get the kubeconfig from EKS](https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html) for the cluster. The region code is the default region provided in the availability zones in variables.tf. For example - ap-south-1. EKS cluster name also should've been filled in variables.tf.
```bash
aws sts get-caller-identity
# Run the below command and give the respective region-code and the cluster name
aws eks --region update-kubeconfig --name
```
3\. Verify that you can connect to the cluster by running the following command
```
kubectl config use-context
kubectl get nodes
NAME STATUS AGE VERSION OS-Image
ip-192-168-xx-1.ap-south-1.compute.internal Ready 45d v1.15.10-eks-bac369 Amazon Linux 2
ip-192-168-xx-2.ap-south-1.compute.internal Ready 45d v1.15.10-eks-bac369 Amazon Linux 2
ip-192-168-xx-3.ap-south-1.compute.internal Ready 45d v1.15.10-eks-bac369 Amazon Linux 2
ip-192-168-xx-4.ap-south-1.compute.internal Ready 45d v1.15.10-eks-bac369 Amazon Linux 2
```
At this point, your basic infra has been provisioned.
**Note:** Refer to the[ DIGIT deployment ](https://core.digit.org/guides/installation-guide/digit-deployment)documentation to deploy DIGIT services.
## Destroying Infra
To destroy the previously created infrastructure with Terraform, run the command below:
1. ELB is not deployed via Terraform. ELB was created at deployment time by the setup of Kubernetes Ingress. This has to be deleted manually by deleting the ingress service.
* `kubectl delete deployment nginx-ingress-controller -n `
* `kubectl delete svc nginx-ingress-controller -n `
**Note**: Namespace can be either egov or jenkins.
2. Delete S3 buckets manually from the AWS console and verify if ELB got deleted.
* In case of if ELB is not deleted, you need to delete ELB from the [AWS console](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-delete.html).
3. Run `terraform destroy`.
{% hint style="info" %}
Sometimes all artefacts associated with a deployment cannot be deleted through Terraform. For example, RDS instances might have to be deleted manually. It is recommended to log in to the AWS management console and look through the infra to delete any remnants.``
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/platform/guides/installation-guide/infrastructure-setup/aws/3.-provision-infrastructure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.