Contains solutions to some of the problems I encountered while deploying apps to Amazon machine instances

contains a docker compose file that helps with deployment of the elk stack. 🔴Does not have xpack security 🔴. Use it for quickly setting up the elk stack on your system. It also has an image for portainer for you to easily manage your volumes and images for the elk stack.

- "5601:5601" -> elastic
- "9200:9200" -> kibana
- "5044:5044" -> logstash

- 9000:9000  -> Portainer
- 8000:8000

Navigate to the folder containing the compose file. Then run the following command

docker-compose up -d --build

In case you only want to run a single image, lets say you wanted to rebuild portainer

docker-compose up -d --build --no-deps portainer

Please make sure to update tests as appropriate.

ssh-config directory in this project contains a guide to include your aws-ec2 pem files in your ssh-configs, so that you don't have to manually enter entire configuration to log in to your remote system. At the end of this you will be able to ssh using a single line of code, which can be optimised to your taste. The ssh-config file contains comments to make the installation simpler.

• Host is an alias you give to your connection
• Hostname can be an ip or domain name for your ec2-instance
• Identity is the location of .pem file
• User is the default user for remote instance [mine is amazon linux, the default user for linux ami is ec2-user, yours may be called root]

    cd ~/.ssh
    nano ssh-config
    
    Host test.elasticsearch.marsplay
    HostName test.marsplay.co
    IdentityFile ~/.ssh/EC2_SSH_KEYS/Test_Elastic.pem
    User ec2-user

Be sure to include the correct path for your .pem file, mine happened to be a folder named EC2_SSH_KEYS inside the .ssh directory . Run the following command

• ssh test.elastic.marsplay you will be connected to your remote system

You may also like the vscode extension that allows you to access your instances via the connections you just mentioned in your ssh-config file. I'll leave it up to you to figure out 😉

The systemd directory contains a systemd configuration file that restarts the docker-compose stack on a system reboot automatically

Dont forget to enable the docker daemon on your system first

sudo systemctl enable docker

This will create a symlink for the docker daemon into the bin directory, so that docker starts on system reboot

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

MIT