- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I don't know what basics you have in place already, but first up is use only IAM Users - put MFA on your root user and only use it again in situations where there's no choice. Also add MFA to your IAM Users.
It's up to you what permissions you give your IAM Users, it can just be "s3:*" if you want.
That's just the beginning though. It you really want to put things "in proper order and locked down tight", have a look at https://aws.amazon.com/architecture/security-identity-compliance.
If you do not intend on using Amazon AppStream 2.0, stop the Fleets that were created immediately as well as any image builders you may have running as that is creating cost.
https://docs.aws.amazon.com/appstream2/latest/developerguide/managing-stacks-fleets.html
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- Come posso risolvere gli errori relativi alle autorizzazioni sulle risorse AWS in Amazon QuickSight?AWS UFFICIALEAggiornata un anno fa