1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
2
First of all, you must remove the access key and secret key from here immediately as you see and terminate the instance and disable this access and secret key. These keys have now been exposed and your AWS account/resources are at risk. Make sure you have blocked access to all resources and see if there is no unusual activity.
Follow this guide at earliest What to do, if I exposed long lived credentials accidentally
Check your subnet's route table and make sure it has a route to the Internet Gateway? Can you check if your subnet NACLs are fully allowing ephemeral ports?
Your subnet route table should have an entry like below:
"Destination" 0.0.0.0/0 "Target" igw-XXXXXXXXXX
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Follow this guide at earliest What to do, if I exposed long lived credentials accidentally
Yes, the subnet route table shows these two routes:
"Destination" 0.0.0.0/0 "Target" igw-XXXXXXXXXX "Status" Active "Propagated" No
"Destination" 172.XX.X.X/16 "Target" local "Status" Active "Propagated" No
I had initially inserted XXXX at the end of the Access Key and Secret Key, but changed it to all X's on your advice. Thanks.