Tag Archives: AWS VPC

dnsmasq: AWS – “Temporary failure in name resolution”, logs, debug and dnsmasq cache size

28 October 2019
 

 We are using AWS VPC DNS and sometimes facing with errors like “php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution“. The only advice from AWS tech. support was to configure a local dnsmasq service to act as a local DNS cache, but I did this already year ago and this issue happens once in 1-2-3… Read More »

Kubernetes: part 3 – AWS EKS overview and manual EKS cluster set up

15 August 2019
 

 Let’s proceed with our Kubernetes journey. Previous parts: Kubernetes: part 1 – architecture and main components overview Kubernetes: part 2 – a cluster set up on AWS with AWS cloud-provider and AWS LoadBalancer In this part we will start working with AWS Elastic Kuberneters Service (EKS) – its short overview, then will create Kubernetes Control… Read More »

AWS: VPC peering DNS resolution and DNS settings for OpenVPN Access Server

17 May 2019
 

 We have a VPC with OpenVPN Access Server running. This VPC is connected with other VPCs in our AWS account. The issue is that currently when a user is connected to VPN for the DNS resolution into EC2 instances private IPswe are using dnsmasq service on the VPN-host which has a /etc/dnsmasq.hosts file where are manually… Read More »

Terraform: creating a project with an AWS EC2, VPC, and AWS cross-region VPC peering connection

18 March 2019
 

 One of the disappointing surprises in my AWS CloudFormation experience was the fact that it wasn’t able to automatically create cross-region VPC-peering connections. Note: this post originally was written in Rus on 28 June 2018 but now CloudFormation can do it, check the PeerRegion parameter of the AWS::EC2::VPCPeeringConnection resource. As a result – it tries… Read More »

OpenVPN: OpenVPN Access Server set up and AWS VPC peering configuration

21 February 2019
 

 OpenVPN Access Server is ready to use OpenVPN server which requires minimal configuration. The free version allows you to have two clients. If you need more – you can buy additional licenses. Infrastructure description Currently to access our resources such as Jenkins, Nexus etc we are using Allow Rules in AWS Security Groups where each user… Read More »