Tuesday, August 20, 2019

Python3 installation on Centos7

If you are installing the python3 on centos7 than it comes by default shipped with python 2.7.5 which is required by the core os of the centos. Now if you try to install through yum than you can't directly install the python3 instead you would require to install the  software collections first.

Software collections is an community project which allows you to build, install and use the multiple version of software on same system without affecting default system packages. It will enable the multiple version of the programming languages which are not available in the core repositories.

To install scl run the following command
# yum install centos-release-scl

To install the python3 run
# yum install rh-python36

You will also need to install the 'Development tools' which are required for building python modules
# yum groupinstall 'Development Tools'

Python virtual environments allows you to install the python modules in isolated location for a specific project, rather than being installed globally. This way it does not affect other python projects.

You can use venv to create the virtual environment in python

Create a new project folder where all project related files and binaries will reside

#mkdir project

# cd project

Next you have to enable the python36 with the scl first before you can use it do
#scl enable rh-python36 bash

You can create the virtual environment
python -m venv my_project_venv

Execute the following command to enable the virtual environment
source my_project_venv/bin/activate

You should get a cursor as below now
$ (my_project_venv) user@host:~/my_new_project$

The prefix indicates that the Python virtual environment my_project_venv is currently active

Now your virtual environment is ready to use.

Wednesday, August 7, 2019

Main Advantages of Using Transit Gateway in Amazon AWS

  • Per region VPN Tunnels: Instead of building tunnels every time we a new VPC is created . It allows to simply attach the VPC to the transit gateway within the region which will already have a VPN established. Once attached, it will simply be a matter of adding routing propagations to establish the connectivity of the VPC with VPN.

  • Attach to Transit Gateway once rather than peer to multiple VPCs: Every time a new VPC is created , It often times required to peer that VPC with other accounts and shared environments. With the Transit gateway, you can simply attach the VPC to the transit gateway and associate that attachment with the right routing domain and allow routes to propagate which will give that new VPC access to multiple VPCs and vice-versa. 

The known limitation of the AWS Transit gateway is the fact that it does not support the cross region support for which Inter-region Vpc peering is required. Though is in the future pipeline and rather the correct direction to be implemented once the AWS releases this functionality in the near future.

The best practice to deploy the AWS transit gateway is by using the Infrastructure as code practices tool like Terraform. Code i will share in the future post so stay tuned and subscribe to our blog.