Connection problems against AWS on VPN S2S

[Matlu]

Hello, Folks.

Does anyone have experience with S2S VPN against cloud environments (AWS, Azure)?

I have a question regarding these VPNs.
I remember that AWS, Azure, etc, usually send you some templates to configure the VPNs.

My question is, is it mandatory to set the VPN column in the security rule, as it is in the document sent by AWS, for example?

In their document, they send the VPN column to be "set" in the following way.

5. Choose "Add" to add directional match rules as follows:
a. internal_clear --> vpn-0f9a91247e29d87c0
b. vpn-0f9a91247e29d87c0 --> vpn-0f9a91247e29d87c0
c. vpn-0f9a91247e29d87c0 --> internal_clear

Is it "mandatory" to configure it this way? Or can we leave this column either as "ANY" or simply by calling the community we have created for this VPN?

I am experiencing a communication problem between the 2 endpoints.
The VPN looks up and everything is fine, but there is no communication between the 2 endpoints.

I found in turn, a rare error, when doing a "TCPDUMP" as part of the tshoot, which shows the following.

The IP on our side, On-Premise, is 172.20.10.127.

Does anyone have any opinion regarding VPN vs. Cloud environments?

Regards.

[the_rock]

It is mandatory, specially for route based vpn tunnels. You need to enable that option in global properties in smart console, cant recall where exactly, somewhere under vpn section, bi-directional vpn or something is called I think.

Andy