Shifting Backend to AWS

[Yashrajdps13]

Currently, our Flask backend is hosted locally, which limits the efficiency of development and testing due to manual deployment and local resource constraints. To streamline the development workflow and provide real-time feedback, we propose migrating the Flask backend to AWS.

By leveraging AWS, we can benefit from:

• Automatic scaling: AWS will handle variable traffic loads, ensuring smooth performance.
• Simplified testing: Testers and developers can access the same environment, reducing discrepancies between local and production environments.
• Real-time feedback: CloudWatch and other AWS tools can provide real-time insights into performance and issues.

Proposed Solution

1. Set up EC2 or Elastic Beanstalk for hosting the Flask application.
2. Configure S3 for storing static assets, logs, or any required resources.

[dev04sa]

@Yashrajdps13 , go for it.