[mvincentbb]

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 a new resource, aws_datazone_environment_blueprint, for creating and managing a custom Amazon DataZone environment blueprint (CreateEnvironmentBlueprint). The provider already has aws_datazone_environment_blueprint_configuration (enables an existing blueprint) and the aws_datazone_environment_blueprint data source (looks one up), but no resource to create a custom blueprint.

• Arguments: domain_identifier and name are required and force replacement. provisioning_properties.cloud_formation.template_url is required. description and user_parameters are optional and update in place.
• Computed attributes: id, blueprint_category, created_at, glossary_terms, provider_name, updated_at.
• description / user_parameters removal: UpdateEnvironmentBlueprint keeps omitted fields. The resource sends "" when description is removed and an empty list when user_parameters is removed, so removal reaches the API.
• Update gating: a timeouts-only change does not call UpdateEnvironmentBlueprint.
• Resource identity: parameterized identity on domain_identifier and id. Import supports both identity and the domain_identifier,id ID.
• Sweeper: deletes custom (managed = false) blueprints in each domain. It is registered as a dependency of the domain sweeper, so blueprints are removed before their domain.

AI usage disclosure

• An AI coding agent (Kiro) helped me write the resource code, the acceptance tests, the docs, the sweeper and the changelog entry. It followed the existing DataZone resources as patterns.
• I used OpenAI Codex /review on the branch twice before opening this PR and I fixed its findings.
• I reviewed every line. I ran the acceptance tests against a real AWS account (output below), plus gofmt, vet, semgrep, providerlint and copyright checks.
• I take full responsibility for this change and can explain it in my own words.

Relations

Closes #50433

References

• CreateEnvironmentBlueprint API

Output from Acceptance Testing

The identity tests skip locally (they need Terraform 1.12; my host has 1.9.8).

% make testacc TESTS=TestAccDataZoneEnvironmentBlueprint_ PKG=datazone

=== RUN   TestAccDataZoneEnvironmentBlueprint_Identity_basic
=== RUN   TestAccDataZoneEnvironmentBlueprint_Identity_regionOverride
=== RUN   TestAccDataZoneEnvironmentBlueprint_basic
=== RUN   TestAccDataZoneEnvironmentBlueprint_update
=== RUN   TestAccDataZoneEnvironmentBlueprint_disappears
=== RUN   TestAccDataZoneEnvironmentBlueprint_userParameters
    environment_blueprint_identity_gen_test.go:32: Terraform CLI version 1.9.8 is below minimum version 1.12.0: skipping test
--- SKIP: TestAccDataZoneEnvironmentBlueprint_Identity_basic (0.48s)
    environment_blueprint_identity_gen_test.go:126: Terraform CLI version 1.9.8 is below minimum version 1.12.0: skipping test
--- SKIP: TestAccDataZoneEnvironmentBlueprint_Identity_regionOverride (0.11s)
--- PASS: TestAccDataZoneEnvironmentBlueprint_disappears (28.70s)
--- PASS: TestAccDataZoneEnvironmentBlueprint_basic (40.22s)
--- PASS: TestAccDataZoneEnvironmentBlueprint_userParameters (51.68s)
--- PASS: TestAccDataZoneEnvironmentBlueprint_update (53.96s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/datazone	54.225s

[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.