{"pageModel":{"attributes":{"id":"","name":"120693.dita","viewName":"DitaDetail"},"elements":{"ditaContent":{"name":"DITAContent","value":"
\r\n

Deploy a Connector in AWS

\r\n
\r\n

A resource connector is a lightweight service deployed in a virtual machine in your cloud environment.\r\n A resource connector manages the network communications to a configured private resource.\r\n Cisco Secure Access provides a pre-configured resource connector image for Amazon Web Services (AWS).\r\n This guide describes the steps to deploy an Amazon Machine Image (AMI) to create your resource connector instances.\r\n

\r\n
\r\n

Prerequisites

\r\n

Gather the required information, and understand and meet the Requirements and Prerequisites for Resource Connectors and Connector Groups.

\r\n
    \r\n
  • An AWS account.
    • \r\n
  • Supported architectures:
      \r\n
    • Intel x86_64
      • \r\n
    • AMD64
      • \r\n
    \r\n
    • \r\n
  • Required instance type for deployments in production environments: C5.xlarge
    • \r\n
  • Create the connector group in the region nearest to the geographical location where you will deploy these connectors.
    • \r\n
  • All connectors in a group must use the same environment, for example: AWS.
    • \r\n
  • Obtain the connector image from the AWS marketplace. For more information, see Get Connector Images on the AWS Marketplace\r\n
    • \r\n
  • Copy the provisioning key for the specific connector group where you will deploy these connectors. For more information, see Provisioning Keys for Resource Connectors.
    • \r\n
  • Disk encryption is recommended for your connectors. You configure this during connector deployment, but you should complete any prerequisites before deploying the image. For more information, see the AWS documentation.
    • \r\n
\r\n
\r\n
\r\n

UEFI Secure Boot Environment for Resource Connector Images

\r\n

The Secure Access Resource Connector images for AWS support UEFI Secure Boot, which provides a trusted boot environment for the connector instance.\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
\r\n\r\n
 		\r\n
If you choose an AWS instance type that is not recommended by Cisco Secure Access, we can not guarantee that your Resource Connector instance can boot in AWS. Review the AWS documentation to verify whether your instance type supports UEFI Secure Boot.
\r\n
\r\n
    \r\n
  • You can deploy Resource Connector images with UEFI Secure Boot on these architectures:
      \r\n
    • Intel x86_64
      • \r\n
    • AMD64
      • \r\n
    \r\n
    • \r\n
  • We recommend that you redeploy your Resource Connector instances with the UEFI Secure Boot environment.
    • \r\n
\r\n
\r\n
\r\n

Save Your Private SSH Key

\r\n

After you generate an SSH key pair required for access to the resource connector, you must save your SSH key in your environment.

\r\n

Cisco cannot recover your SSH key and you will lose remote access and the capability to manage the resource connector.

\r\n
\r\n
\r\n

What's Next

\r\n

Perform the following tasks once per connector instance. You can use the Cisco Secure Access Resource Connector image to create multiple connector instances. You must deploy each connector instance independently.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
\r\n\r\n
 		\r\n
Do not clone the connector instances.
\r\n
\r\n\r\n
\r\n
\r\n
\r\n","ditaVal":"","format":"html"},"bookTitle":{"value":""},"shortDescription":{"value":""}}},"parameters":{"appId":"SecureAccess","topicAlias":"deploy-a-connector-in-aws"}}