Packer Template for CentOS 6.9 with Oracle installed and prepared for Delphix
Switch branches/tags
Nothing to show
Clone or download
Adam Bowen
Latest commit ed93b3f Jul 26, 2018

Packer Template for CentOS 6.9 with Oracle installed and prepared for Delphix

Table of Contents

  1. Description
  2. Installation
  3. Usage
  4. Links
  5. Contribute
  6. Reporting Issues
  7. License


This is a working Packer template that will create an AWS image that consists of:

  • CentOS
  • Oracle
  • Delphix prerequisites installed and configured for use.

This Packer template requires the provisioned system to be able to access and via an unauthenticated http location (like an s3 bucket).


Via Docker (the easiest)

  1. Clone this repository
  2. Navigate into the cloned directory
  3. Copy the .example.docker to .environment.env
git clone
cd packer-templates
cp .example.docker .example.env

Without Docker (the second easiest)

  1. Clone this repository
  2. Navigate into the cloned directory
  3. Copy the .example.env to .environment.env

This template depends on packer and ansible existing in your path. If you are running a Mac, then the easiest way is to install via homebrew. After cloning this repo, install the required ansible dependencies.

git clone
cd packer-templates
brew install ansible packer
cp .example.env .example.env
ansible-galaxy install -r roles/requirements.yml



  1. Edit the .environment.env file in the root directory of the cloned repo

user variables

  1. AWS_ACCESS_KEY_ID - The AWS_ACCESS_KEY_ID environment variable
  2. AWS_SECRET_ACCESS_KEY - The AWS_SECRET_ACCESS_KEY environment variable
  3. AWS_BUILD_REGION - The region packer will build the temporary infrastructure for the AMI
  4. AWS_DESTINATION_REGIONS - A comma-delimited list of regions for packer to copy the AMI
  5. ORACLE_BINARIES_ROOT_URL - The URL where the AWS instance can retrieve the Oracle binaries during the packer build
  6. AWS_VPC_ID - The VPC ID from the region that packer will use
  7. AWS_SUBNET_ID - The subnet ID from the VPC that packer will use #The below values are arbitrary, and only for tagging resources
  8. AWS_EXPIRATION - The date this AMI is expired, i.e. "2037-07-01" or "never"
  9. AWS_OWNER - The name of the person who owns the AMI, i.e. "Adam Bowen"
  10. AWS_PROJECT - The name of the project that the AMI belongs, or came, from


Via Docker

  1. (Optional) Pull the cloudsurgeon/rds_demo docker image
  2. Run the container against the packer template you want to use.
docker pull cloudsurgeon/packer-ansible
docker run --env-file .environment.env -v $(pwd):/build -i -t cloudsurgeon/packer-ansible:latest build delphix-centos7-rds.json

Without Docker

  1. source the .example.env file
  2. run packer against the template you want to use:
source .example.env
packer build delphix-centOS6.9-oracle11.2.0.4.json
packer build delphix-centOS6.9-oracle11.2.0.4.json 
cent69-Oracle11204 output will be in this color.

==> cent69-Oracle11204: Force Deregister flag found, skipping prevalidating AMI Name
    cent69-Oracle11204: Found Image ID: ami-8b44f234
==> cent69-Oracle11204: Creating temporary keypair: packer_5ad55a87-66df-e148-9439-a7bd06aa04fb
==> cent69-Oracle11204: Creating temporary security group for this instance: packer_5ad55ad1-10d5-7eda-e077-9741925ce7e4
==> cent69-Oracle11204: Authorizing access to port 22 from in the temporary security group...
==> cent69-Oracle11204: Launching a source AWS instance...
==> cent69-Oracle11204: Adding tags to source instance
    cent69-Oracle11204: Adding tag: "Name": "Packer Builder"
    cent69-Oracle11204: Instance ID: i-0434f9b2e3a90c0c3
==> cent69-Oracle11204: Waiting for instance (i-0434f9b2e3a90c0c3) to become ready...
==> cent69-Oracle11204: Waiting for SSH to become available...


Include useful links to references or more advanced guides.


Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.


  1. Fork the project.
  2. Make your bug fix or new feature.
  3. Add tests for your code.
  4. Send a pull request.

Contributions must be signed as User Name <>. Make sure to set up Git with user name and email address. Bug fixes should branch from the current stable branch. New feature should be based on the master branch.

Reporting Issues

Issues should be reported in the repo's issue tab.


This is code is licensed under the Apache License 2.0. Full license is available here.