Thank you for taking the time to create this video. Would like to know if the 2MB files are actually visible in the S3 bucket via the Amazon Web Services console... auditing is working, but I don't see any S3 files.
@@emarversity my understanding is that retention is to preserve the files on the ** RDS instance ** for a set number of hours or days *after* the files have been transmitted to S3. Regardless, I'm certain i've generated more than 2gb worth of log content, and I'm seeing the log file name change when I query the audit logs, but nothing is ever ending up in */transmitted as described in the video. (Sorry... to answer your question, yes, 72hr retention is configured)
@@redincs Sorry, that does not appear to be a correct statement. Based on the definitions provided by AWS, the files should be sent from 'D: dsdbdata\SQLAudit\' to the S3 bucket when they reach the SIZE threshold (in our case, 2MB), and appear in the S3 bucket immediately upon being sent in full; and the files, once sent, should appear in 'D: dsdbdata\SQLAudit\transmitted\' and REMAIN there for the retention period (in our case, 72hours/3 days). We are seeing the files only in 'D: dsdbdata\SQLAudit\' , we do not see them in S3, and they never end up in 'D: dsdbdata\SQLAudit\transmitted\' . Not sure where exactly to look for any errors related to this.
![Database Level Auditing with SQL Server 2012 [HD]](http://i.ytimg.com/vi/bW80U9_Jdsw/mqdefault.jpg)
![[LIVE] : ONE ลุมพินี 88 | คู่เอก "ป้อมเพชร vs อัสลามจอน"](http://i.ytimg.com/vi/1ZqTVVbMgbo/mqdefault.jpg)
nice video! thanks for the upload
Glad you liked it!
Thank you for taking the time to create this video. Would like to know if the 2MB files are actually visible in the S3 bucket via the Amazon Web Services console... auditing is working, but I don't see any S3 files.
Did you enable retention in the options configuration? Give it some time.
@@emarversity my understanding is that retention is to preserve the files on the ** RDS instance ** for a set number of hours or days *after* the files have been transmitted to S3. Regardless, I'm certain i've generated more than 2gb worth of log content, and I'm seeing the log file name change when I query the audit logs, but nothing is ever ending up in */transmitted as described in the video. (Sorry... to answer your question, yes, 72hr retention is configured)
So after 72 hours they should be sent to s3. Try disabling rentetion and see if they sent directly to the s3.
@@redincs Sorry, that does not appear to be a correct statement. Based on the definitions provided by AWS, the files should be sent from 'D:
dsdbdata\SQLAudit\' to the S3 bucket when they reach the SIZE threshold (in our case, 2MB), and appear in the S3 bucket immediately upon being sent in full; and the files, once sent, should appear in 'D:
dsdbdata\SQLAudit\transmitted\' and REMAIN there for the retention period (in our case, 72hours/3 days). We are seeing the files only in 'D:
dsdbdata\SQLAudit\' , we do not see them in S3, and they never end up in 'D:
dsdbdata\SQLAudit\transmitted\' . Not sure where exactly to look for any errors related to this.
@@MarcFunaro Try disabling the retention and see what happens. Also try doing a test backup to the s3 to confirm the communication is working.