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
- Cleanup: ~5 minutes (instance and cluster deletion)
53
52
54
53
## Cost
55
54
56
-
DocumentDB instances incur charges while running. The db.t3.medium instance costs approximately $0.08/hour. Cleanup deletes all resources to stop charges.
55
+
DocumentDB instances are billed per hour. A db.t3.medium instance costs approximately $0.076/hour. Clean up promptly after the tutorial.
57
56
58
57
## Related docs
59
58
60
-
-[Get started with Amazon DocumentDB](https://docs.aws.amazon.com/documentdb/latest/developerguide/get-started-guide.html)
59
+
-[Getting started with Amazon DocumentDB](https://docs.aws.amazon.com/documentdb/latest/developerguide/get-started-guide.html)
| Script test result | EXIT 0, 825s, 10 steps, clean teardown |
72
+
| Issues encountered | Region not configured (added pre-check); `openssl rand` password contained DocumentDB-illegal characters (switched to safe character set); subnet IDs needed space separation not comma; original used `set -e` (replaced with ERR trap for clean error reporting) |
# AWS IoT Device Defender getting started tutorial
1
+
# IoT Device Defender: Getting started
2
2
3
-
This tutorial provides a comprehensive introduction to AWS IoT Device Defender using the AWS CLI. You'll learn how to set up device security monitoring, create security profiles, configure anomaly detection, and implement security best practices for your IoT device fleet.
3
+
Set up AWS IoT Device Defender audit, run an on-demand audit, and review the findings.
4
4
5
-
You can either run the provided shell script to automatically set up your IoT Device Defender configuration and basic security monitoring, or follow the step-by-step instructions in the tutorial markdown file to understand each component and customize the security setup for your specific IoT device management requirements.
The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.
16
+
## What it does
17
+
18
+
1. Creates an IAM role for IoT Device Defender
19
+
2. Configures audit settings with the role
20
+
3. Starts an on-demand audit
21
+
4. Waits for the audit to complete
22
+
5. Retrieves and displays audit findings
23
+
6. Cleans up audit configuration, role, and policies
24
+
25
+
## Running
26
+
27
+
```bash
28
+
bash aws-iot-device-defender-gs.sh
29
+
```
30
+
31
+
To auto-run with cleanup:
32
+
33
+
```bash
34
+
echo'y'| bash aws-iot-device-defender-gs.sh
35
+
```
36
+
37
+
## Resources created
38
+
39
+
- IAM role (with IoT Device Defender audit permissions)
40
+
- IoT audit configuration
41
+
- On-demand audit task
42
+
43
+
## Estimated time
44
+
45
+
- Run: ~2 minutes (audit takes ~60 seconds)
46
+
- Cleanup: ~10 seconds
47
+
48
+
## Cost
49
+
50
+
No additional charges for IoT Device Defender audit. Standard IoT pricing applies.
51
+
52
+
## Related docs
53
+
54
+
-[Getting started with AWS IoT Device Defender](https://docs.aws.amazon.com/iot/latest/developerguide/device-defender-tutorial.html)
| Script test result | EXIT 0, ~120s, all steps, clean teardown |
67
+
| Issues encountered | PassRole with `*` in Resource (split into two IAM statements); end-time bug used 'tomorrow' instead of 'now'; audit config not cleaned up on exit (added reset to cleanup); SNS topic ARN referenced but not created |
This tutorial guides you through setting up Amazon Elastic Container Service (Amazon ECS) Service Connect using the AWS Command Line Interface (AWS CLI). You'll learn how to create an ECS cluster with Service Connect enabled, deploy a containerized application, and configure service discovery for inter-service communication.
3
+
Deploy two ECS Fargate services that communicate using Amazon ECS Service Connect.
4
4
5
-
You can either run the automated shell script (`amazon-ecs-service-connect.sh`) to quickly set up the entire environment, or follow the step-by-step instructions in the tutorial (`amazon-ecs-service-connect.md`) to understand each component in detail. Both approaches will help you understand how to implement service-to-service communication in Amazon ECS using Service Connect.
-[Creating a service with Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-connect.html)
62
+
-[Amazon ECS task execution IAM role](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html)
63
+
64
+
---
65
+
66
+
## Appendix: Generation details
18
67
19
-
The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.
68
+
| Field | Value |
69
+
|-------|-------|
70
+
| Generation date | 2026-04-14 (README regenerated with appendix) |
0 commit comments