basic lambda

Author: nhsdevws

.github/dependabot.yml

@@ -58,6 +58,7 @@ updates:
       - "/mesh_processor"
       - "/recordprocessor"
       - "/redis_sync"
+      - "/id_sync"
     schedule:
       interval: "daily"
     open-pull-requests-limit: 1

.github/workflows/sonarcloud.yml

@@ -124,6 +124,18 @@ jobs:
             poetry run coverage run -m unittest discover || echo "redis_sync tests failed" >> ../failed_tests.txt
             poetry run coverage xml -o ../redis_sync-coverage.xml
 
+      - name: Run unittest with id_sync
+        working-directory: id_sync
+        id: id_sync
+        env:
+          PYTHONPATH: ${{ github.workspace }}/id_sync/src:${{ github.workspace }}/id_sync/tests
+        continue-on-error: true
+        run: |
+            poetry env use 3.11
+            poetry install
+            poetry run coverage run -m unittest discover || echo "id_sync tests failed" >> ../failed_tests.txt
+            poetry run coverage xml -o ../id_sync-coverage.xml
+
       - name: Run Test Failure Summary
         id: check_failure
         run: |

Makefile

@@ -38,7 +38,7 @@ build-proxy:
 	scripts/build_proxy.sh
 
 #Files to loop over in release
-_dist_include="pytest.ini poetry.lock poetry.toml pyproject.toml Makefile build/. e2e e2e_batch specification sandbox terraform scripts backend delta_backend ack_backend filenameprocessor recordprocessor mesh_processor redis_sync"
+_dist_include="pytest.ini poetry.lock poetry.toml pyproject.toml Makefile build/. e2e e2e_batch specification sandbox terraform scripts backend delta_backend ack_backend filenameprocessor recordprocessor mesh_processor redis_sync id_sync"
 
 
 #Create /dist/ sub-directory and copy files into directory

README.md

@@ -24,6 +24,7 @@ See https://nhsd-confluence.digital.nhs.uk/display/APM/Glossary.
 | `mesh_processor`    | **Imms Batch** – MESH-specific batch processing functionality. |
 | `recordprocessor`   | **Imms Batch** – Handles batch record processing. |
 | `redis_sync`        | **Imms Redis** – Handles sync s3 to REDIS. |
+| `id_sync`        | **Imms Redis** – Handles sync SQS to IEDS. |
 ---
 
 ### Pipelines

id_sync/Dockerfile

@@ -0,0 +1,25 @@
+FROM public.ecr.aws/lambda/python:3.11 AS base
+
+# Create non-root user
+RUN mkdir -p /home/appuser && \
+    echo 'appuser:x:1001:1001::/home/appuser:/sbin/nologin' >> /etc/passwd && \
+    echo 'appuser:x:1001:' >> /etc/group && \
+    chown -R 1001:1001 /home/appuser && pip install "poetry~=1.5.0"
+
+# Install Poetry as root
+COPY poetry.lock pyproject.toml README.md ./
+RUN poetry config virtualenvs.create false && poetry install --no-interaction --no-ansi --no-root --only main
+# -----------------------------
+FROM base AS test
+COPY src src
+COPY tests tests
+RUN poetry install --no-interaction --no-ansi --no-root && \
+    pytest --disable-warnings tests
+
+# -----------------------------
+FROM base AS build
+COPY src .
+RUN chmod 644 $(find . -type f) && chmod 755 $(find . -type d)
+# Build as non-root user
+USER 1001:1001
+CMD ["id_sync.handler"]

id_sync/Makefile

@@ -0,0 +1,14 @@
+
+test:
+	@PYTHONPATH=src:tests python -m unittest
+
+coverage-run:
+	coverage run -m unittest discover -v
+
+coverage-report:
+	coverage report -m
+
+coverage-html:
+	coverage html
+
+.PHONY: build package

id_sync/README.md

@@ -0,0 +1,44 @@
+# Redis Sync Lambda
+
+## Overview
+
+**Redis Sync** is an AWS Lambda function designed to monitor a configuration S3 bucket and synchronize its contents with an ElastiCache Redis instance. Whenever a new configuration file is uploaded or updated in the S3 bucket, the Lambda function processes the file, applies any required transformations, and uploads the result to the Redis cache.
+
+## Features
+
+- **S3 Event Driven:** Automatically triggered by S3 events (e.g., file uploads or updates) in the config bucket.
+- **Transformation Support:** Applies custom transformation logic to configuration files before caching.
+- **Redis Integration:** Uploads processed configuration data to ElastiCache Redis for fast, centralized access.
+- **Logging:** Provides detailed logging for monitoring and troubleshooting.
+
+## How It Works
+
+1. **S3 Event Trigger:** The Lambda is triggered by S3 events on the config bucket.
+2. **File Processing:** The Lambda reads the new or updated file from S3.
+3. **Transformation:** If required, the file content is transformed to the appropriate format.
+4. **Redis Upload:** The transformed data is uploaded to the Redis cache under a key corresponding to the file.
+5. **Monitoring:** Logs are generated for each step, aiding in monitoring and debugging.
+
+## Configuration
+
+- **Environment Variables:**
+  - `CONFIG_BUCKET_NAME`: Name of the S3 bucket to monitor.
+  - `AWS_REGION`: AWS region for S3 and Redis.
+  - `REDIS_HOST`: Redis endpoint.
+  - `REDIS_PORT`: Redis port (default: 6379).
+
+## Usage
+
+1. **Deploy the Lambda** using your preferred IaC tool (e.g., Terraform, AWS SAM).
+2. **Configure S3 event notifications** to trigger the Lambda on object creation or update.
+3. **Ensure Redis and S3 permissions** are set for the Lambda execution role.
+
+## Development
+
+- Code is located in the `src/` directory.
+- Unit tests are in the `tests/` directory.
+- Use the provided Makefile and Dockerfile for building, testing, and packaging.
+
+## License
+
+This project is maintained by NHS. See [LICENSE](../LICENSE) for details.