Resolution
----------

To avoid failover or connection issues, it's a best practice not to configure graceful restart and BFD at the same time. For fast failover, configure BFD without graceful restart turned on. For more information, see [BGP quotas](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html#bgp-quotas).

Related information
-------------------

[Network requirements](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html#overview_requirements)

I turned on graceful restart and Bidirectional Forwarding Detection (BFD) for my AWS Direct Connect connection for fast failure detection and failover. However, I have failover delays or connection issues.

Troubleshoot BFD failover for Direct Connect

After I configure BFD, why does failover take longer than expected on my AWS Direct Connect connection?

Networking & Content Delivery

Direct Connect - Incident Detection and Response Alarming Best Practices

How do I enable BFD for my Direct Connect connection?

How do I troubleshoot Direct Connect and VPN failover issues?

How do I configure Direct Connect and VPN failover with Transit Gateway?

How do I resolve the DOWN notification on my Direct Connect BFD?

Direct Connect + VPN + TGW with DX/VPN failover

Direct Connect Failover with two Virtual Interfaces (VIFs)

Best Practices for ElasticSearch Cluster Failovers

EKS connection string handling after Aurora PostgreSQL Global Database failover to secondary region

How can we shorten failover time DX and VPN?

After I configure BFD, why does failover take longer than expected on my AWS Direct Connect connection?

Resolution

Related information

Relevant content