feat(imagebuilder): support image pipeline executions

[tarunb12]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

None

Description

Adds support for invoking Image Builder pipelines directly when creating aws_imagebuilder_image resources through a new image_pipeline_execution_settings configuration block.

This enhancement provides an alternative method for creating images by triggering an existing image pipeline execution, rather than requiring users to specify individual recipe and infrastructure configurations. When image_pipeline_execution_settings is used, the resource calls the StartImagePipelineExecution API to invoke the pipeline and create the image.

Key changes:

• Added image_pipeline_execution_settings configuration block to aws_imagebuilder_image resource
  • Contains image_pipeline_arn parameter to reference the pipeline to invoke
• Modified resource creation logic to use StartImagePipelineExecution API when pipeline execution settings are provided
• Made infrastructure_configuration_arn optional (only required for recipe-based creation)
• Added mutual exclusivity validation between pipeline execution settings and recipe-based parameters
• Updated documentation with examples showing both creation methods

Usage example:

resource "aws_imagebuilder_image_pipeline" "example" {
  image_recipe_arn                 = aws_imagebuilder_image_recipe.example.arn
  infrastructure_configuration_arn = aws_imagebuilder_infrastructure_configuration.example.arn
  name                             = "example"
}

resource "aws_imagebuilder_image" "example" {
  image_pipeline_execution_settings {
    image_pipeline_arn = aws_imagebuilder_image_pipeline.example.arn
  }

  tags = {
    Name = "example"
  }
}

Relations

Closes #33212

References

• API Documentation: StartImagePipelineExecution

Output from Acceptance Testing

% make testacc TESTS=TestAccImageBuilderImage_pipelineExecutionSettings PKG=imagebuilder                                    
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running acceptance tests on branch: 🌿 f-aws_imagebuilder_image-start-pipeline 🌿...
TF_ACC=1 go1.24.11 test ./internal/service/imagebuilder/... -v -count 1 -parallel 20 -run='TestAccImageBuilderImage_pipelineExecutionSettings'  -timeout 360m -vet=off
2025/12/10 22:48:14 Creating Terraform AWS Provider (SDKv2-style)...
2025/12/10 22:48:14 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccImageBuilderImage_pipelineExecutionSettings
=== PAUSE TestAccImageBuilderImage_pipelineExecutionSettings
=== RUN   TestAccImageBuilderImage_pipelineExecutionSettings_tags
=== PAUSE TestAccImageBuilderImage_pipelineExecutionSettings_tags
=== RUN   TestAccImageBuilderImage_pipelineExecutionSettings_disappears
=== PAUSE TestAccImageBuilderImage_pipelineExecutionSettings_disappears
=== CONT  TestAccImageBuilderImage_pipelineExecutionSettings
=== CONT  TestAccImageBuilderImage_pipelineExecutionSettings_disappears
=== CONT  TestAccImageBuilderImage_pipelineExecutionSettings_tags
--- PASS: TestAccImageBuilderImage_pipelineExecutionSettings_disappears (783.18s)
--- PASS: TestAccImageBuilderImage_pipelineExecutionSettings (911.17s)
--- PASS: TestAccImageBuilderImage_pipelineExecutionSettings_tags (1081.31s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/imagebuilder       1081.521s

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.