An application group allows you to add applications that share the same global configuration. Global configurations such as the Datapath Version that was previously part of Resources is now available in the App Groups tab. Creating an app group with a specific configuration and then associating it with applications allows the configuration to be applied to all applications in that app group.
Currently, the app group policy allows you to configure the datapath version. As an example, applications running on the same datapath version can be included to be part of one app group.
By default, all Barracuda Managed applications in the Barracuda WAF-As-A-Service are moved to an app group called Production. You can create new groups and move applications to that group. The number of groups is limited to (N/10) +1 for an account, where N denotes the number of applications. For example, if there are 20 applications in an account, it will be possible to create up to 3 app groups. All the configured app groups along with the associated applications are displayed on the APPLICATIONS page.
The table below displays some examples of the number of app groups that are allowed for the number of applications:
Number of Applications | Max Allowed App Groups |
|---|---|
0-9 | 1 |
10-19 | 2 |
20-29 | 3 |
30-39 | 4 |
40-49 | 5 |
In the case of Custom Container deployments, applications become part of the app group associated with the custom container at the time of creation.
Changing the App Group for Applications Deployed using Managed Containers
You can move applications from one app group to another using the Change App Group option under ACTIONS on the APPLICATIONS page (applicable ONLY for Barracuda Managed Containers). If the application is moved to a different app group, the application is redeployed to the data path container associated with the specified app group. The new configuration will be based on the datapath version 12.1.
Changing the App Group for Applications Deployed using Custom Containers
To change the app group for custom containers, go to the Container Management page under RESOURCES > WAF CONTAINERS. After the app group is changed, all applications using the container will move to the changed app group. When you create a new custom container, associate the container with an existing app group. If the app group is not selected, the Barracuda WAF-as-a-Service associates the default app group with the container. For more information on custom container deployments, see the Getting Started – Using Your Own Containers article.
Adding an App Group
Perform the following steps to add an app group:
On the Barracuda WAF-as-a-Service web interface, go to the APP GROUPS tab.
Click Add New. The Add New App Group window appears.
On the Add New App Group window, do the following:
App Group Name – Specify a name for the app group.
Create Using – Select the type of app group that you want to create.
Basic App Group – Creates an app group with the basic configuration.
Clone Existing App Group – Use an existing app group from the drop-down list to clone the configuration settings to the new app group.
Click Add.
Set the Default App Group
By default, the Barracuda WAF-as-a-Service sets Production as the Default app group for all applications. You can create the app group and mark it as default using the Mark as default app group option under ACTIONS on the App Groups page. If you do not provide the app group name when creating an application, the application will be moved to the Default app group.
Renaming and Deleting the App Group
To rename an app group, use the Rename option, and to delete the app group use the Delete option under ACTIONS. A group cannot be deleted if an application is associated with it. Ensure that no applications are associated with the group before you perform the delete action.