EDEN: This note was created after I finished Stephane Maarek’s SysOps course. I did the first section of Neal Davis’s SysOps course and I’ve found some important-to-remember primer details.
Note that some of the information here may been mentioned already in the succeeding note.
These are general information which will be reiterated again on the other notes, but I find as core details for any Solutions Architect or simply anyone in an AWS SysOps role.
[<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/09eaf06c-4ed8-4b9c-8b45-96831b9b7bee/notes-aws-sysops-masterImages02-preview.png>](<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/09eaf06c-4ed8-4b9c-8b45-96831b9b7bee/notes-aws-sysops-masterImages02-preview.png>)
[<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/e9e7f94a-5792-48c1-95ab-6e02a162cf54/notes-aws-sysops-masterImages02-preview.png>](<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/e9e7f94a-5792-48c1-95ab-6e02a162cf54/notes-aws-sysops-masterImages02-preview.png>)
[<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/895b3db5-adb5-4785-88f9-01cae5ec8431/notes-aws-sysops-masterImages02-preview.png>](<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/895b3db5-adb5-4785-88f9-01cae5ec8431/notes-aws-sysops-masterImages02-preview.png>)
[<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/827e7b93-5527-4902-83df-651c613bd3c4/notes-aws-sysops-masterImages02-preview.png>](<https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/827e7b93-5527-4902-83df-651c613bd3c4/notes-aws-sysops-masterImages02-preview.png>)
https://prod-files-secure.s3.us-west-2.amazonaws.com/514dc457-5e07-4181-8560-a8825ab015d8/4d26b979-ee38-4902-ae5b-d7358c41a19e/notes-aws-sysops-masterImages02-preview.png
AWS is a multi-tenant service - which means that for the most part, you’ll be running your resources on hardware that is shared across multiple customers.
There are options where you can have dedicated hardware or connection and you can find more details on that in the other notes, but the majority of AWS services are configured in a multi-tenant setup.
These AWS services can either be Public or Private.
These are services with public endpoints. - have a DNS or IP address whihch you can connect to - as example, S3 buckets have a URL which you can access
These are services that can have a public IP address but exist within a VPC. - all resources have private IP address and is in your VPC - as an example, EC2 instances have public IP addresses which you can SSH into. - from the VPC, your resources can access outside resources through:
- **Internet Gateway**
Can be used to go to the public internet and connect to AWS public services
- **VPC Endpoint**
Can be used to access AWS public resources throguh a private connection