FLASK PYTHON POSTGRESQL AWS EC2 NETLIFY REACT TAILWIND
Design comparison
Solution retrospective
I'm most proud of successfully building and deploying the LinkDev project—a comprehensive link-sharing platform that integrates a React frontend hosted on Netlify with a Flask backend on AWS Elastic Beanstalk. This required careful planning of API endpoints, CORS configuration, and cookie-based authentication for secure cross-origin communication. Despite technical challenges, such as managing SameSite cookie policies and ensuring CSRF protection, I managed to create a functional system that handles user sessions, token-based authentication, and a clean frontend user experience. Next time, I would focus on a domain-first approach by securing an HTTPS-enabled custom domain earlier in the project timeline. While waiting for the domain and SSL certificate has delayed the ability to showcase the platform, planning for HTTPS integration earlier could have avoided issues with mixed-content blocking, cookie rejection, and cross-origin request restrictions during development🥲🥲.
What challenges did you encounter, and how did you overcome them?Challenge: Delays in securing the custom domain via AWS Route 53 and obtaining the SSL certificate have impacted the ability to showcase a production-ready HTTPS-secure website. Problem with creating PuttY for my connection AWS CLI and then modifying nginx configuration on my EC2 instance where my backend is locating
What specific areas of your project would you like help with?Maybe allow me to ask questions about the backend part and specially about AWSconfiguration (like route 53 hosted zone creation and registration of the domain😊)
Community feedback
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord