resource/aws_datasync_location_s3: Add agent_arns and s3_storage_class arguments

[bflad]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

As part of the initial S3 on Outposts support for the Terraform AWS Provider, enhancements to the aws_datasync_location_s3 resource are necessary.

Existing Resource

• aws_datasync_location_s3

Potential Terraform Configuration

resource "aws_datasync_location_s3" "outposts" {
  agent_arns    = [aws_datasync_agent.example.arn]
  s3_bucket_arn = aws_s3_access_point.example.arn
  subdirectory  = "/"

  s3_config {
    bucket_access_role_arn = aws_iam_role.example.arn
  }
}

References

• Feature Request: S3 on Outposts Support
• New Resource: aws_s3control_bucket
• Update module aws/aws-sdk-go to v1.35.0
• DataSync API Reference
• AWS Go SDK v1.35.0
• AWS Go SDK service/datasync

[olgakogan]

Awesome! Note that for S3 on Outposts, DataSync only supports S3 Access Points, so the bucket ARN is an Acces Point ARN

[bflad]

Good catch, @olgakogan! Will update the example.

[cesarpball]

Do we have any update about s3_storage_class property?
Using local-exec to update the location is not an option as we can't do even in the AWS Console

[ewbankkit]

Related:

• storage class support for aws_datasync_location_s3 #19191

[ghost]

This has been released in version 3.40.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.