We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

How to Deploy the Barracuda Email Security Gateway on Amazon Web Services

  • Last updated on

Create a Persistent Public IP Address for Your Barracuda Email Security Gateway 

When an instance of your Barracuda Email Security Gateway appliance is created, a public IP address is associated with the instance. However, this IP address can change if the instance is stopped. To create a persistent IP address, see Configuring an Elastic IP Address for an Instance.

Launch the Barracuda Email Security Gateway Instance on Amazon Web Services

  1. From the Amazon Web Services (AWS) Management Console:

    1. Log into the AWS Management Console and open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
    2. From the top right corner of the page, select the region for the instance. This is important because some Amazon EC2 resources can be shared between regions.
        
      region.jpg

  2. Click Launch Instance.

             launch_instance.jpg

  3. In Step 1: Choose an Amazon Machine Image (AMI) page, select AWS Marketplace and search for the Barracuda Email Security Gateway AMI. Click Select next to the Barracuda Email Security Gateway AMI. 

             ChooseAmazonImageSpam.png

  4. In Step 2: Choose an Instance Type page, select an instance type from the All Instance types or General purpose table. Click Next: Configure Instance Details to continue.

    See the Amazon Web Services article to verify the recommended instance type for your Barracuda Email Security Gateway sizing. Select the recommended instance type. Important: If you need to add additional storage space after deployment, due to the Amazon Web Services (AWS) structure, the only current option is to redeploy and restore the configuration on a larger instance.


             instance_type.jpg

  5. In Step 3: Configure Instance Details page: 

    1. Enter the Number of instances you want to launch.
    2. Select the appropriate Network from the list.
    3. Select the appropriate Subnet from the list, or keep the default subnet.
    4. In the Advanced Details pane, keep the default setting for all parameters and click Next: Add Storage.

      instance_details.jpg

  6. In Step 4: Add Storage page, the table displays the storage device settings for the instance. Modify the values if required and click Next: Tag Instance.

             add_storage.jpg

  7. In Step 5: Tag Instance page, add/remove the tags for the instance (if required).

             tag_instance.jpg

  8. In Step 6: Configure Security Group page, choose Select an existing security group to select and assign the security group(s) from the existing list, or choose Create a new security group to create a new group (refer to Creating a Security Group on Amazon Web Services for more information). Click Review and Launch.

    By default, the Barracuda Email Security Gateway web interface listens on port 8000 for HTTP and port 443 for HTTPS. Make sure these ports (8000 and 443) are added to the Inbound Rule of the security group associated with the Barracuda Email Security Gateway. Also add the port(s) through which you configure the Service(s) for this instance.


    config_security_group.jpg

  9.  In Step 7: Review Instance Launch page, review your settings before launching the instance, and then click Launch

             ReviewInstanceLaunch.png

Amazon Web Services now provisions the Barracuda Email Security Gateway. Allow a few minutes for the Amazon Web Services Agent and the Barracuda Email Security Gateway virtual machine to boot up.

DO NOT restart the Barracuda Email Security Gateway while it is launching.

Continue with  Barracuda Email Security Gateway Quick Start Guide for Amazon Web Services to license and configure your virtual appliance.

 

Last updated on