Installation of Docker Engine and other components takes a few minutes after EC2 instance launch. Please proceed to access it only after 5 minutes of launch.
Swap memory has been created with a 1 GB swap file located at /var/myswap.
To know more about managing swap visit this page.
Debian user admin that you use for SSH access has also been added to the docker user group to enable running Docker containers directly.
System disk size
EBS volume (system storage disk) is 15 GB to accomodate Docker containers and base OS.
Visit this page to know how to modify EBS volume size should you wish to do so.
Remember to extend the Linux file system after increasing EBS volume size.
Debian 10 Server Administration
To administer Debian 10 Server directly using SSH, refer to this guide.
Working with Docker
To setup your Docker development environment, or start working with Docker images, refer to this guide.
We have enabled the admin user with docker group membership and sudo privileges.
Check if Docker Engine is setup correctly
Before you begin working with Docker images you should check if the Docker Engine is setup correctly.
You can do this by accessing your EC2 instance via SSH and running the following command:
docker run hello-world
To find more Docker apps for your Docker Engine server, visit Docker Hub. Just make sure that your EC2 instance meets the minimum requirements of vCPU, RAM, and EBS storage before you add more apps. Also check if the app you intend to install will use a port that is already in use or that has not yet been opened in the EC2's security group settings.
Setup docker-compose (if needed)
To setup docker-compose run the following commands.
sudo curl -L https://github.com/docker/compose/releases/download/1.22.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
You can verify setup by checking the docker-compose version.
Suggested Next Steps
Open Additional Ports for Inbound Traffic
While outbound traffic is open on all ports, we have only enabled inbound SSH access using port 22 for your EC2 instance.
If you need to open any other inbound ports based on your specific deployment needs, you can follow this guide.
Setup DNS records for Domain or Sub-domain
If you intend to use one or more custom domains or sub-domains with your EC2 instance, you should setup an 'A' record in your domain DNS settings pointing to your instance's public IP.
For example, if the custom domain name that you want pointing to your server is paymypage.com then your DNS records should be added as follows:
To get the public IP for your EC2 instance launched using our service, click here.
If you need to register a custom domain name for the purpose, click here.
Next Steps for Docker Apps (only if they were included in your EC2 launch)
We have used t2.small (1 vCPU, 2GB RAM) EC2 instance type for this setup.
Minimum recommended RAM is 2GB for one monitored database node. Memory usage does not grow in proportion to number of nodes. For example, 16GB is adequate for 20 nodes. To know how to upgrade the EC2 instance type, click here.
PMM needs approximately 1GB of disk storage for each monitored database node with data retention set to one week. By default, data retention is 30 days. To reduce the size of the VictoriaMetrics database, you can consider disabling table statistics.
- To access your PMM Server Dashboard, visit http://<Public DNS of your server>/
At launch, the Web UI Username is admin and Password is admin. You will be asked to change this password when you sign-in for the first time.
- To access your PMM Server MetricsMonitor, use http://<Public DNS of your server>/graph/
- To access your PMM Server API, use http://<Public DNS of your server>/swagger/
You can get the Public DNS for your server from your EC2 launch history.
We have already opened port 80 for HTTP access and port 443 for HTTPS access in addition to the port 22 for SSH access.
See also: Enabling HTTPS Connections to Percona Monitoring and Management Using Custom Certificates
If you need SSL certificates for your server, click here.
You can get support from the PMM user community at these forums.
Docker Compose has already been installed as part of the Twake server installation. Do not attempt to install it again.
We have used the t2.micro EC2 instance type (free tier eligible) to setup Twake app server in your AWS account. This configuration should be able to support upto 5 users. You can upgrade the instance type to accommodate more users by following these instructions.
Once the background installation is complete after the launch of your EC2, you can setup Twake users in your web browser by visiting port 8000 with the public Hostname/DNS for your EC2 instance. You can look up the public hostname from your EC2 launch history.
If you wish to use a custom domain/sub-domain with this app, we recommend you switch to using a custom domain/sub-domain (see above) before you proceed.
Once you can access the Twake app in your web browser, the Twake app server is installed, and you can follow the official Twake guide for server configuration from this step.