sayadi

How to SSH to an AWS EC2 Instance Running Linux from a CircleCI 2 Build

The Problem

If you use EC2 to host your application, and a tool like CircleCI to automate the deployment of new versions of your application, chances are, you've run into the problem of Circle not being able to SSH into your servers.

The problem is Circle could change the public IP of your runner for every new Build which prevents it from being able to access (SSH) the EC2 Instance. Unfortunately, Circle is not able to provide a list of public IP addresses to whitelist on a Security Group attached to the EC2 Instance. More on this here: https://discuss.circleci.com/t/circleci-source-ip/1202

sayadi

version: 2
general:
  branches:
    only:
      - dev
      - staging
      - prod
jobs:
  build:
    docker:

sayadi

    # 1- Install AWS CLI
    curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"
    unzip awscli-bundle.zip
    ./awscli-bundle/install -b ~/bin/aws
    
    # 2- Get the public IP of the current CircleCI runner
    PUBLIC_IP=$(curl ipinfo.io/ip)
    
    # 3- Get AWS Region
    # TODO Don't forget to replcae with your own Region

sayadi

version: 2
general:
  branches:
    only:
      - dev
      - staging
      - prod
jobs:
  build:
    docker:

sayadi

	<profiles>
		<profile>
			<id>default</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<properties>
				<spring.profile.from.maven/>
			</properties>
			<dependencies>

sayadi

spring.profiles.include=@spring.profile.from.maven@

sayadi

prop1=This is a shared value across all profiles for prop1.

sayadi

prop2=Non-production-specific value for prop2.

sayadi

spring.profiles.include=non-prod

prop3=Development-specific value for prop3.

sayadi

spring.profiles.include=non-prod

prop3=Staging-specific value for prop3.