Module aws_sdk_codegurusecurity::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules§

  • Builders
  • Error types that Amazon CodeGuru Security can respond with.

Structs§

  • A summary of findings metrics in an account.

  • Contains information about the error that caused a finding to fail to be retrieved.

  • Information about a finding category with open findings.

  • The line of code where a finding was detected.

  • Information about account-level configuration.

  • Information about the location of security vulnerabilities that Amazon CodeGuru Security detected in your code.

  • Information about a finding that was detected in your code.

  • An object that contains information about a finding and the scan that generated it.

  • The severity of the issue in the code that generated a finding.

  • Information about summary metrics in an account.

  • Information about the recommended course of action to remediate a finding.

  • Information about how to remediate a finding.

  • Information about a resource, such as an Amazon S3 bucket or AWS Lambda function, that contains a finding.

  • Information about a scan with open findings.

  • Information about a scan.

  • Information about the suggested code fix to remediate a finding.

  • Information about a validation exception.

  • Information about a security vulnerability that Amazon CodeGuru Security detected.

Enums§

  • When writing a match expression against AnalysisType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • The identifier for a resource object that contains resources where a finding was detected.

  • When writing a match expression against ScanState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ScanType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against Severity, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against Status, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ValidationExceptionReason, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.