eCreatorsTech

Our Services

In today’s ever-connected digital world, ensuring seamless access to data and maintaining high availability is crucial for businesses. One way to achieve this for your Amazon S3 data is by implementing a robust disaster recovery (DR) strategy. This article will guide you through the process of using S3 Multi-Region Access Points (MRAP) to set up an effective DR strategy without changing bucket names, simplifying management, and providing automatic failover.

Why Use Multi-Region Access Points?

S3 Multi-Region Access Points allow you to configure a single global endpoint that can route requests to multiple S3 buckets across different AWS regions. This provides several benefits:

• Simplified Management: No need for complex DNS configurations.
• Automatic Failover: Requests are automatically routed to the nearest available bucket.
• Consistent Access Patterns: Applications can use a single endpoint regardless of the data’s physical location.
• Improved Performance: Requests are routed based on factors like latency or cost.

 

Step-by-Step Guide

1. Create Buckets

First, create two S3 buckets: one in your primary region and another in your DR region.

• Primary Region: primary-bucket
• DR Region: dr-bucket

2. Set Up Replication

Configure cross-region replication from the primary bucket to the DR bucket. This ensures that any data written to the primary bucket is automatically replicated to the DR bucket.

aws s3api put-bucket-replication --bucket primary-bucket --replication-configuration file://replication-config.json

3. Create and Configure Multi-Region Access Point

Create an MRAP that includes both the primary and DR buckets.

aws s3control create-multi-region-access-point --account-id your-aws-account-id --details file://mrap-config.json

Configure routing policies for the MRAP to optimize for factors like lowest latency or network cost.

4. Update Application to Use MRAP

Instead of using individual bucket names or custom DNS configurations, update your application to use the MRAP ARN or alias.

import software.amazon.awssdk.auth.credentials.DefaultCredentialsProvider;
import software.amazon.awssdk.regions.Region;
import software.amazon.awssdk.services.s3.S3Client;
import software.amazon.awssdk.services.s3control.S3ControlClient;
import software.amazon.awssdk.services.s3control.model.GetMultiRegionAccessPointRequest;
import software.amazon.awssdk.services.s3control.model.GetMultiRegionAccessPointResponse;
import java.net.URI;

public class MrapS3Client {

    public static S3Client createMrapS3Client() {
        String accountId = "your-aws-account-id";
        String mrapName = "your-mrap-name";
        Region region = Region.AWS_GLOBAL; // MRAP uses the global endpoint

        // First, get the MRAP alias
        S3ControlClient s3ControlClient = S3ControlClient.builder()
                .region(region)
                .credentialsProvider(DefaultCredentialsProvider.create())
                .build();

        GetMultiRegionAccessPointRequest getMrapRequest = GetMultiRegionAccessPointRequest.builder()
                .accountId(accountId)
                .name(mrapName)
                .build();

        GetMultiRegionAccessPointResponse getMrapResponse = s3ControlClient.getMultiRegionAccessPoint(getMrapRequest);
        String mrapAlias = getMrapResponse.multiRegionAccessPoint().alias();

        // Now create the S3 client using the MRAP alias
        return S3Client.builder()
                .region(region)
                .credentialsProvider(DefaultCredentialsProvider.create())
                .endpointOverride(URI.create("https://" + mrapAlias + ".accesspoint.s3-global.amazonaws.com"))
                .build();
    }
}

Using the MRAP S3 Client:

public class S3Example {
    public static void main(String[] args) {
        S3Client s3 = MrapS3Client.createMrapS3Client();

        String key = "path/to/your/object";

        GetObjectRequest getObjectRequest = GetObjectRequest.builder()
                .bucket("arn:aws:s3::123456789012:accesspoint/mrapname") // Use the MRAP ARN
                .key(key)
                .build();

        ResponseInputStream<GetObjectResponse> response = s3.getObject(getObjectRequest);
        // Process the response...
    }
}

 

This setup ensures that the application always uses the MRAP to access S3 data, allowing AWS to handle the routing and failover between regions automatically. The bucket names remain consistent within each region, and we don’t need to change any configuration in the application during a failover event.

Key Benefits of Using MRAP for S3 Disaster Recovery

1. Simplified Management: No need for custom DNS failover configuration.
2. Automatic Failover: Requests are routed to the nearest available bucket.
3. Consistent Access Pattern: Use a single MRAP ARN across your application.
4. Improved Performance: Requests are routed based on lowest latency or cost.
5. Scalability: Easily add or remove regions from your MRAP configuration.

 

By implementing S3 Multi-Region Access Points, you can ensure high availability and seamless access to your data across multiple regions, enhancing your disaster recovery strategy without the complexity of managing individual bucket names or custom DNS configurations.