Download Amazon VPC

Setup On the Site-to-site VPN > Amazon VPC > Setup page you add connections to your Amazon Virtual Private Cloud (VPC). You can either import all connections configured with one Amazon Web Service (AWS) account and using the IP address of your Sophos UTM as Customer Gateway (Amazon term for your endpoint of a VPC VPN connection). Or you add connections one by one using the configuration file which you can download from Amazon. Import Via Amazon Credentials You can import all connections configured within your VPC and use the IP address of your Sophos UTM as the Customer Gateway. You will need to create AWS access keys and secret keys to import the configuration. Note – For more information, see the AWS Documentation. Note – All existing connections listed in the Status tab will be deleted during the import. The key pair you are required to enter for the import must belong to an AWS user with sufficient privileges. You can use the predefined policy AmazonVPCReadOnlyAccess. Alternatively, create a policy with the following set of permissions: ec2:DescribeVpnConnections ec2:DescribeVpcs ec2:DescribeVpnGateways To import connections, proceed as follows: Make the following settings: Access key: Enter the Amazon Access Key ID. It is a 20-character, alphanumeric sequence. Secret key: Enter the Secret Access Key. It is a 40-character sequence. Click Apply. The connections are imported and subsequently displayed on the Status page. Import Via Amazon Configuration To add a single connection to the existing list of connections you have to upload the configuration file of the respective connection. To import a single connection, proceed as follows: Download the configuration file of your Amazon VPC connection. In Amazon's download dialog make sure to select Sophos from the Vendor drop-down list. Open the Upload file dialog window. Click the Folder icon next to the VPC

IntroductionThis document describes how to install Identity Services Engine (ISE) 3.1 via Amazon Machine Images (AMI) in Amazon Web Services (AWS). From version 3.1 ISE can be deployed as an Amazon Elastic Compute Cloud (EC2) instance with the help of CloudFormation Templates (CFT).PrerequisitesRequirementsCisco recommends that you have basic knowledge of these topics:ISEAWS and its concepts like VPC, EC2, CloudFormationComponents UsedThe information in this document is based on Cisco ISE Version 3.1.The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.ConfigureNetwork TopologyConfigurationsIf there is no VPC, Security Groups, Key Pairs and VPN tunnel configured yet, you need to follow Optional steps, otherwise, start with Step 1.Optional Step A. Create VPC Navigate to VPC AWS Service. Select Launch VPC Wizard as shown in the image.Choose VPC with Private Subnet Only and Hardware VPN Access and click Select as shown in the image.Note: The selection of VPC in Step 1. of the VPC wizard depends on the topology since ISE is not designed as Internet exposed server - VPN with private subnet only is used.Configure VPC Private Subnet Settings as per your network design and Select Next.Configure your VPN as per your network design and Select Create VPC.Once the VPC is created, the message "Your VPC has been successfully created" is displayed. Click OK as shown in the image.Optional Step B. Configure On-Prem VPN Headend DeviceNavigate to VPC AWS Service. Choose Site-to-Site VPN connections, select newly created VPN tunnel and Select Download Configuration as shown in the image.Choose Vendor, Platform and Software, Select Download as shown in the image.Apply downloaded configuration on On-Prem VPN headend device.Optional Step C. Create Custom Key PairAWS EC2 instances are accessed with the help of key pairs. In order to create a key pair, navigate to EC2 Service. Select Key Pairs menu under Network & Security. Select Create Key Pair, give it a Name, leave other values as default and Select Create Key Pair again.Optional Step D. Create custom Security GroupAWS EC2 instances access is protected by Security Groups, in order to configure Security Group, navigate to EC2 Service. Select Security Groups menu under Network & Security. Select Create Security Group, configure a Name, Description, in the VPC field select newly configured VPC. Configure

The Esri arcgis-mission-server-ha.template.json Amazon Web Services (AWS) CloudFormation template creates an ArcGIS Mission Server site on multiple Amazon Elastic Compute Cloud (EC2) instances for high availability. The EC2 instances are deployed in an AWS Auto Scaling group, which offers advantages such as capacity planning based on certain criteria, better fault tolerance, better availability, and better cost management.This template creates the following architecture in Amazon Web Services:License:Certain icons in the diagram are used with permission from Amazon Web Services.PrerequisitesPrerequisites can be grouped by the items—such as files and accounts—that you must obtain and the tasks you must perform before running the CloudFormation template.Required itemsYou need the following before running this template:An Amazon Web Services account.The account must have access to basic AWS services such as CloudFormation, Amazon Elastic Compute Cloud (EC2), Amazon Virtual Private Cloud (VPC), Amazon Simple Storage Service (S3), Systems Manager, Amazon CloudWatch, Lambda, AWS Identity and Access Management (IAM), Amazon DynamoDB, Secrets Manager, AWS Certificate Manager, and Amazon Relational Database Service (RDS).An ArcGIS Mission Server license file (.ecp or .prvc).An SSL certificate file (a .pfx file) and corresponding password.The certificate must be from a certifying authority.If you create a deployment on Ubuntu EC2 instances in AWS GovCloud, you need an AMI ID. If you want to use the base canonical Ubuntu AMI, follow the instructions in Esri Amazon Web Services CloudFormation templates to identify the ID.An Amazon Virtual Private Cloud (VPC) and subnets.All components in the same ArcGIS Enterprise deployment must run in the same VPC. If your portal exists, use the same VPC and subnets you used for the portal. If you have not created a portal yet and do not have an existing VPC, you can use one of the following CloudFormation templates to create a VPC: VPC with two public subnets or VPC with two public and private subnets with a NAT Gateway.The arcgis-mission-server-ha.template.json CloudFormation template.Required tasksComplete the following tasks before running this template:Prepare a deployment Amazon Simple Storage Service (S3) bucket in the AWS account. Specify the bucket name in the template when you launch the stack.Create a bucket or use an existing S3 bucket. You must be the owner of the bucket.Upload the ArcGIS Mission Server authorization file to the bucket. Upload the SSL certificate file to the bucket.If you use an Elastic IP address with this deployment (which is optional), you must create the Elastic IP address before running this template.You can

Config file box. Select the configuration file and upload it. To upload the selected file click the button Start Upload. The filename is displayed in the VPC config file field. If you use static routing, enter the remote network. The remote network is not part of the configuration file. Therefore you need to enter it separately into the Remote network field, e.g. 10.0.0.0/8. This field is only important if you have configured the use of static routing instead of dynamic routing in Amazon VPC. Click Apply. The connection is imported and subsequently displayed on the Status page. Route Propagation You can configure networks which are being pushed in route propagation enabled routing tables in the Amazon VPC. To select local networks, proceed as follows: Add local networks. Add or select a local network that should be pushed in route propagation. How to add a definition is explained on the Definitions & Users > Network Definitions > Network Definitions page. Click Apply. The route propagation networks are applied.