Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amazon S3 Two-way Replication via Replica Modification Sync #16539

Closed
ewbankkit opened this issue Dec 2, 2020 · 6 comments
Closed

Amazon S3 Two-way Replication via Replica Modification Sync #16539

ewbankkit opened this issue Dec 2, 2020 · 6 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@ewbankkit
Copy link
Contributor

ewbankkit commented Dec 2, 2020

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

Amazon S3 Replication now gives you the flexibility of replicating object metadata changes for two-way replication between buckets.
Amazon S3 replica modification sync can help you keep object metadata such as tags, ACLs, and Object Lock settings replicated between replicas and source objects.

New or Affected Resource(s)

Potential Terraform Configuration

resource "aws_s3_bucket" "source" {
  bucket = "example"

  versioning {
    enabled = true
  }

  replication_configuration {
    role = aws_iam_role.replication.arn

    rules {
      id     = "foobar"
      prefix = "foo"
      status = "Enabled"

      source_selection_criteria {
        replica_modifications {
          Status = "Enabled"
        }
      }

      destination {
        bucket        = aws_s3_bucket.destination.arn
        storage_class = "STANDARD"
      }
    }
  }
}

References

Announcement.
Developer Guide.

@ewbankkit ewbankkit added the enhancement Requests to existing resources that expand the functionality or scope. label Dec 2, 2020
@bflad bflad added the service/s3 Issues and PRs that pertain to the s3 service. label Dec 2, 2020
@ewbankkit ewbankkit changed the title Amazon S3 Replica Modification Sync Amazon S3 Two-way Replication via Replica Modification Sync Dec 2, 2020
@Kanikamiglani31
Copy link

Hello team, Do we have this feature working in terraform? I am looking for both "Delete marker replication" & "Replica modification sync" in terraform.

@Kanikamiglani31
Copy link

Hey all,

Meanwhile this can be achieved from local-exec and template_file with aws-cli.

The solution is present in the answer below:

https://stackoverflow.com/questions/67729643/how-can-we-enable-amazon-s3-replication-modification-sync-in-terraform/67792274#67792274

@tmccombs
Copy link
Contributor

tmccombs commented Jun 2, 2021

Meanwhile this can be achieved from local-exec and template_file with aws-cli.

As I've mentioned on other issues, that workaround doesn't work very well if you use a provider that assumes an IAM role.

@anGie44
Copy link
Contributor

anGie44 commented Apr 12, 2022

Noting here that while not available in the S3 bucket resource, replication_modifications is available in the standalone resource aws_s3_bucket_replication_configuration , available since v3.66.0 of the Terraform AWS Provider. Latest argument reference available here: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_replication_configuration#source_selection_criteria

Copy link

github-actions bot commented Apr 1, 2024

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 1, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Copy link

github-actions bot commented Jun 5, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/s3 Issues and PRs that pertain to the s3 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

5 participants