Cross Account Accessing an AWS S3 Bucket

[@paravind2979]

Thank you for such amazing content!! Looking forward for more videos.

[@AnshulJain-sj1lu]

More power to you, brother, keep making this video's

[@madhavareddy580]

Very detailed. Thanks!

[@FelixYu]

Glad that u found it helpful mate!!

[@aabbassp]

Great video. Thanks!

[@FelixYu]

Thanks mate!!

[@arr09322]

for the target account, can you instead of modifying the "Bucket Policy" create an IAM Role in the target account the account A lambda ( source ) can assume in account B (target)?

[@jeffdeng1652]

this is a much more scalable solution

[@arrjay3814]

Thanks for this but it errors when I run it.... The error message is ""require is not defined in ES module scope, you can use import instead". Any idea how to resolve this?

[@gulsanober2401]

Do we have to write policy code by ourselves.... Or we get from documents

[@JohnTheHumbleMan]

so we have two policies at play here, one for the role in account 1, and one for the bucket in account 2...

[@vaibhavsahni7412]

Is it possible to do it cross region?

[@neelimagupta217]

Thanks for sharing the video, However, I wanted to check in Account A you did not mention the account id of B where the Bucket is hosted (under Resource). Wondering, how does account A know where the Bucket is, I feel giving the name without account id won't suffice. Pls correct me if I am wrong.

[@FelixYu]

since aws s3 bucket names are globally unique, providing the bucket name is sufficient. u dont need the account id of account B

[@Welshryu]

Great video, got completely lost when you starting typing the code though, where are we supposed to learn that for AWS?

[@tonymarkey6525]

Really good up to the point where you went off on one typing code in........ You completely lost me at this stage which is a shame because up to that point all was quite understandable.

[@samuraiwolf3669]

why tf people choose node is beyond me