Study Guides/AWS Cybersecurity Notes/Securing EC2 Instances: Difference between revisions
From Cramsession
Jump to navigationJump to search
✍️ Verified Author: Mflavell • Click to view professional profile & credentials
(Created page with "= Securing EC3 Instances = == Key Pairs == Key pairs allows you to connect EC2 Instances. Key pairs can be created two ways: :* During EC2 Deployment :* Witihn the EC2 management console === Deleting Keys === Several reasons for deletion: :* Periodic cycling :* Employee with a key leaving :* Security event resulting in loss of keys or access via keys. If a key id deleted you can no longer use it to access associated EC2 instances. :: This deletes the AWS c...") |
No edit summary |
||
| Line 31: | Line 31: | ||
:: Think of this as deleting the key from AWS registry, it does not delete from the instance!!. | :: Think of this as deleting the key from AWS registry, it does not delete from the instance!!. | ||
You can recover from a lost pem file [Recovery_from_lost_EC2_PEM_file] | |||
Revision as of 00:41, 16 June 2026
Securing EC3 Instances
Key Pairs
Key pairs allows you to connect EC2 Instances.
Key pairs can be created two ways:
- During EC2 Deployment
- Witihn the EC2 management console
Deleting Keys
Several reasons for deletion:
- Periodic cycling
- Employee with a key leaving
- Security event resulting in loss of keys or access via keys.
If a key id deleted you can no longer use it to access associated EC2 instances.
- This deletes the AWS copy of the key but does not delete the public key for the EC2 instances.
- For this reason if you have the private key you can still connect.
- Think of this as deleting the key from AWS registry, it does not delete from the instance!!.
You can recover from a lost pem file [Recovery_from_lost_EC2_PEM_file]
