conjurinc / appliance-docker-ami Goto Github PK

The Conjur Docker instance that is invoked from our AMI should be started with a default Seccomp security profile.
We can use the one that we recommend in our documentation.

The AMI build process works by downloading and saving the Conjur image locally before uploading the gzipped tar file to the AMI. This is super inefficient.

A better approach would be to download the Conjur image directly to the EC2 instance before saving it off as an AMI. Our registry credentials would need to be injected onto the instance prior to docker pull ...., then removed from the instance after the image has been pulled.

Details to be provided

To help simplify setup documentation, we should bring the AMI in line with our recommended configuration.

• Add EC2 user to the sudu group (sudo usermod -a -G docker ec2-user)
• Add an optional sample config file
• Add a seccomp file and add to docker run command
• create recommended folders (and mount into docker image)