The "Which Services to Use" section could use an update, I think. Some questions I'd like to raise:
Why is "Cloudtrail" in "Optional"? There is no alternative that will record API calls made to AWS, and it's a critical tool for having an audit trail.
⛓WAF: Web firewall for CloudFront to deflect attacks - WAF can now be used in front of ALBs which makes it a bit more useful than it used to be. Would be worth mentioning that in the description.
What's the timeline for getting a service out of the "new" tag? Config is still marked as new, but it's a fairly mature service and is often considered critical for complementing an audit trail to record changes that may happen to infrastructure without an API call (so are not recorded by cloudtrail). It's also much easier to see the timeline of changes in the console, that sifting through CloudTrail logs :)
Hi,
The "Which Services to Use" section could use an update, I think. Some questions I'd like to raise:
Why is "Cloudtrail" in "Optional"? There is no alternative that will record API calls made to AWS, and it's a critical tool for having an audit trail.
⛓WAF: Web firewall for CloudFront to deflect attacks- WAF can now be used in front of ALBs which makes it a bit more useful than it used to be. Would be worth mentioning that in the description.What's the timeline for getting a service out of the "new" tag? Config is still marked as new, but it's a fairly mature service and is often considered critical for complementing an audit trail to record changes that may happen to infrastructure without an API call (so are not recorded by cloudtrail). It's also much easier to see the timeline of changes in the console, that sifting through CloudTrail logs :)