---
# System prepended metadata

title: Task Backlog

---

# Task Backlog

## December


From the list of proposed changes abd improvements, we have selected a list of tasks that we think that is good to start with. They can be done without collision with other task and they can be implemented immidiatlelly and should not impact existing resources or billing. We have collected all the tasks and divided them into subgroups. It is possible to carry out all of them simultaneously or focus on one area, e.g. cost optimization

**Cost saving**
- [ ] Enable budgets and cost estimations
- [ ] Detach unused elastic Ip. (8 unused elastic IP) 
- [ ] removing unused resources like:
    - Verify efficiency of EBS storage
- [ ] Use magnetic disk in EBS instead SSD if possible
- [ ] Check out connecting s3 endpoints to cloudfront
- [ ] Use magnetic disk in EBS instead SSD if possible
- [ ] Export snapshot to s3 instead of automatic rds snapshot mechanism


**Network and connectivity components**

- [ ] Review publicly accessible resources
- [ ] A follow up audit and security review to confirm fixes with possible cross check tools 

**Resource sizing**
- [ ] Review of existing resources in lookout for legacy pieces



## After new Year


### Task that correlated and better to start them in parallel

Tasks that are not listed in the first section require more time or have a more complex structure. The execution of each of them may relate to other tasks and even cause a short break in the operation of the application. Therefore, the tasks must be performed with utmost care and precision. 

I believe that starting with cleaning up the current infrastructure, removing missconfiguration and only after completing these steps, moving on to updates and upgrades reflects well the idea of evolution and not revolution. 


If we assume that one person will work on the implementation of changes, I would arrange the tasks in this order:
1) Cost optimization
    a) Resource sizing
    b) Preparing a yearly plan based on current workload visible in cost explorer for 
    c) Other cost saving tasks recommended
2) Resource security 
    a) Resource security
    b) Network and connectivity
    c) Security anomaly detection
3) IaaC improvements and changes

If two people were involved in the design work, then step one combined with step two would be a good solution.

Go through security audit, analyse eudit report, implement fixes. If some of fixes apply to terraform-defined resources make corresponding changes in terraform repository and apply changes. 

While analyzing the report, we will come across irregularities related to networking and connectivity. Therefore, we believe that during this task it is worthwhile to carry out the following two tasks in the meantime
- [ ] Review network policies to keep private traffic private by VPC peerings and endpoints
- [ ] Review and enable industry standard for logging and auditing purposes




IaaC improvment, upgrade terraform version connect with implementing IaaC code security

- [ ] Implement static code scanners to catch misconfigurations and policy issues on PR level




