feast-dev · franciscojavierarceo · Jun 19, 2024 · Jun 12, 2024 · Jun 13, 2024 · Jun 14, 2024
diff --git a/.github/workflows/master_only.yml b/.github/workflows/master_only.yml
@@ -94,7 +94,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        component: [ feature-server-python-aws, feature-server-java, feature-transformation-server ]
+        component: [ feature-server-java, feature-transformation-server ]
     env:
       MAVEN_CACHE: gs://feast-templocation-kf-feast/.m2.2020-08-19.tar
       REGISTRY: gcr.io/kf-feast

diff --git a/Makefile b/Makefile
@@ -397,14 +397,6 @@ build-feature-server-docker:
 		-t $(REGISTRY)/feature-server:$$VERSION \
 		-f sdk/python/feast/infra/feature_servers/multicloud/Dockerfile --load .
 
-push-feature-server-python-aws-docker:
-	docker push $(REGISTRY)/feature-server-python-aws:$$VERSION
-
-build-feature-server-python-aws-docker:
-	docker buildx build --build-arg VERSION=$$VERSION \
-		-t $(REGISTRY)/feature-server-python-aws:$$VERSION \
-		-f sdk/python/feast/infra/feature_servers/aws_lambda/Dockerfile --load .
-
 push-feature-transformation-server-docker:
 	docker push $(REGISTRY)/feature-transformation-server:$(VERSION)
 

@@ -118,9 +118,7 @@
 * [Feature servers](reference/feature-servers/README.md)
   * [Python feature server](reference/feature-servers/python-feature-server.md)
   * [\[Alpha\] Go feature server](reference/feature-servers/go-feature-server.md)
-  * [\[Alpha\] AWS Lambda feature server](reference/feature-servers/alpha-aws-lambda-feature-server.md)
   * [Offline Feature Server](reference/feature-servers/offline-feature-server)
-
 * [\[Beta\] Web UI](reference/alpha-web-ui.md)
 * [\[Alpha\] On demand feature view](reference/alpha-on-demand-feature-view.md)
 * [\[Alpha\] Data quality monitoring](reference/dqm.md)

@@ -92,7 +92,7 @@ The list of supported offline and online stores can be found [here](../reference
 
 ### Does Feast support using different clouds for offline vs online stores?
 
-Yes. Using a GCP or AWS provider in `feature_store.yaml` primarily sets default offline / online stores and configures where the remote registry file can live (Using the AWS provider also allows for deployment to AWS Lambda). You can override the offline and online stores to be in different clouds if you wish.
+Yes. Using a GCP or AWS provider in `feature_store.yaml` primarily sets default offline / online stores and configures where the remote registry file can live. You can override the offline and online stores to be in different clouds if you wish.
 
 ### What is the difference between a data source and an offline store?
 

@@ -8,10 +8,7 @@ Feast users can choose to retrieve features from a feature server, as opposed to
 
 {% content-ref url="go-feature-server.md" %}
 [go-feature-server.md](go-feature-server.md)
-{% endcontent-ref %}
-
-{% content-ref url="alpha-aws-lambda-feature-server.md" %}
-[alpha-aws-lambda-feature-server.md](alpha-aws-lambda-feature-server.md)
+=======
 {% endcontent-ref %}
 
 {% content-ref url="offline-feature-server.md" %}

@@ -12,8 +12,6 @@ There is a CLI command that starts the server: `feast serve`. By default, Feast
 
 One can deploy a feature server by building a docker image that bundles in the project's `feature_store.yaml`. See this [helm chart](https://github.com/feast-dev/feast/blob/master/infra/charts/feast-feature-server) for an example on how to run Feast on Kubernetes.
 
-A [remote feature server](alpha-aws-lambda-feature-server.md) on AWS Lambda is also available.
-
 ## Example
 
 ### Initializing a feature server

@@ -17,9 +17,6 @@
 # Maximum interval(secs) to wait between retries for retry function
 MAX_WAIT_INTERVAL: str = "60"
 
-AWS_LAMBDA_FEATURE_SERVER_IMAGE = "feastdev/feature-server-python-aws"
-AWS_LAMBDA_FEATURE_SERVER_REPOSITORY = "feast-python-server"
-
 # feature_store.yaml environment variable name for remote feature server
 FEATURE_STORE_YAML_ENV_NAME: str = "FEATURE_STORE_YAML_BASE64"
 
@@ -44,8 +41,5 @@
 # Default offline server port
 DEFAULT_OFFLINE_SERVER_PORT = 8815
 
-# Environment variable for feature server docker image tag
-DOCKER_IMAGE_TAG_ENV_NAME: str = "FEAST_SERVER_DOCKER_IMAGE_TAG"
-
 # Default feature server registry ttl (seconds)
 DEFAULT_FEATURE_SERVER_REGISTRY_TTL = 5
@@ -350,32 +350,6 @@ def __init__(self, feature_view_name: str):
         )
 
 
-class RepoConfigPathDoesNotExist(Exception):
-    def __init__(self):
-        super().__init__("The repo_path attribute does not exist for the repo_config.")
-
-
-class AwsLambdaDoesNotExist(Exception):
-    def __init__(self, resource_name: str):
-        super().__init__(
-            f"The AWS Lambda function {resource_name} should have been created properly, but does not exist."
-        )
-
-
-class AwsAPIGatewayDoesNotExist(Exception):
-    def __init__(self, resource_name: str):
-        super().__init__(
-            f"The AWS API Gateway {resource_name} should have been created properly, but does not exist."
-        )
-
-
-class IncompatibleRegistryStoreClass(Exception):
-    def __init__(self, actual_class: str, expected_class: str):
-        super().__init__(
-            f"The registry store class was expected to be {expected_class}, but was instead {actual_class}."
-        )
-
-
 class FeastInvalidInfraObjectType(Exception):
     def __init__(self):
         super().__init__("Could not identify the type of the InfraObject.")