Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Account
Aggregation Contains counts of vulnerability findings from image scans that run when you create new Image Builder images, or build new versions of existing images. The vulnerability counts are grouped by severity level. The counts are aggregated across resources to create the final tally for the account that owns them.
- Additional
Instance Configuration In addition to your infrastructure configuration, these settings provide an extra layer of control over your build instances. You can also specify commands to run on launch for all of your build instances.
Image Builder does not automatically install the Systems Manager agent on Windows instances. If your base image includes the Systems Manager agent, then the AMI that you create will also include the agent. For Linux instances, if the base image does not already include the Systems Manager agent, Image Builder installs it. For Linux instances where Image Builder installs the Systems Manager agent, you can choose whether to keep it for the AMI that you create.
- Ami
Details of an Amazon EC2 AMI.
- AmiDistribution
Configuration Define and configure the output AMIs of the pipeline.
- Component
A detailed view of a component.
- Component
Configuration Configuration details of the component.
- Component
Parameter Contains a key/value pair that sets the named component parameter.
- Component
Parameter Detail Defines a parameter that is used to provide configuration details for the component.
- Component
State A group of fields that describe the current status of components.
- Component
Summary A high-level summary of a component.
- Component
Version The defining characteristics of a specific version of an Amazon Web Services TOE component.
- Container
A container encapsulates the runtime environment for an application.
- Container
Distribution Configuration Container distribution settings for encryption, licensing, and sharing in a specific Region.
- Container
Recipe A container recipe.
- Container
Recipe Summary A summary of a container recipe
- Cvss
Score Amazon Inspector generates a risk score for each finding. This score helps you to prioritize findings, to focus on the most critical findings and the most vulnerable resources. The score uses the Common Vulnerability Scoring System (CVSS) format. This format is a modification of the base CVSS score that the National Vulnerability Database (NVD) provides. For more information about severity levels, see Severity levels for Amazon Inspector findings in the Amazon Inspector User Guide.
- Cvss
Score Adjustment Details about an adjustment that Amazon Inspector made to the CVSS score for a finding.
- Cvss
Score Details Details about the source of the score, and the factors that determined the adjustments to create the final score.
- Distribution
Defines the settings for a specific Region.
- Distribution
Configuration A distribution configuration.
- Distribution
Configuration Summary A high-level overview of a distribution configuration.
- EbsInstance
Block Device Specification Amazon EBS-specific block device mapping specifications.
- EcrConfiguration
Settings that Image Builder uses to configure the ECR repository and the output container images that Amazon Inspector scans.
- Fast
Launch Configuration Define and configure faster launching for output Windows AMIs.
- Fast
Launch Launch Template Specification Identifies the launch template that the associated Windows AMI uses for launching an instance when faster launching is enabled.
You can specify either the
launchTemplateName
or thelaunchTemplateId
, but not both.- Fast
Launch Snapshot Configuration Configuration settings for creating and managing pre-provisioned snapshots for a fast-launch enabled Windows AMI.
- Filter
A filter name and value pair that is used to return a more specific list of results from a list operation. Filters can be used to match a set of resources by specific criteria, such as tags, attributes, or IDs.
- Image
An Image Builder image. You must specify exactly one recipe for the image – either a container recipe (
containerRecipe
), which creates a container image, or an image recipe (imageRecipe
), which creates an AMI.- Image
Aggregation Contains vulnerability counts for a specific image.
- Image
Package A software package that's installed on top of the base image to create a customized image.
- Image
Pipeline Details of an image pipeline.
- Image
Pipeline Aggregation Contains vulnerability counts for a specific image pipeline.
- Image
Recipe An image recipe.
- Image
Recipe Summary A summary of an image recipe.
- Image
Scan Finding Contains details about a vulnerability scan finding.
- Image
Scan Finding Aggregation This returns exactly one type of aggregation, based on the filter that Image Builder applies in its API action.
- Image
Scan Findings Filter A name value pair that Image Builder applies to streamline results from the vulnerability scan findings list action.
- Image
Scan State Shows the vulnerability scan status for a specific image, and the reason for that status.
- Image
Scanning Configuration Contains settings for Image Builder image resource and container image scans.
- Image
State Image status and the reason for that status.
- Image
Summary An image summary.
- Image
Tests Configuration Configure image tests for your pipeline build. Tests run after building the image, to verify that the AMI or container image is valid before distributing it.
- Image
Version The defining characteristics of a specific version of an Image Builder image.
- Infrastructure
Configuration Details of the infrastructure configuration.
- Infrastructure
Configuration Summary The infrastructure used when building Amazon EC2 AMIs.
- Inspector
Score Details Information about the factors that influenced the score that Amazon Inspector assigned for a finding.
- Instance
Block Device Mapping Defines block device mappings for the instance used to configure your image.
- Instance
Configuration Defines a custom base AMI and block device mapping configurations of an instance used for building and testing container images.
- Instance
Metadata Options The instance metadata options that apply to the HTTP requests that pipeline builds use to launch EC2 build and test instances. For more information about instance metadata options, see Configure the instance metadata options in the Amazon EC2 User Guide for Linux instances, or Configure the instance metadata options in the Amazon EC2 Windows Guide for Windows instances.
- Launch
Permission Configuration Describes the configuration for a launch permission. The launch permission modification request is sent to the Amazon EC2 ModifyImageAttribute API on behalf of the user for each Region they have selected to distribute the AMI. To make an AMI public, set the launch permission authorized accounts to
all
. See the examples for making an AMI public at Amazon EC2 ModifyImageAttribute.- Launch
Template Configuration Identifies an Amazon EC2 launch template to use for a specific account.
- Lifecycle
Execution Contains metadata from a runtime instance of a lifecycle policy.
- Lifecycle
Execution Resource Contains details for a resource that the runtime instance of the lifecycle policy identified for action.
- Lifecycle
Execution Resource Action The lifecycle policy action that was identified for the impacted resource.
- Lifecycle
Execution Resource State Contains the state of an impacted resource that the runtime instance of the lifecycle policy identified for action.
- Lifecycle
Execution Resources Impacted Summary Contains details for an image resource that was identified for a lifecycle action.
- Lifecycle
Execution Snapshot Resource Contains the state of an impacted snapshot resource that the runtime instance of the lifecycle policy identified for action.
- Lifecycle
Execution State The current state of the runtime instance of the lifecycle policy.
- Lifecycle
Policy The configuration details for a lifecycle policy resource.
- Lifecycle
Policy Detail The configuration details for a lifecycle policy resource.
- Lifecycle
Policy Detail Action Contains selection criteria for the lifecycle policy.
- Lifecycle
Policy Detail Action Include Resources Specifies how the lifecycle policy should apply actions to selected resources.
- Lifecycle
Policy Detail Exclusion Rules Specifies resources that lifecycle policy actions should not apply to.
- Lifecycle
Policy Detail Exclusion Rules Amis Defines criteria for AMIs that are excluded from lifecycle actions.
- Lifecycle
Policy Detail Exclusion Rules Amis Last Launched Defines criteria to exclude AMIs from lifecycle actions based on the last time they were used to launch an instance.
- Lifecycle
Policy Detail Filter Defines filters that the lifecycle policy uses to determine impacted resource.
- Lifecycle
Policy Resource Selection Resource selection criteria for the lifecycle policy.
- Lifecycle
Policy Resource Selection Recipe Specifies an Image Builder recipe that the lifecycle policy uses for resource selection.
- Lifecycle
Policy Summary Contains a summary of lifecycle policy resources.
- Logging
Logging configuration defines where Image Builder uploads your logs.
- Output
Resources The resources produced by this image.
- Package
Vulnerability Details Information about package vulnerability findings.
- Placement
By default, EC2 instances run on shared tenancy hardware. This means that multiple Amazon Web Services accounts might share the same physical hardware. When you use dedicated hardware, the physical server that hosts your instances is dedicated to your Amazon Web Services account. Instance placement settings contain the details for the physical hardware where instances that Image Builder launches during image creation will run.
- Product
Code List Item Information about a single product code.
- Remediation
Information about how to remediate a finding.
- Remediation
Recommendation Details about the recommended course of action to remediate the finding.
- Resource
State The current state of an impacted resource.
- Resource
State Update Exclusion Rules Additional rules to specify resources that should be exempt from ad-hoc lifecycle actions.
- Resource
State Update Include Resources Specifies if the lifecycle policy should apply actions to selected resources.
- S3Export
Configuration Properties that configure export from your build instance to a compatible file format for your VM.
- S3Logs
Amazon S3 logging configuration.
- Schedule
A schedule configures when and how often a pipeline will automatically create a new image.
- Severity
Counts Includes counts by severity level for medium severity and higher level findings, plus a total for all of the findings for the specified filter.
- SsmParameter
Configuration Configuration for a single Parameter in the Amazon Web Services Systems Manager (SSM) Parameter Store in a given Region.
- Systems
Manager Agent Contains settings for the Systems Manager agent on your build instance.
- Target
Container Repository The container repository where the output container image is stored.
- Vulnerability
IdAggregation Includes counts of image and pipeline resource findings by vulnerability.
- Vulnerable
Package Information about a vulnerable package that Amazon Inspector identifies in a finding.
- Workflow
Defines a process that Image Builder uses to build and test images during the image creation process.
- Workflow
Configuration Contains control settings and configurable inputs for a workflow resource.
- Workflow
Execution Metadata Metadata that includes details and status from this runtime instance of the workflow.
- Workflow
Parameter Contains a key/value pair that sets the named workflow parameter.
- Workflow
Parameter Detail Defines a parameter that's used to provide configuration details for the workflow.
- Workflow
State A group of fields that describe the current status of workflow.
- Workflow
Step Execution Contains runtime details for an instance of a workflow that ran for the associated image build version.
- Workflow
Step Metadata Runtime details and status for the workflow step.
- Workflow
Summary Contains metadata about the workflow resource.
- Workflow
Version Contains details about this version of the workflow.
Enums§
- Build
Type - When writing a match expression against
BuildType
, 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. - Component
Format - When writing a match expression against
ComponentFormat
, 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. - Component
Status - When writing a match expression against
ComponentStatus
, 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. - Component
Type - When writing a match expression against
ComponentType
, 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. - Container
Repository Service - When writing a match expression against
ContainerRepositoryService
, 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. - Container
Type - When writing a match expression against
ContainerType
, 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. - Disk
Image Format - When writing a match expression against
DiskImageFormat
, 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. - EbsVolume
Type - When writing a match expression against
EbsVolumeType
, 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. - Image
Scan Status - When writing a match expression against
ImageScanStatus
, 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. - Image
Source - When writing a match expression against
ImageSource
, 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. - Image
Status - When writing a match expression against
ImageStatus
, 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. - Image
Type - When writing a match expression against
ImageType
, 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. - Lifecycle
Execution Resource Action Name - When writing a match expression against
LifecycleExecutionResourceActionName
, 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. - Lifecycle
Execution Resource Status - When writing a match expression against
LifecycleExecutionResourceStatus
, 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. - Lifecycle
Execution Status - When writing a match expression against
LifecycleExecutionStatus
, 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. - Lifecycle
Policy Detail Action Type - When writing a match expression against
LifecyclePolicyDetailActionType
, 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. - Lifecycle
Policy Detail Filter Type - When writing a match expression against
LifecyclePolicyDetailFilterType
, 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. - Lifecycle
Policy Resource Type - When writing a match expression against
LifecyclePolicyResourceType
, 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. - Lifecycle
Policy Status - When writing a match expression against
LifecyclePolicyStatus
, 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. - Lifecycle
Policy Time Unit - When writing a match expression against
LifecyclePolicyTimeUnit
, 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. - Marketplace
Resource Type - When writing a match expression against
MarketplaceResourceType
, 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. - OnWorkflow
Failure - When writing a match expression against
OnWorkflowFailure
, 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. - Ownership
- When writing a match expression against
Ownership
, 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. - Pipeline
Execution Start Condition - When writing a match expression against
PipelineExecutionStartCondition
, 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. - Pipeline
Status - When writing a match expression against
PipelineStatus
, 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. - Platform
- When writing a match expression against
Platform
, 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. - Product
Code Type - When writing a match expression against
ProductCodeType
, 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. - Resource
Status - When writing a match expression against
ResourceStatus
, 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. - SsmParameter
Data Type - When writing a match expression against
SsmParameterDataType
, 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. - Tenancy
Type - When writing a match expression against
TenancyType
, 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. - Workflow
Execution Status - When writing a match expression against
WorkflowExecutionStatus
, 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. - Workflow
Status - When writing a match expression against
WorkflowStatus
, 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. - Workflow
Step Action Type - When writing a match expression against
WorkflowStepActionType
, 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. - Workflow
Step Execution Rollback Status - When writing a match expression against
WorkflowStepExecutionRollbackStatus
, 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. - Workflow
Step Execution Status - When writing a match expression against
WorkflowStepExecutionStatus
, 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. - Workflow
Type - When writing a match expression against
WorkflowType
, 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.