
Building a portfolio is one thing, but deploying it and making it accessible on the internet is where the real learning begins.
I recently deployed my personal portfolio using AWS, and through this process I got hands-on experience with cloud deployment, AWS services, configuration, permissions, and making a project production-ready.
I started by developing and testing my portfolio locally. Once everything was working as expected, I prepared the project for production and created the required build files.
Then came the AWS part. I created and configured the AWS resources required to host my portfolio. After configuring the necessary permissions and settings, I deployed the production build to AWS.
One thing I quickly realized was that deployment isn't always as simple as uploading files and opening a URL. I had to deal with configuration, permissions, deployment settings, and a few issues along the way. Each error helped me understand a little more about how AWS works behind the scenes.
After successfully deploying the application, I configured the required settings to make the portfolio accessible through the web. I also verified that the pages, navigation, assets, and other functionality were working correctly after deployment.
The final result was my portfolio running on AWS
This experience helped me understand the difference between simply building an application locally and actually deploying it as a production application. More importantly, I got practical exposure to AWS rather than just learning the services theoretically.
Top comments (0)