fix: or-2583 use dedicated user for lambda deploy

Informatievlaanderen · Jan 22, 2025 · 47a660e · 47a660e
1 parent ef94d94
commit 47a660e
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
@@ -540,8 +540,8 @@ jobs:
       - name: Configure AWS credentials
         uses: aws-actions/configure-aws-credentials@v4
         with:
-          aws-access-key-id: ${{ secrets.VBR_AWS_BUILD_USER_ACCESS_KEY_ID_IK4 }}
-          aws-secret-access-key: ${{ secrets.VBR_AWS_BUILD_USER_SECRET_ACCESS_KEY_IK4 }}
+          aws-access-key-id: ${{ secrets.VBR_AWS_DEPLOY_LAMBDA_USER_ACCESS_KEY_ID_IK4 }}
+          aws-secret-access-key: ${{ secrets.VBR_AWS_DEPLOY_LAMBDA_USER_SECRET_ACCESS_KEY_IK4 }}
           aws-region: ${{ secrets.VBR_AWS_REGION }}
 
       - name: Show AWS CLI version
@@ -568,8 +568,8 @@ jobs:
           version: ${{ needs.release.outputs.version }}
           status-url: $STATUS_URL
           deploy-url: $BUILD_URL
-          access-key: ${{ secrets.VBR_AWS_BUILD_USER_ACCESS_KEY_ID_IK4 }}
-          secret-key: ${{ secrets.VBR_AWS_BUILD_USER_SECRET_ACCESS_KEY_IK4 }}
+          access-key: ${{ secrets.VBR_AWS_DEPLOY_LAMBDA_USER_ACCESS_KEY_ID_IK4 }}
+          secret-key: ${{ secrets.VBR_AWS_DEPLOY_LAMBDA_USER_SECRET_ACCESS_KEY_IK4 }}
           deploy-target: 'lambda'
           domain: 'verenigingsregister'
           project: 'verenigingsregister'