Jump to content

Search the Community

Showing results for tags 'replication'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Welcome New Members !
    • General Discussion
    • Site News
  • DevOps & SRE
    • DevOps & SRE General Discussion
    • Data Engineering, Data Science & AI
    • Development & Programming
    • CI/CD & GitOps
    • Docker, Containers, Microservices & Serverless
    • Infrastructure-as-Code
    • Kubernetes
    • Linux
    • Monitoring, Observability & Logging
    • Security
  • Cloud Providers
    • Amazon Web Services
    • Google Cloud Platform
    • Microsoft Azure
    • Red Hat OpenShift

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


LinkedIn Profile URL


About Me


Development Experience


Cloud Experience


Current Role


Skills


Certifications


Favourite Tools


Interests

Found 6 results

  1. MySQL provides several replication configuration options. However, ensuring it is done correctly may take time and effort, with considerable choices. Replication is a crucial initial step to enhance availability in MySQL databases. A properly designed replication architecture can significantly impact the accessibility of your data and prevent potential management complications. This article will delve into […] View the full article
  2. You now can use Amazon DynamoDB as a source data store with AWS Glue Elastic Views to combine and replicate data across multiple data stores—without having to write custom code. With AWS Glue Elastic Views, you can use Structured Query Language (SQL) to quickly create a virtual table—called a view—from multiple source data stores. Based on this view, AWS Glue Elastic Views copies data from each source data store and creates a replica—called a materialized view—in a target data store. AWS Glue Elastic Views monitors continuously for changes to data in your source data stores, and provides updates to your target data stores automatically, ensuring that data accessed through the materialized view is always up to date. View the full article
  3. Amazon S3 Replication now gives you the ability to replicate data from one source bucket to multiple destination buckets in the same, or different AWS Regions. S3 Replication (multi-destination) is intended for customers that want to create and maintain multiple copies of their data in one or more AWS Regions. Additionally, when replicating to multiple destinations, you can use Amazon CloudWatch metrics to track replication progress for each region pair. View the full article
  4. Amazon S3 Replication now gives you the flexibility of replicating object metadata changes for two-way replication between buckets. With this new feature, replica modification sync, you can easily replicate metadata changes like object access control lists (ACLs), object tags, or object locks on the replicated objects. This two-way replication is important if you want to build shared datasets across multiple regions and keep all object and object metadata changes in sync. View the full article
  5. Amazon S3 Replication now provides detailed metrics and notifications to monitor the status of object replication between buckets. You can monitor replication progress by tracking bytes pending, operations pending, and replication latency between your source and destination buckets using the S3 management console or Amazon CloudWatch. You can also set up S3 Event Notifications to receive replication failure notifications to quickly diagnose and correct configuration issues. S3 Replication metrics and notifications help you closely monitor replication progress. Previously, S3 Replication metrics and notifications were available with S3 Replication Time Control (S3 RTC). Beginning now, they can be enabled for all replication rules. View the full article
  6. Amazon S3 Replication is now able to replicate delete markers from one S3 bucket to another. For buckets that use S3 versioning, when a customer issues a delete request without a version ID specified, S3 adds a delete marker on the latest version of the object to protect data from accidental deletions. With S3 Replication, you can easily enable or disable the replication of these delete markers between source and destination buckets for each replication rule. This is critical for customers that have an active-active architecture within the same AWS Region or across different AWS Regions. View the full article
  • Forum Statistics

    39.8k
    Total Topics
    40k
    Total Posts
×
×
  • Create New...