AWS Replicator

Introduction

Infrastructure deployed on AWS often requires access to shared resources defined externally. For example a VPC defined by another team to contain the application infrastructure. This makes it harder to deploy applications into LocalStack as these resource dependencies must be deployed first. These dependencies may not live in IaC where deployment is easy, or accessing the IaC may not be easy. Some resources may be referred to by ARN, for example Secrets Manager secrets, but these ARNs are partly random meaning that simply creating a new resource in LocalStack will generate a resource with a different ARN.

LocalStack AWS Replicator creates identical copies of AWS resources in a running LocalStack instance. This means that external resources can easily be replicated before deploying the main application, and removes the need to change existing stacks or create custom infrastructure, making LocalStack setup easier.

Getting started

A valid LOCALSTACK_AUTH_TOKEN must be configured to start the LocalStack Pro image.

Retrieve credentials to access AWS

The AWS Replicator needs read access to your AWS account and performs a limited set of read-only operations on supported resources. These operations can be limited by creating a minimal IAM role with just the policy actions required for replication, and providing credentials to assume this role.

See the supported resources section for details of what policy actions are required for each resource.

When the replication is triggered using the LocalStack CLI, which must run in a shell configured to access AWS. Here are some options:

AWS CLI v2
AWS CLI v1

If you have the AWS CLI v2 installed, the CLI will read credentials from your configured AWS_PROFILE.

export AWS_PROFILE=my-aws-profile
localstack replicator ...

If you have the AWS CLI v1 installed or no installation of the AWS CLI, the following environment variables must be set:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN (optional)
AWS_DEFAULT_REGION

Trigger a replication job

Replication jobs can be triggered using the LocalStack CLI or an HTTP API. Both methods have two steps:

Submit a replication job.
Check the job status.

Using the LocalStack CLI

The Replicator CLI is part of the LocalStack CLI. Follow the installation instructions to set it up.

To start a replication job, get the ARN of the resource to replicate. Then, trigger the job using the command:

1
export LOCALSTACK_AUTH_TOKEN=<auth token>
2
export AWS_DEFAULT_REGION=...
3
# if required
4
# export AWS_ACCESS_KEY_ID=
5
# export AWS_SECRET_ACCESS_KEY=
6
localstack replicator start \
7
 --resource-type <resource-type> \
8
 --resource-identifier <identifier> \
9
 [--target-account-id <account-id>] \
10
 [--target-region-name <region-name>]

Resources that supports replicating with arn can be replicated by providing --resource-arn instead of --resource-type and --resource-identifier.

localstack replicator start --resource-arn <resource-arn>

This triggers the replication job. The output will look similar to:

1
{
2
  "job_id": "50005865-1589-4f6d-a720-c86f5a5dd021",
3
  "state": "TESTING_CONNECTION",
4
  "error_message": null,
5
  "type": "SINGLE_RESOURCE",
6
  "replication_config": {
7
    "resource_type": "AWS::SSM::PARAMETER",
8
    "identifier": "myParameter"
9
  }
10
}

Using the HTTP API

To trigger replication via the HTTP API, send a POST request to http://localhost.localstack.cloud:4566/_localstack/replicator/jobs with the following payload:

1
{
2
  "replication_type": "SINGLE_RESOURCE",
3
  "replication_job_config": {
4
    "resource_type": "<resource-type>",
5
    "identifier": "<identifier>"
6
  },
7
  "source_aws_config": {
8
    "aws_access_key_id": "...",
9
    "aws_secret_access_key": "...",
10
    "aws_session_token": "...", // optional
11
    "region_name": "...",
12
    "endpoint_url": "..." // optional
13
  },
14
  "target_aws_config": {} // optional, same shape as `source_aws_config`
15
}

Check Replication Job Status

Replication jobs run asynchronously, so you need to poll their status to check when they finish.

Using the LocalStack CLI

When creating a replication job, the response includes a job_id. Use this ID to check the job status:

export LOCALSTACK_AUTH_TOKEN=<auth token>

localstack replicator status <job-id>

This command returns the job status in JSON format, for example:

1
{
2
  "job_id": "50005865-1589-4f6d-a720-c86f5a5dd021",
3
  "state": "SUCCEEDED",
4
  "error_message": null,
5
  "type": "SINGLE_RESOURCE",
6
  "replication_config": {
7
    "resource_type": "AWS::SSM::PARAMETER",
8
    "identifier": "myParameter"
9
  }
10
}

For long-running jobs, the CLI can poll the status until the job reaches a terminal state. To wait for the job to finish, use the --follow flag.

Using the HTTP API

To check the status of a replication job via the HTTP API, send a GET request to http://localhost.localstack.cloud:4566/_localstack/replicator/jobs/<job-id>.

Quickstart

This quickstart example creates an SSM parameter in AWS and replicates it to LocalStack.

To start, create the parameter in AWS. This example uses an SSO profile named ls-sandbox for AWS configuration, and replicates resources from the eu-central-1 region.

AWS_PROFILE=ls-sandbox aws ssm put-parameter\
  --name myparam \
  --type String \
  --value abc123

{
    "Version": 1,
    "Tier": "Standard"
}

AWS_PROFILE=ls-sandbox aws ssm get-parameters --names myparam

1
{
2
    "Parameters": [
3
        {
4
            "Name": "myparam",
5
            "Type": "String",
6
            "Value": "abc123",
7
            "Version": 1,
8
            "LastModifiedDate": "2025-02-07T13:36:56.240000+00:00",
9
            "ARN": "arn:aws:ssm:eu-central-1:<account-id>:parameter/myparam",
10
            "DataType": "text"
11
        }
12
    ],
13
    "InvalidParameters": []
14
}

The SSM parameter has the ARN: arn:aws:ssm:eu-central-1:<account-id>:parameter/myparam.

Next, we can check that the parameter is not present in LocalStack using awslocal:

awslocal ssm get-parameters --name myparam

1
{
2
    "Parameters": [],
3
    "InvalidParameters": [
4
        "myparam"
5
    ]
6
}

Next, trigger replication from AWS to LocalStack. This example uses an SSO profile named ls-sandbox for AWS configuration.

LOCALSTACK_AUTH_TOKEN=<ls-auth-token> \
  AWS_PROFILE=ls-sandbox \
  localstack replicator start  \
    --resource-type AWS::SSM::Parameter \
 --resource-identifier <identifier> \

Configured credentials from the AWS CLI

1
{
2
  "job_id": "9acdc850-f71b-4474-b138-1668eb8b8396",
3
  "state": "TESTING_CONNECTION",
4
  "error_message": null,
5
  "type": "SINGLE_RESOURCE",
6
  "replication_config": {
7
    "resource_type": "AWS::SSM::PARAMETER",
8
    "identifier": "myparam"
9
  }
10
}

You can check the replication job status using the job_id:

LOCALSTACK_AUTH_TOKEN=<ls-auth-token> \
  localstack replicator status 9acdc850-f71b-4474-b138-1668eb8b8396

1
{
2
  "job_id": "9acdc850-f71b-4474-b138-1668eb8b8396",
3
  "state": "SUCCEEDED",
4
  "error_message": null,
5
  "type": "SINGLE_RESOURCE",
6
  "replication_config": {
7
    "resource_arn": "arn:aws:ssm:eu-central-1:<account-id>:parameter/myparam"
8
  }
9
}

The state is SUCCEEDED, indicating the replication job completed successfully. The SSM parameter is now accessible.

awslocal ssm get-parameters --name myparam --region eu-central-1

1
{
2
    "Parameters": [
3
        {
4
            "Name": "myparam",
5
            "Type": "String",
6
            "Value": "abc123",
7
            "Version": 1,
8
            "LastModifiedDate": 1738935663.08,
9
            "ARN": "arn:aws:ssm:eu-central-1:000000000000:parameter/myparam",
10
            "DataType": "text"
11
        }
12
    ],
13
    "InvalidParameters": []
14
}

The resource is replicated into the same AWS region by default. Use the --target-region-name flag to change it. By default, replication occurs in LocalStack account 000000000000. Use the --target-account-id flag to specify a different account.

Supported Resources

The project is still in preview state and we welcome feedback and bug reports. We have opened a github issue where you can request and upvote to help us prioritize our efforts and support the resources with the most impact. For any other requests or reports, please open a new github issue.

Resource Type	Service	Identifier	Required Actions	Arn Support
AWS::EC2::SecurityGroup	ec2	GroupId	cloudformation:GetResource ec2:DescribeSecurityGroups	✔️
AWS::EC2::Subnet	ec2	SubnetId	cloudformation:GetResource ec2:DescribeSubnets	✔️
AWS::EC2::VPC	ec2	VpcId	cloudformation:GetResource ec2:DescribeVpcs	✔️
AWS::ECR::Repository	ecr	RepositoryName:<ImageTag[Optional]>	cloudformation:GetResource ecr:BatchCheckLayerAvailability ecr:BatchGetImage ecr:DescribeRepositories ecr:GetAuthorizationToken ecr:GetDownloadUrlForLayer ecr:GetLifecyclePolicy ecr:GetRepositoryPolicy ecr:ListTagsForResource	✔️
AWS::IAM::Policy	iam	Arn	iam:GetPolicy	✔️
AWS::IAM::Role	iam	RoleName	cloudformation:GetResource iam:GetRole	✔️
AWS::KMS::Key	kms	KeyId	cloudformation:GetResource kms:DescribeKey	✔️
AWS::Lambda::LayerVersion	lambda	LayerVersionArn	cloudformation:GetResource lambda:GetLayerVersion	✔️
AWS::Route53::HostedZone	route53	Id	cloudformation:GetResource route53:GetHostedZone route53:ListQueryLoggingConfigs route53:ListTagsForResource	✔️
AWS::SSM::Parameter	ssm	Name	cloudformation:GetResource ssm:GetParameters	✔️
AWS::SecretsManager::Secret	secretsmanager	Arn	cloudformation:GetResource secretsmanager:DescribeSecret	✔️