In this video, you will see the updates and highlights of the past 2 weeks. We've a big change related to the content inside of our community. And I also explain why things have been quieter than usual from my side. P.S. Hope to see you in tomorrow's Q&A... we will be talking about GitHub Actions!

In this assignment, I created an S3 bucket in the region eu-west1, and enabled Static website hosting. I uploaded the content in the Zip file attached to the lesson and enabled Cloudfront distribution (CDN) for low latency and high speed transfers using the bucket website end point as origin. Generated a bucket policy for Public Read Access. My Tech Blog is ready! 😎

So I managed to find the problem with the OIDC- I made a bloggy-type post which I forgot I didn't put on earlier!! 🤦🏼‍♂️ The AWS IAM role wasn't properly configured to trust GitHub Actions as an OIDC provider. Then I realised that I needed to change the AWS region code to eu-west-1 (Ireland) for it to work! Then that was done and I was holding my breathe that it would all work well enough to not get an email! So far so good! Or was it? In a word, no. What had happened is when the actions tried to configure with the AWS credentials and assume a role using OIDC, it wouldn't allow it as it wasn't authorised. Cue the deep dive in the AWS IAM OIDC whitepapers, GitHubActions Documentation and a keep on trucking attitude which was tested quite a lot!!!!!!! So I had some food and thought about things… I have done something wrong somewhere. This is the essence of DevOps, isn't it? Doing something then seeing it fail and then finding out why it didn't deploy??? Yes. I do think it is. I have heard from various sources (and read Medium regularly..) that if you get it right the first time then there is something wrong or you have not done enough and the output is only "Hello, World"!! Anyway! I went back to the drawing board and had a decent scour of the code, the IAM role and policies I had put in place to allow access and found that I might have to do something a bit different. I made a new branch gh-pages, and then sent the .yaml code to deploy there, rather than from the main. I have now got two branches, and this is the result! I got it to work! Wahoo and all the joy! But wait! This is only on the gh-pages branch! What about the main branch and the sts:AssumeRoleWithWebIdentity error I had been having? Yeah it hadn't changed that part! :-( So I had another re-scour of the IAM Roles, policies, then asked the wonderful people in Cloud Talents what could be the problem? Anoop suggested that I have a look at the GitHub Org and repo name but I could see that it was all ok. I was going to even make a new IAM Role and discard the previous one but held off doing that for the time being.

One of the things about GitHub Actions that I do like is the fact it does break down the errors into bite sized pieces where you can see exactly where the error has occurred! I am grateful for this as if I had to go through mountains of code to find that one little typo from earlier- my eyes would have fallen out and my brain exploded! (Also, compared to AWS codepipine, this makes more sense and being able to use VSCode rather than AWS Cloud9 has made things so much more streamlined and simpler to deal with rather than having two IDE’s running or whatever!) So, I am now looking for gh-pages (might change the name of it unless it becomes a bloody nuisance to do) and see how I can make it work a bit better. That or make a new branch(?) possibly could be the action of what I need to do. We’ll see how things pan out!!😀👍🏼 As I said before I was going to do something drastic. I removed gh-pages from the code altogether. It worked. The build actually worked!!!! Woohoo!! 🙌I have now got a working GitHub Actions workflow and I can now move onto the next section of the assignment!!!

So I have been working hard today trying to get the CI/CD pipeline up and running using GitHub Actions, and there have been a few issues that I have been able to sort out, but I am struggling with the OIDC allowing the GitHubActions role to be assumed as it wasn't authorised to do so. So I am going back and having a decent look at what I have done, using the whitepapers, stackoverflow (not as good as I had hoped....) and have finally given in and used Claude.ai for some help. I have also looked through some of what you guys have done on here and they are brill!!! I have tried to emulate some of the stuff on here but it's not working! I get to the deploy, and then when the actions try to assume the role the OIDC can't as it doesn't have the authorisation to perform the sts:AssumeRoleWithWebIdentity. It is somewhat frustrating and I am getting a bit annoyed... Or I might just be Hangry and need some food. 🤷🏼‍♂️