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
The script handles this step automatically. See `s3-encryption.sh` for the exact CLI commands.
11
+
12
+
## Cleanup
13
+
14
+
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 bucket
9
+
10
+
The script handles this step automatically. See `s3-access-points.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Creating access point: $AP_NAME
13
+
14
+
The script handles this step automatically. See `s3-access-points.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Getting access point details
17
+
18
+
The script handles this step automatically. See `s3-access-points.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Listing access points
21
+
22
+
The script handles this step automatically. See `s3-access-points.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 bucket with Object Lock
9
+
10
+
The script handles this step automatically. See `s3-object-lock.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Setting default retention (1 day governance mode)
13
+
14
+
The script handles this step automatically. See `s3-object-lock.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Getting lock configuration
17
+
18
+
The script handles this step automatically. See `s3-object-lock.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Uploading a locked object
21
+
22
+
The script handles this step automatically. See `s3-object-lock.sh` for the exact CLI commands.
23
+
24
+
## Step 5: Verifying lock
25
+
26
+
The script handles this step automatically. See `s3-object-lock.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 bucket
9
+
10
+
The script handles this step automatically. See `s3-transfer-acceleration.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Enabling Transfer Acceleration
13
+
14
+
The script handles this step automatically. See `s3-transfer-acceleration.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Getting acceleration status
17
+
18
+
The script handles this step automatically. See `s3-transfer-acceleration.sh` for the exact CLI commands.
19
+
20
+
## Step 4: Accelerated endpoint
21
+
22
+
The script handles this step automatically. See `s3-transfer-acceleration.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 source and destination buckets
9
+
10
+
The script handles this step automatically. See `s3-inventory.sh` for the exact CLI commands.
11
+
12
+
## Step 2: Configuring inventory
13
+
14
+
The script handles this step automatically. See `s3-inventory.sh` for the exact CLI commands.
15
+
16
+
## Step 3: Getting inventory configuration
17
+
18
+
The script handles this step automatically. See `s3-inventory.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.
0 commit comments