aws-proxy: remove source code, keep README with PyPI install instructions

Code has moved elsewhere; the extension directory now contains only a
README pointing users to install via `localstack extensions install`.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: whummer

aws-proxy/AGENTS.md

@@ -1,37 +1,34 @@
-AWS Cloud Proxy Extension (experimental)
-========================================
+AWS Cloud Proxy Extension
+=========================
 [![Install LocalStack Extension](https://localstack.cloud/gh/extension-badge.svg)](https://app.localstack.cloud/extensions/remote?url=git+https://github.com/localstack/localstack-extensions/#egg=localstack-extension-aws-proxy&subdirectory=aws-proxy)
 
 A LocalStack extension to proxy and integrate AWS resources into your local machine.
 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).
 
-⚠️ Please note that this extension is experimental and still under active development.
-
-⚠️ 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`.
-
 ## Prerequisites
 
 * LocalStack Pro
 * Docker
 * Python
 
-## AWS Cloud Proxy
+## Installation
 
-The AWS Cloud Proxy can be used to forward certain API calls in LocalStack to real AWS, in order to enable seamless transition between local and remote resources.
+Install the extension via the LocalStack CLI:
 
-**Warning:** Be careful when using the proxy - make sure to _never_ give access to production accounts or any critical/sensitive data!
+```bash
+localstack extensions install localstack-extension-aws-proxy
+```
 
-### Usage
+After installation, restart LocalStack for the extension to take effect.
 
-#### Using curl (API)
+## Usage
 
-The proxy can be enabled and disabled via the LocalStack internal API. This is the recommended approach.
+### Enable the proxy
 
-1. Start LocalStack and install the AWS Proxy extension (restart LocalStack after installation).
+Enable the proxy for specific services (e.g., DynamoDB, S3, Cognito) by posting a configuration along with your AWS credentials:
 
-2. Enable the proxy for specific services (e.g., DynamoDB, S3, Cognito) by posting a configuration along with your AWS credentials:
-```
-$ curl -X POST http://localhost:4566/_localstack/aws/proxies \
+```bash
+curl -X POST http://localhost:4566/_localstack/aws/proxies \
   -H 'Content-Type: application/json' \
   -d '{
     "config": {
@@ -49,114 +46,29 @@ $ curl -X POST http://localhost:4566/_localstack/aws/proxies \
   }'
 ```
 
-3. Check the proxy status:
-```
-$ curl http://localhost:4566/_localstack/aws/proxies/status
-```
+### Check proxy status
 
-4. Disable the proxy:
+```bash
+curl http://localhost:4566/_localstack/aws/proxies/status
 ```
-$ curl -X POST http://localhost:4566/_localstack/aws/proxies/status \
-  -H 'Content-Type: application/json' \
-  -d '{"status": "disabled"}'
-```
-
-5. Now, when issuing an API call against LocalStack (e.g., via `awslocal`), the invocation gets forwarded to real AWS and should return data from your real cloud resources.
-
-#### Using the LocalStack Web App
 
-You can also configure the proxy from the LocalStack Web App at https://app.localstack.cloud. Navigate to your instance and use the AWS Proxy extension settings to enable/disable the proxy and manage credentials.
+### Disable the proxy
 
-Alternatively, the extension exposes a local configuration UI at http://localhost:4566/_localstack/aws-proxy/index.html (requires starting LocalStack with `EXTRA_CORS_ALLOWED_ORIGINS=https://aws-proxy.localhost.localstack.cloud:4566`). Use this Web UI to define the proxy configuration (in YAML syntax) and AWS credentials, then save the configuration. To clean up the running proxy container, click "disable" in the UI.
-
-![configuration settings](etc/proxy-settings.png)
-
-### Resource-specific proxying
-
-As an alternative to forwarding _all_ requests for a particular service, you can also proxy only requests for _specific_ resources to AWS.
-
-For example, assume we own an S3 bucket `my-s3-bucket` in AWS, then we can use the following configuration to forward any requests to `s3://my-s3-bucket` to real AWS, while still handling requests to all other buckets locally in LocalStack:
-```
-services:
-  s3:
-    resources:
-      # list of ARNs of S3 buckets to proxy to real AWS
-      - '.*:my-s3-bucket'
-    operations:
-      # list of operation name regex patterns (optional)
-      - 'Get.*'
-      - 'Put.*'
-    # optionally, specify that only read requests should be allowed (Get*/List*/Describe*, etc)
-    read_only: false
-    # optionally, allow invoke/execute operations (e.g., Lambda invocations) alongside read_only mode.
-    # execute operations have side-effects and are deliberately excluded from read_only by default.
-    execute: false
+```bash
+curl -X POST http://localhost:4566/_localstack/aws/proxies/status \
+  -H 'Content-Type: application/json' \
+  -d '{"status": "disabled"}'
 ```
 
-Pass this configuration in the `config` field of the `POST /_localstack/aws/proxies` request body (as shown above).
+Once enabled, API calls against LocalStack (e.g., via `awslocal`) are forwarded to real AWS and return data from your real cloud resources.
 
-If we then perform local operations against the S3 bucket `my-s3-bucket`, the proxy will forward the request and will return the results from real AWS:
-```
-$ awslocal s3 ls s3://my-s3-bucket
-2023-05-14 15:53:40        148 my-file-1.txt
-2023-05-15 10:24:43         22 my-file-2.txt
-```
+## Configuration
 
-Any other S3 requests targeting other buckets will be run against the local state in LocalStack itself, for example:
-```
-$ awslocal s3 mb s3://test123
-make_bucket: test123
-...
-```
+The following environment variables can be passed to the LocalStack container to customize behavior:
 
-A more comprehensive sample, involving local Lambda functions combined with remote SQS queues and S3 buckets, can be found in the `example` folder of this repo.
-
-### Configuration
-
-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):
-* `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.
-* `PROXY_LOCALSTACK_HOST`: the target host to use when the proxy container connects to the LocalStack main container (automatically determined by default)
-* `PROXY_DOCKER_FLAGS`: additional flags that should be passed when creating the proxy Docker containers
-
-## Resource Replicator CLI (deprecated)
-
-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.
-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)).
-
-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).
-
-## Change Log
-
-* `0.2.4`: Replace deprecated `localstack aws proxy` CLI command with direct Python/HTTP-based proxy startup; update README with curl-based usage instructions
-* `0.2.3`: Enhance proxy support and tests for several services (API Gateway v1/v2, CloudWatch, AppSync, Kinesis, KMS, SNS, Cognito-IDP)
-* `0.2.2`: Refactor UI to use WebAppExtension pattern
-* `0.2.1`: Restructure project to use pyproject.toml
-* `0.2.0`: Rename extension from `localstack-extension-aws-replicator` to `localstack-extension-aws-proxy`
-* `0.1.25`: Fix dynamodb proxying for read-only mode
-* `0.1.24`: Fix healthcheck probe for proxy container
-* `0.1.23`: Fix unpinned React.js dependencies preventing webui from loading
-* `0.1.22`: Fix auth-related imports that prevent the AWS proxy from starting
-* `0.1.20`: Fix logic for proxying S3 requests with `*.s3.amazonaws.com` host header
-* `0.1.19`: Print human-readable message for invalid regexes in resource configs; fix logic for proxying S3 requests with host-based addressing
-* `0.1.18`: Update environment check to use SDK Docker client and enable starting the proxy from within Docker (e.g., from the LS main container as part of an init script)
-* `0.1.17`: Add basic support for ARN-based pattern-matching for `secretsmanager` resources
-* `0.1.16`: Update imports for localstack >=3.6 compatibility
-* `0.1.15`: Move localstack dependency installation to extra since it's provided at runtime
-* `0.1.14`: Install missing dependencies into proxy container for localstack >=3.4 compatibility
-* `0.1.13`: Add compatibility with localstack >=3.4; add http2-server; migrate to localstack auth login
-* `0.1.12`: Modify aws credentials text field type to password  
-* `0.1.11`: Fix broken imports after recent upstream CloudFormation changes
-* `0.1.10`: Add `REPLICATOR_PROXY_DOCKER_FLAGS` option to pass custom flags to proxy Docker containers
-* `0.1.9`: Enhance proxy networking and add `REPLICATOR_LOCALSTACK_HOST` config option
-* `0.1.8`: Add `REPLICATOR_CLEANUP_PROXY_CONTAINERS` option to skip removing proxy containers for debugging
-* `0.1.7`: Add rolo dependency to tests
-* `0.1.6`: Adjust config to support `LOCALSTACK_AUTH_TOKEN` in addition to legacy API keys
-* `0.1.5`: Minor fix to accommodate recent upstream changes
-* `0.1.4`: Fix imports of `bootstrap.auth` modules for v3.0 compatibility
-* `0.1.3`: Adjust code imports for recent LocalStack v3.0 module changes
-* `0.1.2`: Remove deprecated ProxyListener for starting local aws-replicator proxy server
-* `0.1.1`: Add simple configuration Web UI
-* `0.1.0`: Initial version of extension
+* `PROXY_CLEANUP_CONTAINERS`: whether to remove proxy Docker containers on shutdown (default `1`). Set to `0` to keep containers for debugging.
+* `PROXY_LOCALSTACK_HOST`: the target host used by the proxy container to connect to LocalStack (auto-detected by default).
+* `PROXY_DOCKER_FLAGS`: additional flags passed when creating proxy Docker containers.
 
 ## License