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 August to October 2021, 573 Pull Requests were opened in the provider and 465 were merged, adding support for:
- Amazon Chime
- Amazon Connect
- Amazon AppStream 2.0
- Route 53 Recovery Control
- Graviton2 support for Lambda
- S3 Replication Time Control
We also launched a fully generated provider, the AWS Cloud Control (AWSCC) provider for Terraform. The AWSCC provider is currently in Technical Preview. Please check it out and let us know what you think.
From November ‘21- January ‘22, we will be prioritizing the following areas of work:
Issue: #20433
The next major release of the provider will include the adoption of the AWS Go SDK v2.0 as well as a refactor of one of our oldest and most used resources: S3.
There will also be the usual deprecations and sometimes breaking changes to existing resources which are necessary to maintain consistency of behavior across resources. Our goal is to focus on standardization to reduce technical debt and lay a strong foundation for future enhancement initiatives within the provider.
For details of the changes in full please refer to #20433. We would love to hear your feedback.
- Support for Managing Amazon CloudSearch Domains
- aws_config_remediation_configuration: No support for "automatic" remediation
- S3 Intelligent-Tiering Archive configuration
- IoT Thing Group
- Add resource for CodeCommit approval rule templates
- aws_dlm_lifecycle_policy - Implement support for "Cross Region copy"
- Add a data source for aws_key_pair
- Support ECS TaskSet
- Support for AthenaEngineVersion option in Athena work groups
- ECS Service can't update desired replicas when Blue Green deployment is enabled
- Add connection termination control to AWS LB target group
- WAFv2: Added support for custom response bodies
- New Resource aws_route53domains_domain
- Add aws_cognito_user resource
- AWS dynamodb table: restore from point in time
- Added
retainparameter toaws_lambda_layer_versionresource - New Resource: aws_lambda_layer_version_permission
- resoure/aws_lb: Support WAF fial open
- aws_elb & aws_lb: Add desync_mitigation_mode
- Implement object lambda access points for S3
- WAFv2: Added support for label_match_statement and rule_label
- Cloudtrail: Exclude Management Event Sources
- Retry S3 OperationAborted errors
- aws_dms_endpoint: support for secrets id for oracle and postgres
- Add support for private_ip_list
- aws_emr_cluster: Fix aws_emr_security_configuration destroy issues
- New Resource: aws_ecrpublic_repository_policy
- aws_ecs_task_definition overwrites previous revision
- Order is lost for data aws_iam_policy_document when applied to S3 buckets, iam roles, kms keys
- aws_ecs_cluster with capacity_providers cannot be destroyed
- Support for Account Settings Flags
- Execute AWS Lambda Only Once
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.
Adding resources, datasources and test files to the provider is a repetitive task which should be automated to ensure consistency and speed up contributor and maintainer workflow. A simple cli tool should be able to generate these files in place, and ensure that any code reference additions required (ie adding to provider.go) are performed as part of the process.
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.