Recommendations and best practices

Here are a few key takeaways from this chapter:

  • First and foremost, create and use separate IAM users for working with EC2. DO NOT USE your standard root account credentials!
  • Use IAM roles if you need to delegate access to your EC2 account to other people for some temporary period of time. Do not share your user passwords and keys with anyone.
  • Use a standard and frequently deployed set of AMIs as they are tried and tested by AWS thoroughly.
  • Make sure that you understand the difference between instance store-backed and EBS-backed AMIs. Use the instance store with caution and remember that you are responsible for your data, so take adequate backups of it.
  • Don't create too many firewall rules on a single security group. Make sure that you apply the least permissive rules for your security groups.
  • Stop your instances when not in use. This will help you save up on costs as well.
  • Use tags to identify your EC2 instances. Tagging your resources is a good practice and should be followed at all times.
  • Save your key pairs in a safe and accessible location. Use passphrases as an added layer of security if you deem it necessary.
  • Monitor your instances at all times. We will be looking at instance monitoring in depth in the coming chapters; however, you don't have to wait until then! Use the EC2 Status and Health Check tabs whenever required.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset