It was a rewarding experience to explore and experiment with different git command line options while managing the remote repo in GitHub. This learning journey was both fun and insightful. Here is the link to my GitHub Repo: https://github.com/anoopjayadharan/tech-blog Steps Followed: 1. Created a new branch named "feature/development" 2. Made changes to the "hugo.toml" file 3. The changes were committed to Git and tested using the local Hugo server 4. Pushed new file to GitHub. 5. Opened a Pull Request(PR) 6. Reviewed and merged the changes into the "main" branch. 7. Back to the local machine, checked out to the main branch and executed a "git pull" to maintain the updated copy. 8. Verified Git logs

I completed this assignment! - Created an S3 Bucket and Enabled Static Website Hosting. - Uploaded Content from the Course Resources: Faced an issue with loading the website as I uploaded the zipped files. I manually unzipped and re-uploaded due to the small project size. For larger projects, zipped uploads would require AWS CLI scripts for extraction. - Set Up a CloudFront Distribution: Created a distribution and a function to resolve website loading issues. - Personalized the Website: Made edits to customize the site.

After completing week 2, assignment 1, where we set up a tech blog and edited some code on Hugo, it got me thinking—how often do DevOps engineers work with source code? Is being proficient in programming languages a necessary skill? Honestly, I’m not a big fan of programming.

Hello everyone, I am Aman from India. Where are you from? Let's know about each other

When attempting to set up my landing zone using AWS Control Tower, the process failed to complete even after launching an EC2 instance. I kept receiving the error: "AWS Control Tower failed to set up your landing zone completely: AWS Control Tower setup failed. Be sure your account is subscribed to the AWS EC2 service, then try again." After researching the issue on various forums, I discovered that the problem stemmed from the virtual card I used during the account setup, which made my subscription invalid. I resolved the issue by obtaining a new virtual card, updating my billing information on AWS, and retrying the landing zone setup. This time, the setup completed successfully.