githubEdit

S3 Server Access Logging Gets Disabled After Enabling Through AWS Console

If you enable S3 server access logging through the AWS Console and it gets automatically disabled after 45-60 seconds, this is due to DuploCloud's state reconciliation process. DuploCloud manages the configuration of your S3 buckets and will reconcile any changes made directly through the AWS Console back to the state defined in DuploCloud. Solution To enable S3 server access logging that will persist, you must enable it through the DuploCloud portal instead of the AWS Console: Navigate to your S3 bucket in the DuploCloud portal Open the bucket settings panel Enable server access logging through the DuploCloud interface When enabled through the DuploCloud portal, the server access logging setting will remain active and won't be automatically disabled by the state reconciliation process. Important: Always use the DuploCloud portal to modify S3 bucket configurations to ensure your changes persist and aren't overridden by DuploCloud's management system.

Last updated

Was this helpful?