SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 7 rules found
aws
    Impact
      Clean code attribute
        1. Using long-term access keys is security-sensitive

           Security Hotspot
        2. AWS region should not be set with a hardcoded String

           Code Smell
        3. Lambdas should not invoke other lambdas synchronously

           Code Smell
        4. Consumer Builders should be used

           Code Smell
        5. Reusable resources should be initialized at construction time of Lambda functions

           Code Smell
        6. Credentials Provider should be set explicitly when creating a new "AwsClient"

           Code Smell
        7. Region should be set explicitly when creating a new "AwsClient"

           Code Smell

        Lambdas should not invoke other lambdas synchronously

        intentionality - efficient
        maintainability
        Code Smell
        • aws

        This rule reports an issue when a lambda invokes another lambda synchronously.

        Why is this an issue?

        More Info

        Invoking other Lambdas synchronously from a Lambda is a scalability anti-pattern. Lambdas have a maximum execution time before they timeout (15 minutes as of June 2025). Having to wait for another Lambda to finish its execution could lead to a timeout.

        A better solution is to generate events that can be consumed asynchronously by other Lambdas.

        Noncompliant code example

        With AWS SDKv1

        InvokeRequest invokeRequest = new InvokeRequest()
                 .withFunctionName("myFunction");
        
        AWSLambda awsLambda = AWSLambdaClientBuilder.standard()
        		.withCredentials(new ProfileCredentialsProvider())
        		.withRegion(Regions.US_WEST_2).build();
        
        awsLambda.invoke(invokeRequest); // Noncompliant
        
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.6
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.6

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use