Lab 3

  • 17 February 2022
  • 0 replies

Userlevel 5


In this lab you will adopt a CI/CD pipeline for making secure changes to your cloud infrastructure using the Aviatrix Multi-Cloud Networking and Security platform.

Specifically, you will implement Egress FQDN Security by collaborating with Applications Development and InfoSec teams. The Developers will be making changes to a single file whenever they need to make changes to the FQDNs that their app needs egress access to. We are using the term Day 2 for the work done in this lab.

Here is an overview of the tasks:

  • Refer to the infrastructure built in Lab 1 and Lab 2
  • Fork new ACE code for this lab as a remote repository in your own account
  • Personalize the code for your accounts
  • Invite Collaborators for the Repository
  • Create a new GitHub Branch where code changes will be made, and then secure the main branch with Branch Protection Rules
  • Connect GitHub with Terraform Cloud via an API-driven workflow

You will implement Egress Security by collaborating with your DevOps and SecOps teams. The DevOps team will add FQDNs to the file in a new GitHub branch that their app needs to access. They will then create a Pull Request (PR) in GitHub. The PR will need to be approved by the SecOps team prior to being merged into the main branch. Branch protection rules enable checks and balances for the organization. By having such guard rails, no single entity can bring down the entire infrastructure with Terraform.

The workflow is represented here.


Fork ACE code for this lab

While logged into your GitHub student account, create a new repository by visiting

Click Fork in the top-right corner of the browser.

This will create a remote repository (aka repo) of the lab code in your own GitHub account.

Code Review

Here is how each file has a purpose in this Lab:

  • - DevOps team maintains this file. This file defines FQDNs that the app needs access to. The DevOps team will know best what domains their app needs to reach out to, so they are the 'owners' of this file. They will need to make sure the formatting (white space, etc) of each line specifying an FQDN is consistent because GitHub Actions will check this, and fail if the code is not represented in a canonical format. Read this doc for more info on terraform fmt.
  • - This file states where your Terraform runtime (aka execution) and State should reside. We are using a Remote Backend in which both of these will reside in a Terraform Cloud workspace. You will need to edit this file appropriately
  • - This creates an Egress FQDN allowlist tag called APP-RULES, applies it to the Spoke gateway in Azure, and associates TCP and UDP rules to the tag.
  • - specific information about the Aviatrix Terraform provider that we are using in this training. All resources in this repository leverage the Aviatrix provider. Only a pointer to the Controller IP is specified in this file in Lab 3. In Lab 1 and Lab 2, this file also had Terraform variables for the credentials for the Controller. Both methods are valid. 
  • - Any variable with optional default values are provided here. Additionally, if a variable needs to have a non-default value, you would specify it in the Terraform Cloud Variables section.
  • - specific version about the provider versions. 

Personalize the code for your accounts

Edit ace-iac-day-two > (<your-account>/ace-iac-day-two/blob/main/

Click the Pencil icon to edit directly on cloud UI

Uncomment this line:

# organization = "<replace-with-your-Terraform-Cloud-organization-and-uncomment>"

Edit it with the username of your Terraform Cloud organization account.

Commit the changes directly to the main branch.

Next, edit ace-iac-day-two > .github > CODEOWNERS (<student-account>/ace-iac-day-two/blob/main/.github/CODEOWNERS)

Click on the Pencil icon to edit directly on cloud UI

Edit the line for this CODEOWNERS file to specify the ACE SecOps GitHub account as the Owner. For example, @ace-secops

Edit the other 4 lines and specify the Student’s own GitHub account (NetOps role).

Commit the changes directly to the main branch.

Invite Collaborators for the Repository

Remember that you are playing the Network Operator role and will need to invite the DevOps and SecOps personas as Collaborators to your Repository.

  1. Click on Settings > Collaborators > Manage access. Make sure these are the Settings for the Repository, not the Settings for your account. 
  2. Click on Invite a collaborator.
  3. Invite your GitHub account that will serve the purpose of the DevOps.
  4. Click on Invite a collaborator again.
  5. Invite your GitHub account that will serve the purpose of SecOps.
  6. Check the email for your respective accounts for DevOps and SecOps and approve the invitations to become a collaborator for your Network Operator Repository.

Create, Automate, and Secure a Branch

Create a new branch called updates

Automate workflows on the branch by configuring GitHub Actions

Click Actions

Click I understand my workflows, go ahead and enable them

Secure the main branch by creating a Branch Protection Rule. This will ensure that only the GitHub account(s) mentioned in the CODEOWNERS file are authorized to review/approve the Pull Request.

  • Click on Settings > Branches > Add rule
  • Name the Branch Name Pattern main
  • Check the following 7 fields:
  1. Require pull request reviews before merging
  2. Require approvals
  3. Dismiss stale pull request approvals when new commits are pushed
  4. Require review from Code Owners
  5. Require status checks to pass before merging
  6. Require branches to be up to date before merging
  7. Include administrators

By setting this up, you are adding several layers of security to the main branch which is where Terraform will be looking at for terraform apply.

Terraform Cloud

Set up workspace

Create a new Workspace.

Select API-driven workflow.

Name the workspace ace-iac-day-two and click Create workspace

Configure Variables

Navigate to the Variables tab and add these credentials for accessing the Controller as Environment Variables:


Mark the value for AVIATRIX_CONTROLLER_IP and AVIATRIX_PASSWORD as sensitive.

As a learning exercise, note that the credentials for accessing the Aviatrix Controller are defined as Environment variables in this Lab. However, in Lab 1 and Lab 2, the credentials were instead defined as Terraform variables that were called in the file. Both methods are valid.


Connect GitHub Repo and Terraform Cloud via API

Finally, generate an API Token in Terraform Cloud and specify it as a new Secret for your GitHub Repository.

Terraform Cloud side

Go to the Tokens page in your Terraform Cloud User Settings. Make sure you are in the Settings for your User account (accessible from the upper right corner of the page), not the Settings for your Organization (typically visible in the center of the top menu).


Click on Create an API token and generate an API token named GitHub Actions.

Save the token in a safe place. You will add it to GitHub later as a secret, so the Actions workflow can authenticate to Terraform Cloud.

GitHub side

Back in GitHub, for the repository (not the user), navigate to Settings > Secrets > Actions.

Create a New repository secret named TF_API_TOKEN, setting the Terraform Cloud API token you created in the previous step as the value.

Now your Terraform Cloud account and the repository in your GitHub account are securely linked via API.

Collaboration with other stakeholders

Work done by DevOps team

Please check your work carefully for any errors. If all looks good, navigate to the browser window where you are logged on in GitHub as the DevOps team.

Since Branch Protection Rules are in place for the main branch, make sure you navigate to the updates branch to make any changes. Click on the file in the updates branch to request access to a new FQDN.

Click on the Pencil icon to edit directly on cloud UI

Below the two existing lines for aviatrix, add the following line:

      "*"   = "80"

Make sure the formatting (white spaces and alignment) matches the two existing lines. Otherwise, the GitHub Actions check will fail. GitHub Actions is configured for best practices, which is to check for formatting inconsistencies. As an FYI, this file is ace-iac-day-two > .github > workflows > terraform.yml, but it is beyond the scope of this training to go into the configuration and syntax of this file.

Next, click Commit changes:

After the DevOps account makes the code change, they need to create a Pull Request (PR) on the branch. Click New pull request.

Make sure you select the main branch of your repository (NOT the one that you forked) as the base and the updates branch as the compare.

Add relevant comments and then click Create pull request one more time.

GitHub Actions will then automatically do some checks for formatting, and then notify the SecOps GitHub account that their Approval of the PR is pending.

You can click on Details to see the progress at any point.

Work done by SecOps team

Now you can navigate to the browser window where you are logged on in GitHub as the SecOps team to approve the PR.

Specifically, navigate to Pull requests > Review requests and click on the request.

Click Add your review.

Click Review changes one more time. If you are okay with the changes, click the Approve button and the Submit review.

Once the SecOps team has Approved the PR, it will look like this:

Now, any team can Merge the PR back into the Main branch. Upon doing so, GitHub Actions will trigger a Deployment (CD part of Continuous Deployment), which is a terraform apply and the Network Team can monitor the progress of the apply on Terraform Cloud.

At any time in this workflow, you can see the status of the GitHub Actions by clicking on Actions in GitHub.

On the Controller, you should now see the new rule in your Egress FQDN filter.

Final Thoughts

Congratulations! You have just built, enhanced, and secured a multi-cloud network by using automation. By using git branches and enabling collaboration with DevOps and SecOps teams to build CI/CD pipelines with secured branches, you have experienced true NetOps in action. Many of Aviatrix's largest customers practice IaC day in and day out. While the choice of tools (e.g. Jenkins instead of Terraform Cloud, GitLab instead of GitHub) may vary across enterprises, the concepts of Infrastructure as Code remain the same.

Be sure to clean up your resources to avoid any excess charges.

0 replies

Be the first to reply!