Python Pro Needed: AWS Fix, Algo Update

Developer Required: Fix Kite Login + Replace Existing Algo File on AWS

I have an existing **Python-based algo trading system** deployed on an **AWS EC2 Ubuntu server** and connected to **Zerodha Kite Connect API**.

The system was previously working. I have now changed my Zerodha/Kite password, and the existing system is giving:

**`Kite Login Failed: Invalid username or password.`**

In addition to fixing the authentication issue, I also need to **replace the currently deployed algo/Python file with an updated file that I will provide**.

## Existing AWS Setup

* AWS EC2 Ubuntu server
* Existing algo directory:

`~/Vijay915`

* Existing startup command:

`cd ~/Vijay915 && bash start_algo.sh`

* Existing `start_algo.sh` must continue to work after the changes.

## Work Required

### 1. Fix Kite Authentication

Identify and fix the current Kite/Zerodha authentication problem.

The developer should check:

* Kite user/client ID
* Password configuration
* TOTP/authentication mechanism
* API key configuration
* API secret usage
* Request-token/access-token handling
* `.env` files
* Configuration files
* Environment variables
* Startup scripts
* Any other authentication-related configuration

The current error is:

**`Kite Login Failed: Invalid username or password.`**

### 2. Replace the Existing Algo File

I will provide an **updated Python/algo file**.

The developer must:

1. Identify the currently running/deployed Python algo file.
2. Take a backup of the existing file before replacing it.
3. Replace the existing file with my **new Python file**.
4. Ensure that the new file is connected correctly to the existing `start_algo.sh`.
5. Preserve the existing directory structure wherever possible.
6. Check that all required Python packages/dependencies are available.
7. Check that the new file starts without errors.
8. Verify that the new file uses the correct Kite authentication configuration.
9. Test the new file in **PAPER TRADING mode first**.
10. Only after successful testing should LIVE TRADING be enabled with my explicit permission.

### 3. DO NOT Change My Trading Strategy

The developer must **not modify the strategy logic contained in the new file I provide** unless a modification is technically necessary to make it run.

The purpose is:

**New Python file → deploy on AWS → connect to existing configuration/environment → fix Kite authentication → test → run.**

If any modification to the new Python file is required, the developer must explain the reason to me **before making the change**.

### 4. Preserve Existing Startup Method

After deployment, I should still be able to start the system using:

`cd ~/Vijay915 && bash start_algo.sh`

The developer must ensure that `start_algo.sh` points to the correct new Python file.

### 5. Backup Requirement

Before replacing anything, the developer must create a backup of the existing production file.

For example:

`old_algo_backup_YYYYMMDD.py`

The original file must **not be deleted permanently** until I confirm that the new file is working correctly.

### 6. Testing

Testing must be performed in this order:

**Step 1:** Verify AWS environment.

**Step 2:** Verify Python dependencies.

**Step 3:** Verify Kite authentication.

**Step 4:** Deploy the new Python file.

**Step 5:** Run in PAPER TRADING mode.

**Step 6:** Verify market-data/WebSocket connection.

**Step 7:** Verify that the algo starts correctly.

**Step 8:** Check logs for errors.

**Step 9:** Only after my confirmation, test LIVE TRADING.

## Security

I will not unnecessarily provide:

* Zerodha password
* Kite API secret
* TOTP secret
* AWS private SSH key

The developer must use a secure method of working and must not retain or disclose my credentials.

The developer must **not place live orders during testing without my explicit approval**.

## Required Experience

Please apply only if you have hands-on experience with:

* Python
* Zerodha Kite Connect API
* Kite authentication/TOTP
* AWS EC2
* Ubuntu Linux
* SSH
* Bash
* Python deployment
* WebSocket market data
* Algo-trading systems

## Deliverables

The developer must provide:

1. Existing Kite login problem fixed.
2. New Python algo file deployed.
3. Existing file backed up.
4. `start_algo.sh` verified/updated if required.
5. Required dependencies installed/verified.
6. Paper-trading test completed.
7. Market-data/WebSocket connection verified.
8. Logs checked.
9. Confirmation that the algo can be started using:

`cd ~/Vijay915 && bash start_algo.sh`

10. A brief explanation of:

* What caused the login problem.
* Which files were changed.
* Which file was replaced.
* What configuration was updated.
* How the new algo was tested.

## Important

**This is NOT a request to develop a new trading strategy.**

I already have the strategy and the updated Python file.

The requirement is to:

**FIX THE KITE LOGIN → REPLACE THE EXISTING ALGO FILE → DEPLOY IT ON AWS → TEST IT → KEEP THE EXISTING STARTUP SYSTEM WORKING.**

Please quote a **fixed price for this work** and mention your previous experience with **Zerodha Kite Connect + Python + AWS algo deployment**.