Is this an error? Relay to BP Node Connection Message

Hi, I am currently having issues connecting my relay node to my BP Node. I am seeing repeating messages shown below and am not sure if there is an issue or not with the connection.

[cardano.node.IpSubscription:Info:55] [2021-03-12 03:09:47.06 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Trying to connect to <BP_NODE_IP:PORT>
[cardano.node.IpSubscription:Info:2007] [2021-03-12 03:09:47.06 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Connection Attempt Start, destination <BP_NODE_IP:PORT>
[cardano.node.IpSubscription:Notice:55] [2021-03-12 03:09:47.06 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Waiting 0.025s before attempting a new connection
[cardano.node.IpSubscription:Notice:2007] [2021-03-12 03:09:47.06 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Connection Attempt End, destination <BP_NODE_IP:PORT> outcome: ConnectSuccessLast
[cardano.node.IpSubscription:Info:2007] [2021-03-12 03:09:47.09 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Closed socket to <BP_NODE_IP:PORT>
[cardano.node.IpSubscription:Error:55] [2021-03-12 03:09:37.08 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Failed to start all required subscriptions
[cardano.node.IpSubscription:Info:55] [2021-03-12 03:09:38.08 UTC] IPs: 0.0.0.0:0 [<BP_NODE_IP:PORT>] Restarting Subscription after 1.026399829s desired valency 1 current valency 0

On the other hand, this is what I am seeing on my BP Node:

[cardano.node.ChainDB:Notice:59] [2021-03-12 03:16:20.84 UTC] Chain extended, new tip: 15aa41d2ee1bd856e5d37748365eb6b1a9d1e0368cb53587d2c6c6ca7f7e9cd4 at slot 1055860

These observations led me to believe that my BP to Relay connection is working, but not vice versa.
I am not too sure how to interpret the messages on the first block. Is it true that my Relay to BP Node connection has some problem. Is so, are there any pointers on how I can go about this?

Note that both Relay and BP Node reside on AWS.

Make sure your ports have been added to your firewall allowance list

Hi @KrakenStaking,

Thanks for answering my question, it turns out the message stops showing up after a while, I guess we just have to wait it out sometimes.