(powerDNS)[https://www.powerdns.com] it’s a great alternative for large and complex BIND setup. Light footprint, and quick setup made that server as my obvious choice for slave server for primary BIND server. So let’s config begins:
Biggest advantage with AWS – EC2 service, is that you are paying for each minute of usage. So – why run instances 24/7 if you need them only for 12 hours par day ? You can just start and stop whenever you need them. Obviously we don’t want to forgot to shutdown our instance, or start when we need it. Here is a simple recipe how to automate whole task
Caddy is a another alternative to Apache or nginx . For me the biggest advantage is that it’s only one binary file to work with. It’s easy to run, setup and just “works”. It’s super modern – handles HTTP2 and automatic HTTPS encryption using let’s encrypt certificates. Obviously it has plenty of other features but we focus only on speed of deployment.
PHP 7.0 it’s already a while on the market. Let’s install it on EC2 instance. Here you can find a quick recipe:
Recently on CyberCity nice article appeared about using middle server to connect to our destination servers. Most of servers have firewalls which allow connect only from given pool of IP addresses. So tunnelling is very useful as long we are using it in smart way.
