- Newest
- Most votes
- Most comments
This issue of hourly tunnel drops in your Site-to-Site VPN connection is likely related to a Phase 1 or Phase 2 lifetime mismatch between your Fortinet customer gateway device and AWS.
The most common causes for this pattern include:
-
IKE/Phase 1 or IPsec/Phase 2 lifetime mismatch: The lifetime values on your Fortinet device may not match AWS parameters, causing rekey issues. This is particularly relevant for IKEv1, as IKEv2 lifetime values are independent of peers.
-
Dead Peer Detection (DPD) timeout: AWS may be timing out DPD after multiple retransmits if your Fortinet device isn't responding to DPD messages properly.
-
Rekey collision: When both sides attempt to rekey simultaneously, it can cause temporary disconnections.
To troubleshoot this issue:
-
Verify that the Phase 1 and Phase 2 lifetime settings on your Fortinet device align with AWS parameters.
-
Check AWS Site-to-Site VPN logs in CloudWatch for specific error messages like "AWS tunnel DPD timed out" or messages about DELETE for IKE_SA or Phase 2 SA, which would indicate the specific cause.
-
Look for messages about CHILD_REKEY collisions in the logs, which could explain the periodic disconnections.
-
Ensure that the encryption domain or traffic selector includes both source and destination networks.
-
Verify that your VPN connection has proper redundancy with a second customer gateway device for better availability.
Since the issue occurs at regular intervals (hourly), it strongly suggests a timer-based issue like lifetime mismatches or scheduled rekey operations that aren't being handled smoothly between AWS and your Fortinet device.
Sources
Troublehsoot connectivity between SIte-to-Site VPN and VPC | AWS re:Post
AWS Site-to-Site VPN logs - AWS Site-to-Site VPN
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago

Hi Mamadou, recheck appliance and AWS VPN connection for lifetime mismatch and DPD timeout