Skip to content
This repository was archived by the owner on Jan 24, 2025. It is now read-only.

Commit d5ed776

Browse files
authored
Update README.md
1 parent d305ed8 commit d5ed776

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ jobs:
5151
# modify this block to scan your intended EC2 instances
5252
- name: Inspector Scan
5353
id: inspector
54-
uses: austinsonger/[email protected]
54+
uses: action.yml
5555
with:
5656
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
5757
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
@@ -120,7 +120,7 @@ The below example shows how to enable action outputs in various locations and fo
120120
```yaml
121121
- name: Scan EC2 instances
122122
id: inspector
123-
uses: austinsonger/EC2-Vulnerability-Scan-GitHub-Action-for-Amazon-Inspector
123+
uses: action.yml
124124
with:
125125
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
126126
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
@@ -161,7 +161,7 @@ Vulnerability thresholds can be used to support custom logic, such as failing th
161161
```yaml
162162
- name: Invoke Amazon Inspector Scan
163163
id: inspector
164-
uses: austinsonger/EC2-Vulnerability-Scan-GitHub-Action-for-Amazon-Inspector
164+
uses: action.yml
165165
with:
166166
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
167167
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

0 commit comments

Comments
 (0)