Connect to a VAP through AWS

to connect to a vap, you must create a vpc endpoint in the aws management console and configure it to point to the vap id this endpoint is the logic aws uses to connect to a software as a service (saas) in this case, {{vc}} is the saas provider to connect to a vap, follow these steps sign in to the aws console vaps are region specific, so select a region in the upper right toolbar search for vpc in the find services menu bar and select the vpc service first, to create the vpc for the segregated aws environment, select your vpcs from the left side menu, and then select \[ create vpc ] if your organization already has environments on the aws platform, we still recommend setting up a segregated, secured vpc to use for the {{vc}} endpoint connection complete the requested information to create the vpc, as recommended by your organization you can also choose to use default information (such as /24 for available addresses, no ipv6 cidr block , and default from the tenancy drop down list) after completing the form, select \[ create vpc ] next, you must create the associated subnets by selecting subnets from the left side menu and selecting \[ create subnet ] in the vpc id drop down list, select the vpc you just created for subnet settings , we recommend building a minimum of three availability zones select a name, corresponding availability zone, and subnet (based on your supernet/associated vpc cidr) repeat step 8 until you create a minimum of three subnets select \[ create subnet ] lastly, you need to create the associated endpoint go to endpoints on the left side menu, and select \[ create endpoint ] under service category , select find service by name and enter the service name provided to you in an email from the {{futurex}} team after verifying the service name, the system prompts you to select the vpc and associated subnets or availability zones we recommend that you select all options selecting availability zones next, select the security group for the vap the security group defines the firewall rules within your vpc for more information on creating and assigning security groups, see security groups in aws docid\ c3upx5va sb1vzhplctky in the next section finally, select \[ create endpoint ] the endpoint now shows in the aws management console as pending acceptance , and {{futurex}} is notified of the new connection request automatically send the endpoint id to your {{futurex}} representative by email this enables our network administrators to associate the endpoint id with your organization and approve the connection for an extra layer of security and authorization, you might also share your aws customer id the following image shows where you can find your endpoint id after we accept the connection, you have a local ip on the server that connects to {{vc}}