Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

💝 Valentine's Sale! Get 30% OFF Any Reviewer. Use coupon code: PASSION-4-CLOUD & 10% OFF Store Credits/Gift Cards

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate Server access logging for Amazon S3 buckets Reply To: Server access logging for Amazon S3 buckets

  • Neil-TutorialsDojo

    Member
    January 31, 2025 at 10:25 am

    Hello Theodosios,

    Good day!

    Thanks for reaching out. Based on your shared requirements, the best solution for tracking and logging access to your S3 buckets would be to enable server access logging for all required buckets (Option B). This feature provides comprehensive logs of requests, including details like the requester, bucket name, request time, request action, and error codes. It also offers great visibility into object-level operations, which you mentioned is important. Plus, it’s cost-effective as you only pay for the storage used for the log files.

    While AWS CloudTrail (Option A) is also a powerful logging solution and is often recommended for its comprehensive auditing capabilities, server access logging is more tailored to the specific requirements mentioned in this scenario, especially for object-level operations and detailed access information.

    Regarding the answer provided by ChatGPT. While ChatGPT is a great tool for getting quick insights, it’s important to consider the specific context and official documentation for the best fit. In this case, server access logging aligns more with the detailed object-level logging requirements for S3 buckets.

    For more details, you can refer to the official AWS documentation on logging with Amazon S3 |

    https://docs.aws.amazon.com/AmazonS3/latest/userguide/logging-with-S3.html

    I hope this helps.

    Regards,

    Neil @ tutorials dojo

Skip to content