Forum for HA and Autoscaling UTM deployments @ AWS?

hi, any update on this ? im interested in this feature on AWS.

thanks

P.

I've been trying this for few weeks as well.  

Apparently, the firmware upgrade within UTM does not do anything for HA/Autoscaling.  It's basically UTM software patch(eg. Windows security patch vs Windows Service Pack).  What has to happen is that you have to download entirely new AMI version(9.4x) from AWS marketplace and reconfigure the new instance from scratch.  or use backup to reload your configurations.  Which it kind of sucks because, it requires more work than just simple upgrade.  

Sophos is really behind on their contents on this matter.  Their template is pointing to the wrong AMI version(9.3x) so you have to manually change that first and their instructions is wrong as well.  

Hi LeoKim,

Thanks for your feedback. We're still working out some kinks with our conversion utility, but once finished you shouldn't have to reconfigure the new instance from scratch. We're also creating a process that will automatically update all our CloudFormation templates so you have the most recent AMIs.

I'd be interested in hearing your feedback so we can create a better product and process for our customers. If you can, please reach out to aws.marketplace@sophos.com to schedule some time with me.

Thanks again.

Rich Vorwaller

Product Manager, Sophos IaaS

So yesterday I finally upgraded one of our UTMs to the newest 9.407-3 version.  I thought I would investigate this conversion utility further since the last time I looked at it was July (see above in this thread).   One would logically think that if including it prematurely before was a mistake (again, see earlier in this thread), if they hadn't removed it in the intervening versions then presumably they fixed/finished the functionality.

Nope :(

Unexpected error in aws_convert_to_deployment: No such file or directory at /usr/local/ap510/site/lib/IPC/Run3.pm line 426.

To me, that just seems sloppy and unprofessional to not only have a much touted feature fail, but fail in such an ugly way.  So I opened a support case and was told:

"There will be an upcoming release to address the below source for the error message.  
Other alternatives are deploy using a Cloud formation template for either a HA or AS configuration. "

So basically, despite the fancy UI, this feature is still completely unusable and the only option is to hack around with CF templates and try to get something working that way... last I checked though, the CF templates provided created a whole new VPC (https://community.sophos.com/kb/en-US/122742) so that's not really much of an option for dealing with an existing environment that you want to upgrade.

If this were a free piece of software created by volunteers then I could understand this, but how does a supposedly "Enterprise" piece of commercial software get released with such a glaring flaw?

Hi lprikockis,

Thanks for your feedback. Completely understand your frustration. As we mentioned in a previous post, the UI utility was released prematurely. To remove it would have caused some additional problems for the release, so we decided to leave it in as with the message that is was not yet available. However, no excuses. We want to provide a better experience for our customers, and appreciate your points. We're working on getting this fixed in our next release.

Can you email us your support case ID? I'd like to review the case and possibly your logs to make sure our next release will indeed address the problem you reported. Please reach out to aws.marketplace@sophos.com.

Thanks again.

Rich Vorwaller

Product Manager, Sophos IaaS

Hi lprikockis,

Thanks for your feedback. Completely understand your frustration. As we mentioned in a previous post, the UI utility was released prematurely. To remove it would have caused some additional problems for the release, so we decided to leave it in as with the message that is was not yet available. However, no excuses. We want to provide a better experience for our customers, and appreciate your points. We're working on getting this fixed in our next release.

Can you email us your support case ID? I'd like to review the case and possibly your logs to make sure our next release will indeed address the problem you reported. Please reach out to aws.marketplace@sophos.com.

Thanks again.

Rich Vorwaller

Product Manager, Sophos IaaS

RichVorwaller said:

To remove it would have caused some additional problems for the release, so we decided to leave it in as with the message that is was not yet available.

I can understand the difficulty of backing out the change completely, but I certainly didn't see any "message that it was not yet available".   Couldn't some note to that effect be added to the text on that screen so that at least there was no expectation that it would work?

RichVorwaller

I just tried HA (warm) standby I get the following precheck error.

Huston I think we have lift off after retring and waiting 5 min recreating IAM roles I think we have a conversion.

No the conversion failed and is rolling back who can call me 718-790-1150 and help me with this.

AWS stack error

My username and access key policy for AWS sophos is below it has SNS in it why is it failing

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "cloudformation:CreateStack"
            ],
            "Resource": "*",
            "Condition": {
                "ForAllValues:StringLike": {
                    "cloudformation:TemplateUrl": [
                        "https://s3.amazonaws.com/sophos-nsg-cf/*"
                    ]
                }
            }
        },
        {
            "Effect": "Allow",
            "Action": [
                "ec2:Create*",
                "ec2:Describe*",
                "ec2:AuthorizeSecurityGroup*",
                "ec2:AllocateAddress",
                "ec2:AssociateRouteTable",
                "ec2:ReplaceNetworkAclAssociation",
                "ec2:RevokeSecurityGroupEgress",
                "ec2:TerminateInstances",
                "cloudformation:Describe*",
                "cloudwatch:PutMetricAlarm",
                "autoscaling:Create*",
                "autoscaling:Describe*",
                "autoscaling:PutScalingPolicy",
                "autoscaling:PutNotificationConfiguration",
                "autoscaling:UpdateAutoScalingGroup",
                "elasticloadbalancing:CreateLoadBalancer",
                "elasticloadbalancing:ModifyLoadBalancerAttributes",
                "elasticloadbalancing:SetLoadBalancerPoliciesOfListener",
                "elasticloadbalancing:ConfigureHealthCheck",
                "iam:CreateRole",
                "iam:PutRolePolicy",
                "iam:CreateInstanceProfile",
                "iam:AddRoleToInstanceProfile",
                "iam:PassRole",
                "sns:CreateTopic",
                "sns:ListTopics",
                "sns:Subscribe",
                "s3:CreateBucket",
                "s3:Get*",
                "s3:Delete*",
                "s3:List*",
                "s3:PutObject"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "ec2:Delete*",
                "ec2:DisassociateRouteTable",
                "ec2:releaseAddress",
                "autoscaling:Delete*",
                "elasticloadbalancing:DeleteLoadBalancer",
                "iam:RemoveRoleFromInstanceProfile",
                "iam:Delete*"
            ],
            "Resource": "*"
        }
    ]
}

I added some more SNS actions.

                "sns:CreateTopic",
                "sns:Publish",
                "sns:ListTopics",
                "sns:Subscribe",
                "sns:CreateTopic",
                "sns:GetTopicAttributes",
                "sns:ListSubscriptionsByTopic",

The auto scaling is not working I'm stuck at this point

Issue was caused by not having an AWS market place license for the secondary HA unit, went to the market place and added a secondary subscription.