S3 Access Logs to CloudWatch Logs Now Reach GovCloud, China, and the European Sovereign Cloud!
Hi, it's Shii-chan! Today I'm sharing a Region expansion for S3 logging!
AWS What's NewWhat was announced?
In AWS What's New, Amazon S3 server access log delivery to Amazon CloudWatch Logs is now available in five additional AWS Regions.
The newly added Regions are:
- AWS GovCloud (US) Regions
- AWS European Sovereign Cloud
- AWS China Regions
With this addition, delivery of S3 server access logs to CloudWatch Logs is available in all AWS Regions!
Why it matters
This delivery path complements the existing delivery of server access logs to S3 general purpose buckets. Being able to run the same setup in government, sovereign, and China Regions is the big deal here.
What changes
With access logs in CloudWatch Logs, you can:
- Query logs as they arrive
- Set alarms, for example on error rates
- Encrypt them with AWS KMS keys
- Monitor traffic patterns and investigate access incidents
- Correlate S3 access activity with the rest of your operational data
If you used to analyze logs after they piled up in an S3 bucket, you can now monitor much closer to real time!
Dive Deep
CloudWatch Logs charges for vended logs apply. See the Amazon CloudWatch pricing page for details. For how to set it up, check the Amazon S3 User Guide.
Wrap-up
- Support extends to the GovCloud (US), European Sovereign Cloud, and China Regions
- S3 server access log delivery to CloudWatch Logs is available in all AWS Regions
- You get querying, alarms, KMS encryption, and correlation with other operational data
- CloudWatch Logs vended logs charges apply
This one is for anyone monitoring S3 access in tightly regulated Regions!