You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating web ACL: $ACL_NAME
9
+
10
+
The script handles this step automatically. See `aws-waf-gs.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Describing web ACL
13
+
14
+
The script handles this step automatically. See `aws-waf-gs.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Listing available managed rule groups
17
+
18
+
The script handles this step automatically. See `aws-waf-gs.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Listing web ACLs
21
+
22
+
The script handles this step automatically. See `aws-waf-gs.sh` for the exact CLI commands.
23
+
24
+
## Cleanup
25
+
26
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Enabling Detective
9
+
10
+
The script handles this step automatically. See `amazon-detective-gs.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Listing graphs
13
+
14
+
The script handles this step automatically. See `amazon-detective-gs.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Listing members
17
+
18
+
The script handles this step automatically. See `amazon-detective-gs.sh` for the exact CLI commands.
19
+
20
+
## Cleanup
21
+
22
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating policy store
9
+
10
+
The script handles this step automatically. See `amazon-verifiedpermissions-gs.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Creating a static policy
13
+
14
+
The script handles this step automatically. See `amazon-verifiedpermissions-gs.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Testing authorization
17
+
18
+
The script handles this step automatically. See `amazon-verifiedpermissions-gs.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Testing denied action
21
+
22
+
The script handles this step automatically. See `amazon-verifiedpermissions-gs.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Listing policies
25
+
26
+
The script handles this step automatically. See `amazon-verifiedpermissions-gs.sh` for the exact CLI commands.
27
+
28
+
## Cleanup
29
+
30
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
1. AWS CLI installed and configured (`aws configure`)
6
+
2. Appropriate IAM permissions for the AWS services used
7
+
8
+
## Step 1: Creating a custom policy
9
+
10
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Getting policy details
13
+
14
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Getting policy version (the actual document)
17
+
18
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Creating a role and attaching the policy
21
+
22
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Listing attached policies
25
+
26
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
27
+
28
+
## Step 6: Simulating policy
29
+
30
+
The script handles this step automatically. See `iam-policies.sh` for the exact CLI commands.
31
+
32
+
## Cleanup
33
+
34
+
The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
0 commit comments