Yes, instead of allowing "all traffic" in the outbound rules, You only allow outbound traffic to specific IP addresses, ports, or protocols, ensuring that data only flows to trusted destinations
in the given example, the test folder is from different region (virginia) how EFS can back up the data in the test folder when EFS is in the different region (ohio)
@@btreesystems meaning as per the example explained in the video, EFS would be created in Virginia and the EFS would be mounted in Ohio using the EFS ID created in Virginia?? So the conclusion: if the data from one region to be backed up ,create EFS in that region and use the efs ID to mount in availability zones in other regions where we want the data to be replicated ?
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
content is clear ,also do the practical session is easily understand to everyone.......!
is there any case where outbound rule should not be all traffic?
Yes, instead of allowing "all traffic" in the outbound rules, You only allow outbound traffic to specific IP addresses, ports, or protocols, ensuring that data only flows to trusted destinations
@@btreesystems Thanks 😊
in the given example, the test folder is from different region (virginia) how EFS can back up the data in the test folder when EFS is in the different region (ohio)
Mounting the EFS ID in different availability zones ensures that the data in the EFS folder is backed up and replicated across those zones.
@@btreesystems meaning as per the example explained in the video, EFS would be created in Virginia and the EFS would be mounted in Ohio using the EFS ID created in Virginia??
So the conclusion: if the data from one region to be backed up ,create EFS in that region and use the efs ID to mount in availability zones in other regions where we want the data to be replicated ?