https://medium.com/nerd-for-tech/aws-certified-solutions-architect-associate-saa-c02-exam-notes-cbafca04bc07

- EC2 user data, can be run on every reboot using MIME configuration.

- Add an EC2 instance type section After user data.

- One example of how to ready insance type would be useful.

- use cases for c, r, m i, x series will be useful (question comes on SAP Hana where we can use r/c series)

- Spot instances: Suitable for short workloads but the instances are really cheap. This line is not apt. It should be:

Spot instances: Suitable for workloads that can tolerate interruptions. Like idempotent workloads.

- Dedicated host - Add use case for dedicated host (workloads with BYOL)

- States for EC2 instances:

Stop is not an state, its an action. Stopping or stopped. Same for terminate.

- Extras: ENI: It can have 2 IP. This statement is wrong. ENIs can have upto 50 IPs. Depeneds upon instance type.

https://medium.com/nerd-for-tech/part-2-ec2-instance-storage-databases-aws-saa-notes-75f04c9dee80

EC2 storage should talk about. Instance store, EBS, EFS thats it. If at all you can metion about mounting S3 using s3fs.

No need to include Load balancer & Route53 in this. It should be in networking.

I would have written separate article for RDS. Clubbing it with EC2 is not right.

https://medium.com/mlearning-ai/part-3-s3-cloudfront-data-migration-services-ead6106b0ac4

As mentioned you need to structure the article logically. There is no coherence between s3 & DMS.

DMS & RDS can be put together.