aws_s3_object idempotency issue

[quentin9696]

Terraform and AWS Provider Version

Terraform v1.13.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v6.13.0

Affected Resource(s) or Data Source(s)

• aws_s3_object

Expected Behavior

Attribute and argument consistent when apply twice

Actual Behavior

TF show the following diff

      ~ metadata                      = null -> {}
      ~ tags                          = null -> {}
      ~ version_id                    = "" -> "null"

Please note that version_id isn't affected if the bucket version is disabled

Relevant Error/Panic Output

  ~ aws_s3_object = {
        id                            = "mybucket"
      ~ metadata                      = null -> {}
      ~ tags                          = null -> {}
      ~ version_id                    = "" -> "null"
        # (32 unchanged attributes hidden)
    }

Sample Terraform Configuration

Click to expand configuration

provider "aws" {
  region = "us-east-1"
}

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6"
    }
  }
}

resource "aws_s3_bucket" "this" {
  bucket = "mybucket"
  force_destroy = true
}

resource "aws_s3_bucket_versioning" "this" {
  bucket = aws_s3_bucket.this.id
  versioning_configuration {
    status = "Enabled"
  }
}

resource "aws_s3_object" "this" {
  bucket = aws_s3_bucket.this.id
  key    = "foo"
  content = "foo"
}

output "aws_s3_object" {
  value = aws_s3_object.this
}

Steps to Reproduce

1. Apply
2. Apply a second time without any modification

Debug Logging

No response

GenAI / LLM Assisted Development

n/a

Important Facts and References

No response

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue 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 Issue 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 Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.