Differences

This shows you the differences between two versions of the page.

--- bloglike:2022-05 [2022/05/14 03:44] – AWS Event Rule, CloudWatch target and failed invocations stybla
+++ bloglike:2022-05 [2022/05/16 03:33] (current) – add AWS EFS cross-account mount stybla
@@ Line 47: / Line 47: @@
 See this [[https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/351|GitHub issue]] for more info.
+ --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2022/05/14 09:08//
+===== AWS EFS cross-account mount =====
+There is not much to write about except it works, at least in 2022. It seems that wasn't always the case. You will need to connect accounts by either [[https://www.middlewareinventory.com/blog/aws-vpc-peering-tutorial/|VPC peering]] or Transit gateway or however you like and need. Then there is a handy [[https://aws.amazon.com/premiumsupport/knowledge-center/access-efs-across-accounts/|how-to/KB article]] from AWS which seems a bit overcomplicated than it needs to be. Despite I like CLI, you can find IP addresses in the web console which seems way easier and faster than querying an internal API to which you must have ACLs. You need this in order to modify ''/etc/hosts''.
+And that should be it. Of course, everything depends on your setup, security etc. One last thing. Should you encounter ''Connection reset by peer'', it most likely means that VPC range from the other account needs to be allowed in a security group attached to EFS mount target/access point.
+ --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2022/05/16 08:01//