Check the Results

Step 1: Trigger deployment by publishing a release tag

The root GitHub Actions dispatcher workflow is configured to trigger automatically whenever a Git tag matching the v* pattern is pushed to the repository.

1. In your web browser, navigate to your aws-fcaj-container-app repository on GitHub.

2. In the right-hand sidebar of the repository home page, click Tags.

   

3. On the releases page, click Create a new release.

   

4. Click the Choose a tag dropdown menu.

5. In the input field, enter v1.0.1.

6. Select Create new tag: v1.0.1 on publish.

   

7. In the Release title field, enter v1.0.1.

8. Click Publish release.

   

git tag -a v1.0.1 -m "Release v1.0.1"
git push origin v1.0.1

Step 2: Monitor GitHub Actions pipeline execution

1. In your GitHub repository, click the Actions tab in the top navigation bar.

2. Under All workflows, select the workflow run triggered by your release tag v1.0.1.

   

3. Review the workflow summary graph. The pipeline executes two build jobs in parallel followed by their respective deployment jobs:

   • Backend Build & Push -> Backend Deploy
   • Frontend Build & Push -> Frontend Deploy

   

4. Click into Frontend Build & Push to inspect the container packaging steps:

   • Checks out the repository source code.
   • Configures AWS credentials using repository secrets.
   • Logs into Amazon ECR.
   • Builds the frontend Docker image and pushes it to Amazon ECR with the tag v1.0.1.

   

5. Click into Frontend Deploy to observe the deployment automation:

   • Sets up the job environment and checks out the deployment scripts.
   • Configures AWS credentials.
   • Deploys the new revision to Amazon ECS and initiates the rolling update.

   

Step 3: Inspect deployment artifacts in the AWS Management Console

Verify that the automated pipeline successfully updated all target cloud resources in AWS.

1. Verify container images in Amazon ECR

1. Open the Amazon ECR console in your target AWS Region.

2. In the left navigation menu, click Repositories and select aws-fcaj-container-app-frontend.

3. Confirm that an image tagged v1.0.1 exists with a recent push timestamp.

   

2. Verify task definitions in Amazon ECS

1. Open the Amazon ECS console.

2. In the left navigation menu, click Task definitions.

3. Select FCAJResbar-task-fe and verify that a new active revision has been registered pointing to the frontend container image tagged v1.0.1.

   

4. Return to Task definitions and select FCAJResbar-task-be. Confirm that a new active revision has been registered for the backend task definition.

   

3. Verify Amazon ECS service deployments

1. In the Amazon ECS console, navigate to Clusters and select FCAJ-Lab-cluster.

2. Under the Services tab, select app-frontend.

3. In the Service overview card, verify ECS service app-frontend has been deployed successfully.

   

4. Return to Services and select app-backend.

5. Verify that ECS service app-backend has been deployed successfully.

   

Step 4: Verify the application in your browser

1. In the AWS Management Console, navigate to the Amazon EC2 console.

2. In the left navigation menu, click Load balancers and select FCAJ-Lab-alb.

3. In the Details tab, locate and copy the DNS name

4. Open a new web browser tab and navigate to DNS name of FCAJ-Lab-alb

5. Log in to the application.

6. Inspect the sidebar navigation menu under the user profile photo.

7. Confirm that the dashboard navigation item displays Dashboard v1.0.1 (reflecting your code update from Section 4.1).