Difference between revisions of "Amazon S3 logging"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
* [[Logging requests with server access logging]] | * [[Logging requests with server access logging]] | ||
* [[Enabling Amazon S3 server access logging]] | * [[Enabling Amazon S3 server access logging]] | ||
| − | * [[AWS S3 Object Lock]] | + | * [[AWS S3 Object Lock]]: <code>[[aws s3api put-object-lock-configuration]]</code> |
== See also == | == See also == | ||
Revision as of 04:03, 17 June 2024
Amazon S3 allows users to enable or disable logging. If enabled, the logs are stored in Amazon S3 buckets which can then be analyzed. These logs contain useful information such as:
- Date and time of access to requested content
- Protocol used (HTTP, FTP, etc.)
- HTTP status codes
- Turnaround time
- HTTP request message
- Terraform resource:
aws_s3_bucket_logging
Limitations:
- The destination bucket must be in the same AWS Region and AWS account as the source bucket.
News
Related
- Logging requests with server access logging
- Enabling Amazon S3 server access logging
- AWS S3 Object Lock:
aws s3api put-object-lock-configuration
See also
- Amazon S3 logging,
aws s3 bucket logging - AWS S3,
aws s3, aws s3api, aws s3control, s3:, Amazon S3 Storage Lens, AWS S3 replication, CRR, SSR, CAR, S3 Replication Time Control (S3 RTC), Website endpoint, Amazon Macie, Versioning, Lifecycle, Encryption, logging, Amazon S3 Inventory, Amazon S3 Batch Operations, Storage Classes, Amazon S3 clients, Terraform S3, AWS canned ACLs, Directory buckets, security,PutObject
Advertising:
