How does CodeGuru Profiler help reduce operational costs?
CodeGuru Profiler identifies the most expensive lines of code in an application. By pinpointing these inefficiencies, it helps optimize application performance, which can lead to a reduction in operational costs by up to 50%.
What types of issues does CodeGuru Reviewer detect in Java and Python code?
CodeGuru Reviewer detects a range of issues including security vulnerabilities (like OWASP Top 10 risks and AWS API security best practices), secrets hardcoded in repositories, resource leaks, concurrency problems, incorrect input validation, and deviations from best practices for AWS APIs and SDKs. It also identifies code quality issues such as maintainability problems and inconsistencies.
Can CodeGuru Reviewer analyze code for security vulnerabilities related to AWS APIs?
Yes, CodeGuru Reviewer provides recommendations based on AWS API security best practices, specifically checking security for Amazon Elastic Compute Cloud and AWS Key Management Service. It also applies Amazon's internal security expertise to your code, including Java and Python crypto library best practices.
How does CodeGuru Reviewer handle secrets detection in code repositories?
CodeGuru Reviewer's Secrets Detector uses machine learning to identify hardcoded secrets such as passwords, API keys, SSH keys, and database connection strings within your repository or configuration files. It then offers point-and-click steps to secure these secrets using AWS Secrets Manager.
What is the pricing model for CodeGuru Reviewer's full repository scans?
The standard monthly pricing for CodeGuru Reviewer includes up to two full repository scans per month for each onboarded repository. Additional full repository scans beyond this limit are charged at $10 per 100K lines of code.
How does CodeGuru Reviewer calculate the monthly cost for repositories with multiple branches?
When a repository has multiple code branches, CodeGuru Reviewer charges based on the largest code branch. This means you are only billed for the lines of code in the largest branch, even if you run analysis on other branches.