This doc contains template that you (PM/TM) should paste in the JIRA task and answer inline.

# questionnaire

### are we creating staging and prod OR only the prod env?
---

### do we have the SLA contract for this client? (yes/no)
---

### have you approved $650/mo per env with the client?
---

### select desired AWS region for the infrastructure?
---

| Region Name                     | Region Code   |
|---------------------------------|---------------|
| US East (N. Virginia)           | us-east-1     |
| US East (Ohio)                  | us-east-2     |
| US West (N. California)         | us-west-1     |
| US West (Oregon)                | us-west-2     |
| Africa (Cape Town)              | af-south-1    |
| Asia Pacific (Hong Kong)        | ap-east-1     |
| Asia Pacific (Hyderabad)        | ap-south-2    |
| Asia Pacific (Jakarta)          | ap-southeast-3|
| Asia Pacific (Kuala Lumpur)     | ap-southeast-5|
| Asia Pacific (Melbourne)        | ap-southeast-4|
| Asia Pacific (Mumbai)           | ap-south-1    |
| Asia Pacific (Osaka)            | ap-northeast-3|
| Asia Pacific (Seoul)            | ap-northeast-2|
| Asia Pacific (Singapore)        | ap-southeast-1|
| Asia Pacific (Sydney)           | ap-southeast-2|
| Asia Pacific (Tokyo)            | ap-northeast-1|
| Canada (Central)                | ca-central-1  |
| Europe (Frankfurt)              | eu-central-1  |
| Europe (Ireland)                | eu-west-1     |
| Europe (London)                 | eu-west-2     |
| Europe (Milan)                  | eu-south-1    |
| Europe (Paris)                  | eu-west-3     |
| Europe (Spain)                  | eu-south-2    |
| Europe (Stockholm)              | eu-north-1    |
| Europe (Zurich)                 | eu-central-2  |
| Middle East (Bahrain)           | me-south-1    |
| Middle East (Israel)            | il-central-1  |
| Middle East (UAE)               | me-central-1  |
| South America (São Paulo)       | sa-east-1     |


### what domain name should be used for the production env?
---

### how to access the godaddy or registrar to update the NS records of the domain?
---
If they bought the domain in godaddy - pls invite our account (devops+godaddy@saritasa.com) to manage their domain

### is this a new or a legacy project?
---
new means - saritasa developed this project from scratch

### technology stack backend
---
- language:
- framework (and version):
- git repo:

### technology stack frontend
---
- language:
- framework (and version):
- git repo:

### queue usage
---
are we using any queus like celery in the backend solution?

### aws services
---
what aws services are planned to be used (outside EC2, RDS, S3, ELB, EKS, ECS, VPC). List them below

### what database you want to use?
---

### what caching server you want to use?
---

### do we send outgoing emails from the server?
---
I.e. do you need sendgrid to act as email gateway for outgoing emails?

- If yes, do they have their own sendgrid account? 
  - If they have an existing account - ask them to invite our devops team using the following pattern of the email: devops+CLIENTNAME@saritasa.com, i.e. devops+trivver@saritasa.com.

If they don't have an existing sendgrid account - we will create one on their behalf.

### do we use AWS S3 buckets?
---

### list git repos that should be deployed in the eks cluster?
---

### stakeholders of the project?
---

- client name:
- client email:
- PM:
- TM:
- QA:
- Lead backend dev:
- Lead frontend dev: