You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A LocalStack extension to proxy and integrate AWS resources into your local machine.
6
6
This enables one flavor of "hybrid" or "remocal" setups where you can easily bridge the gap between LocalStack (local resources) and remote AWS (resources in the real cloud).
7
7
8
8
⚠️ Please note that this extension is experimental and still under active development.
9
9
10
-
⚠️ Note: Given that the scope of this extension has recently changed (see [below](#resource-replicator-cli-deprecated)), it may get renamed from `aws-replicator` to `cloud-proxy` in an upcoming release.
10
+
⚠️ Note: Given that the scope of this extension has recently changed (see [below](#resource-replicator-cli-deprecated)) - it has been renamed from `aws-replicator` to `aws-proxy`.
11
11
12
12
## Prerequisites
13
13
@@ -33,11 +33,11 @@ For example, in order to forward all API calls for DynamoDB/S3/Cognito to real A
33
33
```
34
34
$ localstack start -d
35
35
```
36
-
2. Enable LocalStack AWS replicator from the Web Application Extension Library
36
+
2. Enable LocalStack AWS Proxy from the Web Application Extension Library
37
37
3. After installation restart Localstack
38
-
4. Install the AWS replicator CLI package
38
+
4. Install the AWS Proxy CLI package
39
39
```
40
-
$ pip install localstack-extension-aws-replicator
40
+
$ pip install localstack-extension-aws-proxy
41
41
```
42
42
5. Configure real cloud account credentials in a new terminal session to allow access
2. Enable Localstack AWS replicator from the Web Application Extension Library
59
+
2. Enable Localstack AWS Proxy from the Web Application Extension Library
60
60
61
-
3. Once the extension is installed, it will expose a small configuration endpoint in your LocalStack container under the following endpoint: http://localhost:4566/_localstack/aws-replicator/index.html .
61
+
3. Once the extension is installed, it will expose a small configuration endpoint in your LocalStack container under the following endpoint: http://localhost:4566/_localstack/aws-proxy/index.html .
62
62
63
63
4. Use this Web UI to define the proxy configuration (in YAML syntax), as well as the AWS credentials (AWS access key ID, secret access key, and optionally session token) and save configuration. The proxy should report enabled state and on the host a proxy container should spawn.
64
64
@@ -111,22 +111,23 @@ A more comprehensive sample, involving local Lambda functions combined with remo
111
111
### Configuration
112
112
113
113
In addition to the proxy services configuration shown above, the following configs can be used to customize the behavior of the extension itself (simply pass them as environment variables to the main LocalStack container):
114
-
*`REPLICATOR_CLEANUP_PROXY_CONTAINERS`: whether to clean up (remove) the proxy Docker containers once they shut down (default `1`). Can be set to `0` to help debug issues, e.g., if a proxy container starts up and exits immediately.
115
-
*`REPLICATOR_LOCALSTACK_HOST`: the target host to use when the proxy container connects to the LocalStack main container (automatically determined by default)
116
-
*`REPLICATOR_PROXY_DOCKER_FLAGS`: additional flags that should be passed when creating the proxy Docker containers
114
+
*`PROXY_CLEANUP_CONTAINERS`: whether to clean up (remove) the proxy Docker containers once they shut down (default `1`). Can be set to `0` to help debug issues, e.g., if a proxy container starts up and exits immediately.
115
+
*`PROXY_LOCALSTACK_HOST`: the target host to use when the proxy container connects to the LocalStack main container (automatically determined by default)
116
+
*`PROXY_DOCKER_FLAGS`: additional flags that should be passed when creating the proxy Docker containers
117
117
118
118
**Note:** Due to some recent changes in the core framework, make sure to start up your LocalStack container with the `GATEWAY_SERVER=hypercorn` configuration enabled, for backwards compatibility. This will be fixed in an upcoming release.
119
119
120
120
## Resource Replicator CLI (deprecated)
121
121
122
122
Note: Previous versions of this extension also offered a "replicate" mode to copy/clone (rather than proxy) resources from an AWS account into the local instance.
123
-
This functionality has been removed from this extension, and is now being migrated to a new extension (more details following soon).
123
+
This functionality has been removed from this extension, and is now available directly in the LocalStack Pro image (see [here](https://docs.localstack.cloud/aws/tooling/aws-replicator)).
124
124
125
125
If you wish to access the deprecated instructions, they can be found [here](https://github.com/localstack/localstack-extensions/blob/fe0c97e8a9d94f72c80358493e51ce6c1da535dc/aws-replicator/README.md#resource-replicator-cli).
126
126
127
127
## Change Log
128
128
129
-
*`0.1.25`: Fix dynamodb proxying for read-only mode.
129
+
*`0.2.0`: Rename extension from `localstack-extension-aws-replicator` to `localstack-extension-aws-proxy`
130
+
*`0.1.25`: Fix dynamodb proxying for read-only mode
130
131
*`0.1.24`: Fix healthcheck probe for proxy container
131
132
*`0.1.23`: Fix unpinned React.js dependencies preventing webui from loading
132
133
*`0.1.22`: Fix auth-related imports that prevent the AWS proxy from starting
0 commit comments