{"id":22000,"date":"2023-01-09T01:40:33","date_gmt":"2023-01-08T18:40:33","guid":{"rendered":"https:\/\/renovacloud.com\/?p=22000"},"modified":"2024-12-05T14:02:49","modified_gmt":"2024-12-05T07:02:49","slug":"26-aws-security-best-practices-to-adopt-in-production-part-1","status":"publish","type":"post","link":"https:\/\/renovacloud.com\/en\/26-aws-security-best-practices-to-adopt-in-production-part-1\/","title":{"rendered":"26 AWS Security Best Practices to Adopt In Production – Part 1"},"content":{"rendered":"

One of the most important pillars of a well-architected framework is security. Thus, it is important to follow these AWS security best practices to prevent unnecessary security situations.<\/span><\/p>\n

So, you\u2019ve got a problem to solve and turned to AWS to build and host your solution. You create your account and now you\u2019re all set up to brew some coffee and sit down at your workstation to architect, code, build, and deploy. Except, you aren\u2019t!<\/span><\/p>\n

There are many things you must set up if you want your solution to be operative, secure, reliable, performant, and cost effective. And, first things first, the best time to do that is now \u2013 right from the beginning, before you start to design and engineering.<\/span><\/p>\n

Initial AWS Setup<\/b><\/h2>\n

Never, ever, use your <\/span>root<\/span><\/i> account for everyday use. Instead, head to Identity and Access Management (IAM) and create an administrator user. Protect and lock your <\/span>root<\/span><\/i> credentials in a secure place (is your password strong enough?) and, if your <\/span>root<\/span><\/i> user has keys generated, now is the best time to delete them.<\/span><\/p>\n

You will absolutely want to activate Multi Factor Authentication (MFA) too for your root account. You must end up with a root user with MFA and no access keys. And you won\u2019t use this user unless strictly necessary.<\/span><\/p>\n

Now, about your newly created admin account, <\/span>activating MFA for it is a must<\/span><\/a>. It\u2019s actually a requirement for every user in your account if you want to have a security first mindset (and you actually want to), but especially so for power users. You will only use this account for administrative purposes.<\/span><\/p>\n

\"\"<\/p>\n

For daily use, you need to go to the IAM panel and create users, groups, and roles which can access only the resources to which you explicitly grant permissions.<\/span><\/p>\n

Now you have:<\/span><\/p>\n