Note
Note: Please contact feature-releases@catonetworks.com for more information about enabling and using this feature.
You can deploy an app connector in Amazon Web Services (AWS) to provide secure access to private applications in your cloud environment. The app connector establishes a connection between your cloud environment and Cato, and once connected, you assign it in the CMA and associate it with the relevant app connector group.
The following is a high-level workflow for deploying an app connector in AWS:
- You create the App Connector object in the CMA
- Deploy the Cato App Connector from AWS Marketplace
- Assign apps to the connector
To create an app connector
- In the Access > App Connector page, click New.
- Enter the information in the General section, such as name and location.
- Under Type, click Virtual.
- In the Connector Group section, select an existing group from the list or enter a name to create a new group.
- Under Preferred PoPs, use the toggle to determine if you want the connector to use the preferred PoPs configured for the account (default), or manually enter the PoPs to which the connector should attempt to connect.
- Click Apply.
Once the app connector is created in the CMA, copy the serial number, as you will need to provide it when deploying the app connector in your cloud environment.
Use the automated Cato wizard in the Amazon Marketplace to create the virtual resources for the app connector and deploy it to AWS. The app connector image is publicly available in the Marketplace.
To deploy an app connector in AWS
- From the AWS Marketplace, search for Cato Networks App Connector, and click Launch.
- Under Network Configuration, determine if you want to deploy the App Connector in a new or existing VPC.
- If you select an existing account, in the Existing VPC dropdown, click on the relevant virtual network.
-
Select the subnets for the following interfaces (minimum subnet address space of /28):
- MGMT subnet – Management communication between the app connector and the AWS API
- WAN subnet - External WAN traffic for the app connector (Internet and Cato Cloud)
- LAN subnet - Internal AWS resources and traffic that are connected to the app connector
- Under Security Configuration:
- In the Existing External Security Group field, define the security group that controls inbound traffic over ports 443 and 22. To maintain good security posture, this should be limited to the smallest possible group of IP addresses
- In the Existing Internal Security Group field, define the security group that controls traffic from your internal network
- Under Instance Configuration:
- Select the Instance Type on which the app connector should run
- In the MyKeyPair field, select the key pair that you created to encrypt this connection
- In the Serial Number field, paste the value that you copied earlier from the CMA.
- Click Submit.
You can see your app connectors in the Access > App Connectors page.
0 comments
Please sign in to leave a comment.