Separating Out Access Logging

[noah-paige]

Feature or Bugfix

• Refactoring

Detail

• Move access logging to a separate environment logging bucket (rather than env default bucket used for athena queries and profiling job artifacts)

Relates

Security

Please answer the questions below briefly where applicable, or write N/A. Based on OWASP 10.

• Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)?
  • Is the input sanitized?
  • What precautions are you taking before deserializing the data you consume?
  • Is injection prevented by parametrizing queries?
  • Have you ensured no eval or similar functions are used?
• Does this PR introduce any functionality or component that requires authorization?
  • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  • Are you logging failed auth attempts?
• Are you using or adding any cryptographic features?
  • Do you use a standard proven implementations?
  • Are the used keys controlled by the customer? Where are they stored?
• Are you introducing any new policies/roles/users?
  • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[noah-paige]

Tested:

• [x] CICD Pipeline
• [x] Migration Script Upgrade
• [x] Environment Stack Update
• [x] Dataset Stack Update
• [x] Migration Script Downgrade
• [x] Dataset Table Profiling Run Successful
• [x] Worksheet Query Successful
• [x] Access Logs Written for Env Bucket + All Dataset Buckets to new Logs Bucket