Using best practices for Metabase on AWS
In the last section, we deployed Metabase with Elastic Beanstalk using the minimum number of steps to configure and secure the application. In this section, we trade speed for best practices. By following best practices, we can have more control over our application, make it more scalable and robust, and monitor its performance. If you are going to be administering Metabase within your organization, you will want to follow this guide.
The first thing we want to do is stop using our root credentials. As mentioned previously, using root credentials to build in AWS is not recommended, as it is too easy to make a critical error. The recommended path is to create individual accounts with limited permissions, and that's exactly what we will do in the next section.
