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 security group: $SG_NAME
9
+
10
+
The script handles this step automatically. See `ec2-security-groups.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Adding inbound rules
13
+
14
+
The script handles this step automatically. See `ec2-security-groups.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Describing rules
17
+
18
+
The script handles this step automatically. See `ec2-security-groups.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Adding a tag
21
+
22
+
The script handles this step automatically. See `ec2-security-groups.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Listing security groups
25
+
26
+
The script handles this step automatically. See `ec2-security-groups.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 function with environment variables
9
+
10
+
The script handles this step automatically. See `lambda-env-vars.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Invoking function
13
+
14
+
The script handles this step automatically. See `lambda-env-vars.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Updating environment variables
17
+
18
+
The script handles this step automatically. See `lambda-env-vars.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Invoking with updated vars
21
+
22
+
The script handles this step automatically. See `lambda-env-vars.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: Creating function (v1)
9
+
10
+
The script handles this step automatically. See `lambda-aliases.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Creating alias pointing to v1
13
+
14
+
The script handles this step automatically. See `lambda-aliases.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Deploying v2 with canary
17
+
18
+
The script handles this step automatically. See `lambda-aliases.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Invoking via alias (multiple times)
21
+
22
+
The script handles this step automatically. See `lambda-aliases.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Shifting all traffic to v2
25
+
26
+
The script handles this step automatically. See `lambda-aliases.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 RSA key pair
9
+
10
+
The script handles this step automatically. See `ec2-keypairs.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Creating ED25519 key pair
13
+
14
+
The script handles this step automatically. See `ec2-keypairs.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Describing key pairs
17
+
18
+
The script handles this step automatically. See `ec2-keypairs.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Listing all tutorial key pairs
21
+
22
+
The script handles this step automatically. See `ec2-keypairs.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: Creating function
9
+
10
+
The script handles this step automatically. See `lambda-urls.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Creating function URL
13
+
14
+
The script handles this step automatically. See `lambda-urls.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Testing the URL
17
+
18
+
The script handles this step automatically. See `lambda-urls.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Getting URL config
21
+
22
+
The script handles this step automatically. See `lambda-urls.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.
0 commit comments