Legacy methods for AWS environments
This section only applies to AWS environments added to Sophos Cloud Optix prior to November 2020
You must only use this help section if you opened your Sophos Cloud Optix account before November 17, 2020. If you opened your account after that date, you must use the instructions under Add your AWS environment.
The documentation shows you how to add environments by the following methods:
- Legacy: AWS Quick-start.
- Legacy: Add AWS environments using CLI scripts.
- Legacy: Add AWS environments using AWS CloudFormation, with or without Legacy: Add AWS environments with AWS Organizations.
You can also add environments using a Terraform template supplied by Sophos.
To find out which resources Sophos Cloud Optix creates in your AWS environments, see Legacy: Resources created in your AWS environments.
After adding your AWS account to Sophos Cloud Optix, you can add Amazon Elastic Kubernetes Service (EKS) clusters. You must add these clusters to Sophos Cloud Optix separately, using the Amazon CLI script provided by Sophos. See Legacy: Add your Amazon EKS clusters.
Before you add AWS environments you must be aware of the following points:
- By adding your AWS environment, you authorize Sophos to access information via APIs and to collect log data from your environment. Your cloud provider may charge you for this. Contact them for details. See Cloud provider charges.
- AWS regions that aren't connected to the global AWS infrastructure, including AWS GovCloud (US) and AWS China, are not supported.
- Sophos Cloud Optix doesn't support AWS's legacy EC2-Classic platform, which was deprecated in 2013. You can add AWS environments that are on the EC2-VPC platform.