You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling Logging to S3 it creates the access and sessions bucket, but from what I can tell nothing is actually sent to either bucket. Previously this was accomplished by adding a CloudTrail and an S3 policy that allowed the Cloudtrail to put logs into the session logs bucket:
From what I can tell this has not been replaced by another method of logging and I believe that is why nothing is being logged to the Session logs bucket.
Impact
No logs in the Session logs bucket
Completion
Completion of this issue would mean that logs regarding the Bastions established session being sent to the Session logs bucket and whenever the Session logs bucket is accessed a log is sent to the access logging bucket. In addition to this an automated test to validate that there are any items (logs) in the Session logs bucket could be very helpful.
The change has been peer reviewed
Automated tests have been written and/or updated, and are passing
Documentation has been written and/or updated -->
The text was updated successfully, but these errors were encountered:
Description
When enabling Logging to S3 it creates the access and sessions bucket, but from what I can tell nothing is actually sent to either bucket. Previously this was accomplished by adding a CloudTrail and an S3 policy that allowed the Cloudtrail to put logs into the session logs bucket:
From what I can tell this has not been replaced by another method of logging and I believe that is why nothing is being logged to the Session logs bucket.
Impact
No logs in the Session logs bucket
Completion
Completion of this issue would mean that logs regarding the Bastions established session being sent to the Session logs bucket and whenever the Session logs bucket is accessed a log is sent to the access logging bucket. In addition to this an automated test to validate that there are any items (logs) in the Session logs bucket could be very helpful.
The text was updated successfully, but these errors were encountered: