Fix/redis connection failure

[JohnPraveenYL]

Description

This PR resolves the 29-second timeout issue (502 Bad Gateway) encountered during AWS Serverless deployments. By optimizing the agent's execution speed and increasing the available compute resources.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update
• CI/CD update
• Other (please describe):

Related Issues

no response from

Fixes #
Fixes the AWS API Gateway timeout errors caused by slow agent initialization and execution.

Changes Made

• Increased Lambda Memory: Upgraded the AWS Lambda memory allocation to 1024 MB (1 GB) to provide more vCPU power, significantly reducing cold start and initialization times.
• Optimized Prompts: Adjusted the agent prompts to remove unnecessary reasoning steps, reducing the overall LLM generation time and speeding up the final response delivery.

Testing

• Unit tests pass locally
• Integration tests pass locally
• Manual testing completed
• New tests added for changes

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Notes