Skip to content
Adobe Experience Manager (AEM) machine images builder using Packer
Ruby Puppet Shell Makefile Python Pascal
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
conf Bump up to next pre-release version 4.11.0-pre.0 Aug 19, 2019
docs Add config property aws.temporary_security_group_source_cidr. Aug 14, 2019
provisioners Excluding python-urllib3 from yum upgrading … (#171) Aug 14, 2019
scripts Update apache_module_base_url as a configuration item (aem.dispatcher… Mar 4, 2019
templates Fixed hiera SSM Parameterstore lookup for keystore password (#173) Aug 17, 2019
test
.gitignore
.pylintrc Add custom Ansible module Python files check to lint target. Dec 10, 2018
.rtk.json Add Packer AEM version as AWS resources tag including created AMI. Aug 12, 2019
.rubocop.yml Revert cert size check to use > 0 due to positive? not available on r… Dec 9, 2018
.travis.yml Switch to Travis build with generic language. Jan 8, 2019
CHANGELOG.md
Gemfile - Upgrade aem_curator to 2.0.0 Jun 6, 2019
Gemfile.lock Remove old ServerSpec and nokogiri dependencies which require native … Aug 3, 2019
LICENSE
Makefile Bump up to next pre-release version 4.11.0-pre.0 Aug 19, 2019
Puppetfile Upgrade aem_curator to 2.7.0 . Jul 31, 2019
README.md Add snyk vuln badge. Jun 3, 2019
buildspec.yml
requirements.txt Upgrade Ansible to 2.8.2 . Jul 12, 2019

README.md

Build Status Known Vulnerabilities

Packer AEM

Packer AEM is a set of Packer templates for creating Adobe Experience Manager (AEM) machine and container images, which include the following components:

Machine Images Diagram

The AMIs produced by Packer AEM will then be used by AEM AWS Stack Builder to create an AEM environment on AWS.

Learn more about Packer AEM:

Packer AEM is part of AEM OpenCloud platform.

Installation

Usage

  • Set up the required AWS resources
  • Create configuration file
  • Create the AMIs by running make <platform>-<component> version=<version> config_path=<path/to/config/dir>, for example: make aws-author version=1.2.3 config_path=stage/user-config/aws-rhel7-aem64/

To retrieve the latest AMI IDs for all AEM AWS Stack Builder components, run the command make ami-ids config_path=<path/to/config/dir>, and the AMI IDs will be written into stage/stack-builder-configs/<aem_profile>-<os_type>-stack-builder-ami-ids.yaml file(s). These files can then be dropped in to AEM AWS Stack Builder configuration path.

Testing

Testing with remote dependencies

You can run integration test for creating the AMIs for all components using the command make test-integration test_id=<sometestid>, which downloads the dependencies from the Internet.

Testing with local dependencies

If you're working on the dependencies of Packer AEM and would like to test them as part of machine images creation before pushing the changes upstream, you need to:

Debugging

If you want to jump on the environment that Packer launched and you want to debug/troubleshoot it, you can modify the Makefile and set Packer to build in debug mode by replacing packer build command with packer build -debug, and then run the image creation again. With debug enabled, Packer will prompt you before terminating the EC2 instance / Docker container, giving you the chance to check it.

When running in debug mode, Packer will make the private key available on the repo directory for you to use, e.g. ssh -i ec2.pem ec2-user@<ip-address>

Please read Packer Debugging for further information.

You can’t perform that action at this time.