I do not think there could be improvements in AWS CloudTrail because I am too small to suggest anything. It is already a well-established service from AWS, and I have only been using it for the last two or three years, though it has been available for many years. They should implement some kind of AI that can help you give commands to the AI and have it search all the logs and return results. Searching the logs is not very easy; it requires a lot of patience and hard work to find the right information in the log.
I have not experienced the Trail feature of AWS CloudTrail in tracking changes to AWS infrastructure. AWS CloudTrail could benefit from more comprehensive documentation and broader service integration. Making it as fundamental as EC2 would increase its adoption. It is currently an underrated but powerful service.
AWS CloudTrail should be redesigned to capture non-API calls. It would be more effective to have one tool that can perform multiple tasks instead of relying on multiple services for non-API activities.
More controls should be introduced in CloudTrail, especially to see the logs in CloudTrail itself without saving them in S3, as S3 starts to incur charges. Real-time log submission could be improved, as sometimes there is a lag of around two to three minutes, which should be under a minute.
It would be good if we were able to integrate with other services as well. From what I am aware of, we do the monitoring. We can integrate AWS CloudTrail with CloudWatch, Amazon Athena, and EventBridge. If we can integrate AWS CloudTrail with more services, then it can be a more helpful product for the organization.
Once the organization defines its policies, it must immediately enable AWS CloudTrail and integrate it with auto-remediation procedures using Lambda functions. This ensures that the main administrator can receive information quickly and on time without delay.
Principal Solution Architect at StarOne IT Solutions
MSP
Top 5
Feb 15, 2024
It's getting better, but it's not perfect because technology landscapes and use cases constantly evolve. There's a lot happening, so it's not perfect. It's improving.
The solution should incorporate visibility for CloudWatch events so that one view includes everything across both products. The event capture timing should be reduced. Currently, you have to wait about 15 minutes after an event happens before you can view it in the log.
AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your AWS infrastructure. CloudTrail provides event history of your AWS account activity, including actions taken through the AWS Management Console, AWS SDKs, command line tools, and other AWS services. This event history simplifies security analysis, resource...
I do not think there could be improvements in AWS CloudTrail because I am too small to suggest anything. It is already a well-established service from AWS, and I have only been using it for the last two or three years, though it has been available for many years. They should implement some kind of AI that can help you give commands to the AI and have it search all the logs and return results. Searching the logs is not very easy; it requires a lot of patience and hard work to find the right information in the log.
I have not experienced the Trail feature of AWS CloudTrail in tracking changes to AWS infrastructure. AWS CloudTrail could benefit from more comprehensive documentation and broader service integration. Making it as fundamental as EC2 would increase its adoption. It is currently an underrated but powerful service.
I'm satisfied function-wise with AWS CloudTrail; only the integration with third-party solutions is a point for improvement.
AWS CloudTrail should be redesigned to capture non-API calls. It would be more effective to have one tool that can perform multiple tasks instead of relying on multiple services for non-API activities.
Right now, AWS CloudTrail is perfect. I have not experienced any challenges while using it.
More controls should be introduced in CloudTrail, especially to see the logs in CloudTrail itself without saving them in S3, as S3 starts to incur charges. Real-time log submission could be improved, as sometimes there is a lag of around two to three minutes, which should be under a minute.
It would be good if we were able to integrate with other services as well. From what I am aware of, we do the monitoring. We can integrate AWS CloudTrail with CloudWatch, Amazon Athena, and EventBridge. If we can integrate AWS CloudTrail with more services, then it can be a more helpful product for the organization.
Once the organization defines its policies, it must immediately enable AWS CloudTrail and integrate it with auto-remediation procedures using Lambda functions. This ensures that the main administrator can receive information quickly and on time without delay.
It's getting better, but it's not perfect because technology landscapes and use cases constantly evolve. There's a lot happening, so it's not perfect. It's improving.
Maybe if we could do direct queries on CloudTrail without needing to export it to Athena, that'd be great.
The solution is very expensive.
The platform’s reporting log sheet feature could be more user-friendly.
The solution should incorporate visibility for CloudWatch events so that one view includes everything across both products. The event capture timing should be reduced. Currently, you have to wait about 15 minutes after an event happens before you can view it in the log.