Update aws log forwarder

.eslintrc.json

@@ -1,4 +1,5 @@
 {
+  "root": true,
   "env": {
     "browser": false,
     "es2021": true,

.github/workflows/release.yaml

@@ -0,0 +1,25 @@
+name: release
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - name: Package
+        run: |
+          npm ci
+          zip -r aws-log-forwarder.zip  . -i "*.js" "*.json" "node_modules" VERSION LICENSE
+      - name: Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: |
+            aws-log-forwarder.zip

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [0.2.0] - 2024-04-03
+
+### Added
+
+- Publish to github releases
+
 ## [0.1.0] - 2023-08-28
 
 ### Added

README.md

@@ -18,7 +18,7 @@ Lambda function to stream ec2 loadbalancer access logs and cloudwatch logs to im
 INSPECTOR_MODE: "log_stream_server"
 INSPECTOR_LOGSTREAM_LISTEN_ADDR: ":<port>"
 INSPECTOR_LOGSTREAM_ID: "<log_binding_logstream_ID>" # from step 1
-INSPECTOR_API_ACCESS_TOKEN: "<access_token>" # setup here https://console.impartsecurity.net/orgs/_/settings/tokens#create. Click `New inspector access token`, click `Inspector access` to set the scopes.
+INSPECTOR_API_ACCESS_TOKEN: "<access_token>" # setup here https://console.impartsecurity.net/orgs/_/access-tokens#create. Click `New inspector access token`, click `Inspector access` to set the scopes.
 ```
 
 3. Run the lambda function subscribed either to cloud watch events or elb s3 events.

VERSION

@@ -1 +1 @@
-0.1.0
+0.2.0

package.json

@@ -10,10 +10,10 @@
     "lint": "eslint . --cache --ext .js --max-warnings=0"
   },
   "dependencies": {
-    "aws-sdk": "^2.1467.0"
+    "aws-sdk": "^2.1589.0"
   },
   "devDependencies": {
-    "eslint": "^8.50.0",
-    "prettier": "^3.0.2"
+    "eslint": "^8.57.0",
+    "prettier": "^3.2.5"
   }
 }