Integrate Arm Virtual Hardware into CI/CD workflow 2
Introduction
Prepare AWS account for GitHub integration
Automate build and validation example
Next Steps
Integrate Arm Virtual Hardware into CI/CD workflow 2
Who is this for?
This is an advanced topic for DevOps integrating AVH into their CI/CD flows
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Prepare AWS account for GitHub integration
- Integrate Arm Virtual Hardware into CI/CD flow with GitHub Actions
Prerequisites
Before starting, you will need the following:
- This learning path builds on Integrate Arm Virtual Hardware into CI/CD workflow 1 .
- Valid AWS and GitHub accounts are required
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll extend Arm Virtual Hardware (AVH) integration by preparing an AWS account with a CloudFormation stack and connecting it to a forked GitHub repository that runs automated build and validation on AVH. First, you’ll fork the
ARM-software/AVH-GetStarted project, deploy the included CloudFormation template, and configure GitHub Actions with repository secrets. The settings include the AWS region used by the stack and a valid VPC subnet ID obtained from the AWS console. After configuration, you’ll run the workflow in GitHub Actions to drive tests on AVH, providing a clear sequence from account setup to automated validation.Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Fork the
repository
and clone your fork. The example includes a template to help set up your AWS account and documentation for the CI workflow.
Deploy the CloudFormation stack using the template provided in the example project. After creating the stack, proceed to define the repository secrets in GitHub.
Use the same AWS Region where you created the CloudFormation stack. The region must match for the workflow to reference the correct resources.
In the AWS console, go to VPC > Subnets and select any valid Subnet ID. Copy that ID into the
AWS_SUBNET_ID repository secret.In your forked repository, go to Settings > Secrets > Actions, then choose New repository secret. The secret names must match exactly as specified in the Learning Path.