What is our primary use case?
I use AWS CloudTrail to gather audit logs to determine who, what, where, when, how, and why actions took place within the cloud environment.
How has it helped my organization?
I have a use case where I determined that system failures or API failures happen with specific IM roles, and I saw that within the log data, so I reached out to the team responsible for that role and allowed the team to remediate that. AWS CloudTrail has been beneficial as it provided better reliability within the service. It was a blocker, which the team wasn't particularly aware of until I raised it.
What is most valuable?
What I found most valuable in AWS CloudTrail is that it provides a good context of what's happening in the environment, so it's an excellent way to baseline what's occurring.
I also like that AWS CloudTrail helps with audits.
What needs improvement?
I have to check if this is still the case, but I know that filtering multiple values within the console is a feature that has yet to exist in AWS CloudTrail.
You can look up a user identity, service, or action, but you can't search for multiple dimensions. For example, you can't combine service and user identity as search filters. If AWS CloudTrail lets you filter more and get a subset of the information on multiple dimensions, that'd be useful.
Besides that, I'm content with the solution, and AWS has made some good improvements over the years.
For how long have I used the solution?
I've been working with AWS CloudTrail for about six years.
What do I think about the stability of the solution?
AWS CloudTrail is a stable solution, and I've not seen many performance issues. The performance issue only occurred when the downstream service was affected.
For example, a few years back, AWS had a problem with Amazon S3. Amazon S3 was out of service for six hours or more, which caused massive issues within AWS that led to a downstream effect that affected AWS CloudTrail. It was only one instance in the years I've worked with the solution.
What do I think about the scalability of the solution?
AWS CloudTrail is scalable, and I didn't find any issues with its reliability or ability to scale. Scalability-wise, the solution is a ten.
How was the initial setup?
AWS CloudTrail is easy to deploy, and by default, it's already turned on.
What about the implementation team?
My company deploys AWS CloudTrail in-house. Once the account is provisioned, the service turns on.
What's my experience with pricing, setup cost, and licensing?
AWS CloudTrail is pretty affordable, and I have to double-check, but the service is free to use. I can add logs on the console, but if I want to store logs long-term, then I have to pay a storage fee, but it's relatively inexpensive.
AWS CloudTrail hooks right into Amazon S3, and you can even send your files to CloudWatch if you wish, though that adds to the cost. You can also view certain data events. It's mainly for the control plane of services, but you can view AWS Lambda and Amazon S3 actions, which entails a higher cost. Though not free, the charge is pretty affordable. In terms of cloud spending per year, it's not that high.
What other advice do I have?
AWS CloudTrail gets updated regularly, so I'm using the latest version. It's similar to a SaaS, which means it's consumed in the AWS cloud and not hosted.
I advise anyone looking into implementing AWS CloudTrail to devise a strategy for retrieving logs and integrating the AWS CloudTrail logs into any incident response and detection service. It would be best if you also considered the data retention needed for the log data. The logs will continually add up, and you'll incur more costs over time. Figuring out your log life cycling policy might help reduce the number of logs you're storing.
My rating for AWS CloudTrail is nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.