Every few months, the team will highlight areas of focus for our work and upcoming research.
We select items for inclusion in the roadmap from the Top Community Issues, Core Services, and internal priorities. Where community sourced contributions exist we will work with the authors to review and merge their work. Where this does not exist or the original contributors are not available we will create the resources and implementation ourselves.
Each weekly release will include necessary tasks that lead to the completion of the stated goals as well as community pull requests, enhancements, and features that are not highlighted in the roadmap. To view all the items we've prioritized for this quarter, please see the Roadmap milestone.
This roadmap does not describe all the work that will be included within this timeframe, but it does describe our focus. We will include other work as events occur.
In the period spanning February to April 2022, 912 Pull Requests were opened in the provider and 839 were closed/merged, adding support for:
- Amazon OpenSearch
- AWS Cost Categories
- AWS AppFlow
- Amazon Managed Grafana
- Amazon Global Networks
- Lambda Function URLs
From May ‘22 - July ‘22, we will be prioritizing the following areas of work:
Issue: #18865
Amazon Transcribe is an automatic speech recognition service that makes it easy to add speech to text capabilities to any application. Transcribe’s features enable you to ingest audio input, produce easy to read and review transcripts, improve accuracy with customization, and filter content to ensure customer privacy.
Support for Amazon Transcribe will include:
New Resource(s):
aws_transcribe_language_model
aws_transcribe_medical_vocabulary
aws_transcribe_vocabulary
aws_transcribe_vocabulary_filter
Issue: #18864
Amazon Comprehend is a natural-language processing (NLP) service that uses machine learning to uncover valuable insights and connections in text.
Support for Amazon Comprehend will include:
New Resource(s):
aws_comprehend_endpoint
aws_comprehend_entity_recognizer
aws_comprehend_document_classifier
Issue: #24478
Amazon Textract is a machine learning (ML) service that automatically extracts text, handwriting, and data from scanned documents.
New Resource(s):
- TBD
Issue: #13367
Amazon Kendra is an intelligent search service powered by machine learning (ML).
Support for Amazon Kendra will include:
New Resource(s):
aws_kendra_index
aws_kendra_query_suggestion_block_list
aws_kendra_thesaurus
- Lake Formation Tag-Based Access Control
- Amazon Managed Apache Cassandra Service / Keyspaces
- Assignment multiple users or groups via aws_ssoadmin_account_assignment
- Add support for regex_match_statement to AWS WAF v2 ACL rules
- Introduce custom timeout when waiting for aws_ecs_service to reach a steady state
- r/aws_wafv2_web_acl: add support for captcha in rule actions #21766
- Terraform seems to ignore "skip_final_snapshot" for rds cluster
- Provider produced inconsistent final plan / an invalid new value for .tags_all
- Support for Reserved Instances
- Cost Explorer
- Directory Service Shared Directory Support
- New Feature: Launch AWS Marketplace products in linked AWS accounts
- Don't mark non SecureString SSM parameters as sensitive
- FIS Experiment Template
- AWS Inspector Enable Service Feature
- Fix aws_iam_policy_document order
- Need SSM update-service-setting equivalent
- Add data sources for Managed Rules for WAF and WAF Regional
- Add aws_acmpca_permission resource
- Terraform AWS Provider does not support CopyDBSnapshot
- Access Analyzer archive_rule
- Add new resource_aws_lightsail_container_service
- Add resource aws_db_snapshot_copy
- Dualstack prefix forcibly removed from ALIAS records
- Add LoadBasedAutoscaling to OpsWorks Layer
- Allow setting custom domain for click/open tracking as part of SES Event destination resource
- Aws_inspector_assessment_template ability to send findings to SNS topic
- data_source/aws_ecr_lifecycle_policy_document: adding new data source for ECR
Research topics include features, architectural changes, and ideas that we are pursuing in the longer term that may significantly impact the core user experience of the AWS provider. Research topics are discovery only and are not guaranteed to be included in a future release.
Pull Request: #23948
Prototyping the ability to combine resources and data sources implemented in either Terraform Plugin SDK v2 or Terraform Plugin Framework using terraform-plugin-mux
.
Issue: #469
Currently the awscc
provider documentation that lives on the registry is generated from the CloudFormation Cloud Control API schema. This means that we are limited to attribute level and resource level descriptions that are quite terse. The aws
Provider has rich, contributor drafted documentation which includes examples, notes, and guides that make for a much more positive user experience.
While resource behavior in awscc
should remain wholly generated, we would like to enable contributors to append information to the generated documentation in order to foster an improved experience more inline with what Terraform practitioners are used to.
The product-development initiatives in this document reflect HashiCorp's current plans and are subject to change and/or cancellation in HashiCorp's sole discretion.