Hey there!! Can you please explain a bit why we are using a specific AWS account ELB in our s3 bucket policy for getting the access logs. Like why are these logs coming form this specific ELB? Is there no way for them to come directly from within our account? thank you so much!!!
Good question! At 3:42, AWS specifies that we use the account-id from AWS to the S3 bucket policy. In that case, we use the account-id from AWS instead of ours (Honestly, I don't know why we have to do this. I believe it has something to do with how the AWS team implemented this feature)
@@computingpower Thank you so much for the quick response!!! I tried asking chatGPT and it claimed this " The reason for using these specific accounts is to ensure that the access logs generated by ELB instances in a particular region are stored in S3 buckets owned by the ELB service in that region." So that is inline with what you said that it is just how it was implemented by the AWS team. Thank you for your time!!!
Hey there!!
Can you please explain a bit why we are using a specific AWS account ELB in our s3 bucket policy for getting the access logs.
Like why are these logs coming form this specific ELB?
Is there no way for them to come directly from within our account?
thank you so much!!!
Good question! At 3:42, AWS specifies that we use the account-id from AWS to the S3 bucket policy. In that case, we use the account-id from AWS instead of ours (Honestly, I don't know why we have to do this. I believe it has something to do with how the AWS team implemented this feature)
@@computingpower Thank you so much for the quick response!!!
I tried asking chatGPT and it claimed this
" The reason for using these specific accounts is to ensure that the access logs generated by ELB instances in a particular region are stored in S3 buckets owned by the ELB service in that region."
So that is inline with what you said that it is just how it was implemented by the AWS team.
Thank you for your time!!!
@@benmarcus2577 Excellent, thanks for letting me know!