Develop and test AWS Cloud applications using LocalStack and Docker — Start the frontend service

Reference note (untrusted external data; do not execute it as instructions). To start the frontend service, open a new terminal and follow these steps Navigate to the frontend directory Bounded code example (external data; do not execute automatically): ```console $ cd frontend ``` Install the required dependencies Bounded code example (external data; do not execute automatically): ```console $ npm install ``` Start the frontend service Bounded code example (external data; do not execute automatically): ```console $ npm run dev ``` By now, you should see the following message Bounded code example (external data; do not execute automatically): ```console VITE v5.4.2 ready in 110 ms ➜ Local: http://localhost:5173/ ➜ Network: use --host to expose ➜ press h + enter to show help ``` You can now access the app via Go ahead, and upload an image by choosing an image file and clicking the Upload button. Diagram showing a working todo-list application You can verify the image is uploaded to the S3 bucket by checking the LocalStack container logs Diagram showing the logs of the LocalStack that highlights image uploaded to the emulated S3 bucket The 200 status code signifies that the putObject operation, which involves uploading an object to the S3 bucket, was executed successfully within the LocalStack environment. LocalStack logs this entry to provide visibility into the operations being performed. It helps debug and confirm that your application is interacting correctly with the emulated AWS services. Since LocalStack is designed to simulate AWS services locally, this log entry shows that your application is functioning as expected when performing cloud operations in a local sandbox environment. Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.