A configuration file can be exported from aws to get all ipsec parameters (if the vpn on aws is done on a customer gateway). If it's done on a 3rd party firewall, then people managing that fw in the cloud will have to give you the information.
Then, you can follow any cisco step by step for L2L vpn on FTD. The only thing is that ftd doesn't support route based (vti tunnel) except version 6.7, so the only limitation is that you are limited to only 1 sa. Basically, you have any as source fromn your lan and the aws subnet as destination. Afterwards, you'll be able to filter the communication at the fw level if you don't have sysopt permit-vpn enabled.
Thanks Francesco PS: Please don't forget to rate and select as validated answer if this answered your question
On December 8, FireEye reported that it had been compromised in a sophisticated supply chain attack: more specifically through the SolarWinds Orion IT monitoring and management software. The attackers leveraged business software updates in order to distr...
About this Document
Cisco Secure Endpoint (formerly AMP for Endpoints) is a comprehensive Endpoint Security solution designed to function both as a stand-alone tool, and as a part of the architecture of natively integrated Cisco and 3rd par...
To verify the status of RADIUS server from NAD, use the command show aaa server
4507#sh aaa servers
RADIUS: id 3, priority 1, host 10.10.14.20, auth-port 1812, acct-port 1813
State: current UP, duration 10862s, previ...