COSC349 Assignment 1
===
###### tags: `cosc349`
(http://www.cs.otago.ac.nz/cosc349/assignments/COSC349A1.pdf)
# Table of Contents
[TOC]
## Marking Schedule
## Interaction of Virtual Machines
The 3 Virtual Machine(VM) in our assignment are ubuntu/xenial64 [Vagrant Boxs](https://www.vagrantup.com/docs/boxes.html).
## Loading Times
The load time for the 3 VMs is currently about 10mins
## Getting Started
type the following command to initial the vagrantfile
### [vagrant init](https://www.vagrantup.com/intro/getting-started/)
```gherkin=
$ vagrant init
```
Once completed the follwing message should appear
```gherkin=
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
```
The initial vagrantfile contains the following information
```gherkin=
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://vagrantcloud.com/search.
config.vm.box = "base"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# NOTE: This will enable public access to the opened port
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
# config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
end
```
## Useful Vagrant Commands
#### Command: [vagrant reload](https://https://www.vagrantup.com/docs/cli/reload.html) [name|id]
The equivalent of running a halt followed by an up.
[](https://)
This command is usually required for changes made in the Vagrantfile to take effect. After making any modifications to the Vagrantfile, a reload should be called.
#### Command: vagrant provision [vm-name]
Runs any configured provisioners against the running Vagrant managed machine.
This command is a great way to quickly test any provisioners, and is especially useful for incremental development.
https://www.vagrantup.com/docs/cli/init.html
# AWS
## Setting up AWS
Originally I had hoped to actually do the VM within the AWS cloud system and I used this [blog](https://https://blog.wimwauters.com/vagrant-aws-launch-multiple-instances/) to help create a template for the Vagrant file
```gherkin=
ssh -i ~/349/vagrant-multivm-master/Assign_1.pem.txt ec2-user@54.87.163.37
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '54.87.163.37' (ECDSA) to the list of known hosts.
__| __|_ )
_| ( / Amazon Linux 2 AMI
___|\___|___|
https://aws.amazon.com/amazon-linux-2/
4 package(s) needed for security, out of 12 available
Run "sudo yum update" to apply all updates.
[ec2-user@ip-172-31-34-223 ~]$ sudo yum update
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 2.4 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package amazon-linux-extras.noarch 0:1.6.8-1.amzn2 will be updated
---> Package amazon-linux-extras.noarch 0:1.6.9-1.amzn2 will be an update
---> Package amazon-linux-extras-yum-plugin.noarch 0:1.6.8-1.amzn2 will be updated
---> Package amazon-linux-extras-yum-plugin.noarch 0:1.6.9-1.amzn2 will be an update
---> Package amazon-ssm-agent.x86_64 0:2.3.372.0-1.amzn2 will be updated
---> Package amazon-ssm-agent.x86_64 0:2.3.662.0-1.amzn2 will be an update
---> Package curl.x86_64 0:7.61.1-9.amzn2.0.1 will be updated
---> Package curl.x86_64 0:7.61.1-11.amzn2.0.2 will be an update
---> Package ec2-hibinit-agent.noarch 0:1.0.0-3.amzn2 will be updated
---> Package ec2-hibinit-agent.noarch 0:1.0.0-4.amzn2 will be an update
---> Package ec2-instance-connect.noarch 0:1.1-9.amzn2 will be updated
---> Package ec2-instance-connect.noarch 0:1.1-10.amzn2 will be an update
---> Package kernel.x86_64 0:4.14.138-114.102.amzn2 will be installed
---> Package libcurl.x86_64 0:7.61.1-9.amzn2.0.1 will be updated
---> Package libcurl.x86_64 0:7.61.1-11.amzn2.0.2 will be an update
---> Package libssh2.x86_64 0:1.4.3-12.amzn2.2 will be updated
---> Package libssh2.x86_64 0:1.4.3-12.amzn2.2.1 will be an update
---> Package nss-softokn.x86_64 0:3.36.0-5.amzn2 will be updated
---> Package nss-softokn.x86_64 0:3.36.0-5.amzn2.0.1 will be an update
---> Package nss-softokn-freebl.x86_64 0:3.36.0-5.amzn2 will be updated
---> Package nss-softokn-freebl.x86_64 0:3.36.0-5.amzn2.0.1 will be an update
---> Package systemtap-runtime.x86_64 0:3.2-4.amzn2.0.2 will be updated
---> Package systemtap-runtime.x86_64 0:4.1-0.20190208git4e76869512d2.amzn2.0.2 will be an update
--> Processing Dependency: libjson-c.so.2()(64bit) for package: systemtap-runtime-4.1-0.20190208git4e76869512d2.amzn2.0.2.x86_64
--> Running transaction check
---> Package json-c.x86_64 0:0.11-4.amzn2.0.3 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
kernel x86_64 4.14.138-114.102.amzn2 amzn2-core 20 M
Updating:
amazon-linux-extras noarch 1.6.9-1.amzn2 amzn2-core 36 k
amazon-linux-extras-yum-plugin noarch 1.6.9-1.amzn2 amzn2-core 9.6 k
amazon-ssm-agent x86_64 2.3.662.0-1.amzn2 amzn2-core 15 M
curl x86_64 7.61.1-11.amzn2.0.2 amzn2-core 343 k
ec2-hibinit-agent noarch 1.0.0-4.amzn2 amzn2-core 13 k
ec2-instance-connect noarch 1.1-10.amzn2 amzn2-core 21 k
libcurl x86_64 7.61.1-11.amzn2.0.2 amzn2-core 291 k
libssh2 x86_64 1.4.3-12.amzn2.2.1 amzn2-core 135 k
nss-softokn x86_64 3.36.0-5.amzn2.0.1 amzn2-core 318 k
nss-softokn-freebl x86_64 3.36.0-5.amzn2.0.1 amzn2-core 225 k
systemtap-runtime x86_64 4.1-0.20190208git4e76869512d2.amzn2.0.2
amzn2-core 442 k
Installing for dependencies:
json-c x86_64 0.11-4.amzn2.0.3 amzn2-core 31 k
Transaction Summary
================================================================================
Install 1 Package (+1 Dependent package)
Upgrade 11 Packages
Total download size: 37 M
Is this ok [y/d/N]: y
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
(1/13): amazon-linux-extras-1.6.9-1.amzn2.noarch.rpm | 36 kB 00:00
(2/13): amazon-linux-extras-yum-plugin-1.6.9-1.amzn2.noarc | 9.6 kB 00:00
(3/13): curl-7.61.1-11.amzn2.0.2.x86_64.rpm | 343 kB 00:00
(4/13): ec2-hibinit-agent-1.0.0-4.amzn2.noarch.rpm | 13 kB 00:00
(5/13): ec2-instance-connect-1.1-10.amzn2.noarch.rpm | 21 kB 00:00
(6/13): json-c-0.11-4.amzn2.0.3.x86_64.rpm | 31 kB 00:00
(7/13): amazon-ssm-agent-2.3.662.0-1.amzn2.x86_64.rpm | 15 MB 00:00
(8/13): libcurl-7.61.1-11.amzn2.0.2.x86_64.rpm | 291 kB 00:00
(9/13): libssh2-1.4.3-12.amzn2.2.1.x86_64.rpm | 135 kB 00:00
(10/13): nss-softokn-3.36.0-5.amzn2.0.1.x86_64.rpm | 318 kB 00:00
(11/13): nss-softokn-freebl-3.36.0-5.amzn2.0.1.x86_64.rpm | 225 kB 00:00
(12/13): systemtap-runtime-4.1-0.20190208git4e76869512d2.a | 442 kB 00:00
(13/13): kernel-4.14.138-114.102.amzn2.x86_64.rpm | 20 MB 00:00
--------------------------------------------------------------------------------
Total 61 MB/s | 37 MB 00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : libssh2-1.4.3-12.amzn2.2.1.x86_64 1/24
Updating : libcurl-7.61.1-11.amzn2.0.2.x86_64 2/24
Updating : curl-7.61.1-11.amzn2.0.2.x86_64 3/24
Installing : json-c-0.11-4.amzn2.0.3.x86_64 4/24
Updating : nss-softokn-freebl-3.36.0-5.amzn2.0.1.x86_64 5/24
Updating : amazon-linux-extras-1.6.9-1.amzn2.noarch 6/24
Updating : amazon-linux-extras-yum-plugin-1.6.9-1.amzn2.noarch 7/24
Updating : nss-softokn-3.36.0-5.amzn2.0.1.x86_64 8/24
Updating : systemtap-runtime-4.1-0.20190208git4e76869512d2.amzn2.0. 9/24
ec2-instance-connect:x:998:996::/home/ec2-instance-connect:/sbin/nologin
Updating : ec2-instance-connect-1.1-10.amzn2.noarch 10/24
Updating : amazon-ssm-agent-2.3.662.0-1.amzn2.x86_64 11/24
Installing : kernel-4.14.138-114.102.amzn2.x86_64 12/24
Updating : ec2-hibinit-agent-1.0.0-4.amzn2.noarch 13/24
Cleanup : ec2-instance-connect-1.1-9.amzn2.noarch 14/24
Cleanup : curl-7.61.1-9.amzn2.0.1.x86_64 15/24
Cleanup : libcurl-7.61.1-9.amzn2.0.1.x86_64 16/24
Cleanup : nss-softokn-3.36.0-5.amzn2.x86_64 17/24
Cleanup : amazon-linux-extras-yum-plugin-1.6.8-1.amzn2.noarch 18/24
Cleanup : ec2-hibinit-agent-1.0.0-3.amzn2.noarch 19/24
Cleanup : amazon-linux-extras-1.6.8-1.amzn2.noarch 20/24
Cleanup : nss-softokn-freebl-3.36.0-5.amzn2.x86_64 21/24
Cleanup : libssh2-1.4.3-12.amzn2.2.x86_64 22/24
Cleanup : systemtap-runtime-3.2-4.amzn2.0.2.x86_64 23/24
Cleanup : amazon-ssm-agent-2.3.372.0-1.amzn2.x86_64 24/24
Verifying : nss-softokn-3.36.0-5.amzn2.0.1.x86_64 1/24
Verifying : amazon-linux-extras-1.6.9-1.amzn2.noarch 2/24
Verifying : nss-softokn-freebl-3.36.0-5.amzn2.0.1.x86_64 3/24
Verifying : ec2-hibinit-agent-1.0.0-4.amzn2.noarch 4/24
Verifying : kernel-4.14.138-114.102.amzn2.x86_64 5/24
Verifying : curl-7.61.1-11.amzn2.0.2.x86_64 6/24
Verifying : amazon-ssm-agent-2.3.662.0-1.amzn2.x86_64 7/24
Verifying : systemtap-runtime-4.1-0.20190208git4e76869512d2.amzn2.0.2.x86_64 8/24
Verifying : ec2-instance-connect-1.1-10.amzn2.noarch 9/24
Verifying : amazon-linux-extras-yum-plugin-1.6.9-1.amzn2.noarch 10/24
Verifying : libcurl-7.61.1-11.amzn2.0.2.x86_64 11/24
Verifying : json-c-0.11-4.amzn2.0.3.x86_64 12/24
Verifying : libssh2-1.4.3-12.amzn2.2.1.x86_64 13/24
Verifying : ec2-hibinit-agent-1.0.0-3.amzn2.noarch 14/24
Verifying : amazon-ssm-agent-2.3.372.0-1.amzn2.x86_64 15/24
Verifying : nss-softokn-3.36.0-5.amzn2.x86_64 16/24
Verifying : systemtap-runtime-3.2-4.amzn2.0.2.x86_64 17/24
Verifying : nss-softokn-freebl-3.36.0-5.amzn2.x86_64 18/24
Verifying : libcurl-7.61.1-9.amzn2.0.1.x86_64 19/24
Verifying : libssh2-1.4.3-12.amzn2.2.x86_64 20/24
Verifying : curl-7.61.1-9.amzn2.0.1.x86_64 21/24
Verifying : amazon-linux-extras-1.6.8-1.amzn2.noarch 22/24
Verifying : ec2-instance-connect-1.1-9.amzn2.noarch 23/24
Verifying : amazon-linux-extras-yum-plugin-1.6.8-1.amzn2.noarch 24/24
Installed:
kernel.x86_64 0:4.14.138-114.102.amzn2
Dependency Installed:
json-c.x86_64 0:0.11-4.amzn2.0.3
Updated:
amazon-linux-extras.noarch 0:1.6.9-1.amzn2 amazon-linux-extras-yum-plugin.noarch 0:1.6.9-1.amzn2
amazon-ssm-agent.x86_64 0:2.3.662.0-1.amzn2 curl.x86_64 0:7.61.1-11.amzn2.0.2
ec2-hibinit-agent.noarch 0:1.0.0-4.amzn2 ec2-instance-connect.noarch 0:1.1-10.amzn2
libcurl.x86_64 0:7.61.1-11.amzn2.0.2 libssh2.x86_64 0:1.4.3-12.amzn2.2.1
nss-softokn.x86_64 0:3.36.0-5.amzn2.0.1 nss-softokn-freebl.x86_64 0:3.36.0-5.amzn2.0.1
systemtap-runtime.x86_64 0:4.1-0.20190208git4e76869512d2.amzn2.0.2
Complete!
```
> I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it. [name=Bill Gates]
```gherkin=
[ec2-user@ip-172-31-34-223 ~]$ sudo yum install -y httpd24 php56
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 2.4 kB 00:00:00
No package httpd24 available.
No package php56 available.
Error: Nothing to do
[ec2-user@ip-172-31-34-223 ~]$ sudo yum install -y httpd php
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Resolving Dependencies
--> Running transaction check
---> Package httpd.x86_64 0:2.4.39-1.amzn2.0.1 will be installed
--> Processing Dependency: httpd-tools = 2.4.39-1.amzn2.0.1 for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: httpd-filesystem = 2.4.39-1.amzn2.0.1 for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: system-logos-httpd for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: mod_http2 for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: httpd-filesystem for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: /etc/mime.types for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.4.39-1.amzn2.0.1.x86_64
--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.4.39-1.amzn2.0.1.x86_64
---> Package php.x86_64 0:5.4.16-45.amzn2.0.6 will be installed
--> Processing Dependency: php-cli(x86-64) = 5.4.16-45.amzn2.0.6 for package: php-5.4.16-45.amzn2.0.6.x86_64
--> Processing Dependency: php-common(x86-64) = 5.4.16-45.amzn2.0.6 for package: php-5.4.16-45.amzn2.0.6.x86_64
--> Running transaction check
---> Package apr.x86_64 0:1.6.3-5.amzn2.0.2 will be installed
---> Package apr-util.x86_64 0:1.6.1-5.amzn2.0.2 will be installed
--> Processing Dependency: apr-util-bdb(x86-64) = 1.6.1-5.amzn2.0.2 for package: apr-util-1.6.1-5.amzn2.0.2.x86_64
---> Package generic-logos-httpd.noarch 0:18.0.0-4.amzn2 will be installed
---> Package httpd-filesystem.noarch 0:2.4.39-1.amzn2.0.1 will be installed
---> Package httpd-tools.x86_64 0:2.4.39-1.amzn2.0.1 will be installed
---> Package mailcap.noarch 0:2.1.41-2.amzn2 will be installed
---> Package mod_http2.x86_64 0:1.15.1-1.amzn2 will be installed
---> Package php-cli.x86_64 0:5.4.16-45.amzn2.0.6 will be installed
---> Package php-common.x86_64 0:5.4.16-45.amzn2.0.6 will be installed
--> Processing Dependency: libzip.so.2()(64bit) for package: php-common-5.4.16-45.amzn2.0.6.x86_64
--> Running transaction check
---> Package apr-util-bdb.x86_64 0:1.6.1-5.amzn2.0.2 will be installed
---> Package libzip010-compat.x86_64 0:0.10.1-9.amzn2.0.5 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
===========================================================================================================================================================
Package Arch Version Repository Size
===========================================================================================================================================================
Installing:
httpd x86_64 2.4.39-1.amzn2.0.1 amzn2-core 1.3 M
php x86_64 5.4.16-45.amzn2.0.6 amzn2-core 1.4 M
Installing for dependencies:
apr x86_64 1.6.3-5.amzn2.0.2 amzn2-core 118 k
apr-util x86_64 1.6.1-5.amzn2.0.2 amzn2-core 99 k
apr-util-bdb x86_64 1.6.1-5.amzn2.0.2 amzn2-core 19 k
generic-logos-httpd noarch 18.0.0-4.amzn2 amzn2-core 19 k
httpd-filesystem noarch 2.4.39-1.amzn2.0.1 amzn2-core 23 k
httpd-tools x86_64 2.4.39-1.amzn2.0.1 amzn2-core 87 k
libzip010-compat x86_64 0.10.1-9.amzn2.0.5 amzn2-core 30 k
mailcap noarch 2.1.41-2.amzn2 amzn2-core 31 k
mod_http2 x86_64 1.15.1-1.amzn2 amzn2-core 147 k
php-cli x86_64 5.4.16-45.amzn2.0.6 amzn2-core 2.9 M
php-common x86_64 5.4.16-45.amzn2.0.6 amzn2-core 566 k
Transaction Summary
===========================================================================================================================================================
Install 2 Packages (+11 Dependent packages)
Total download size: 6.7 M
Installed size: 22 M
Downloading packages:
(1/13): apr-1.6.3-5.amzn2.0.2.x86_64.rpm | 118 kB 00:00:00
(2/13): apr-util-1.6.1-5.amzn2.0.2.x86_64.rpm | 99 kB 00:00:00
(3/13): generic-logos-httpd-18.0.0-4.amzn2.noarch.rpm | 19 kB 00:00:00
(4/13): apr-util-bdb-1.6.1-5.amzn2.0.2.x86_64.rpm | 19 kB 00:00:00
(5/13): httpd-filesystem-2.4.39-1.amzn2.0.1.noarch.rpm | 23 kB 00:00:00
(6/13): httpd-tools-2.4.39-1.amzn2.0.1.x86_64.rpm | 87 kB 00:00:00
(7/13): httpd-2.4.39-1.amzn2.0.1.x86_64.rpm | 1.3 MB 00:00:00
(8/13): libzip010-compat-0.10.1-9.amzn2.0.5.x86_64.rpm | 30 kB 00:00:00
(9/13): mod_http2-1.15.1-1.amzn2.x86_64.rpm | 147 kB 00:00:00
(10/13): php-5.4.16-45.amzn2.0.6.x86_64.rpm | 1.4 MB 00:00:00
(11/13): php-cli-5.4.16-45.amzn2.0.6.x86_64.rpm | 2.9 MB 00:00:00
(12/13): php-common-5.4.16-45.amzn2.0.6.x86_64.rpm | 566 kB 00:00:00
(13/13): mailcap-2.1.41-2.amzn2.noarch.rpm | 31 kB 00:00:00
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Total 15 MB/s | 6.7 MB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : apr-1.6.3-5.amzn2.0.2.x86_64 1/13
Installing : apr-util-bdb-1.6.1-5.amzn2.0.2.x86_64 2/13
Installing : apr-util-1.6.1-5.amzn2.0.2.x86_64 3/13
Installing : httpd-tools-2.4.39-1.amzn2.0.1.x86_64 4/13
Installing : generic-logos-httpd-18.0.0-4.amzn2.noarch 5/13
Installing : mailcap-2.1.41-2.amzn2.noarch 6/13
Installing : httpd-filesystem-2.4.39-1.amzn2.0.1.noarch 7/13
Installing : mod_http2-1.15.1-1.amzn2.x86_64 8/13
Installing : httpd-2.4.39-1.amzn2.0.1.x86_64 9/13
Installing : libzip010-compat-0.10.1-9.amzn2.0.5.x86_64 10/13
Installing : php-common-5.4.16-45.amzn2.0.6.x86_64 11/13
Installing : php-cli-5.4.16-45.amzn2.0.6.x86_64 12/13
Installing : php-5.4.16-45.amzn2.0.6.x86_64 13/13
Verifying : apr-util-1.6.1-5.amzn2.0.2.x86_64 1/13
Verifying : libzip010-compat-0.10.1-9.amzn2.0.5.x86_64 2/13
Verifying : php-cli-5.4.16-45.amzn2.0.6.x86_64 3/13
Verifying : apr-util-bdb-1.6.1-5.amzn2.0.2.x86_64 4/13
Verifying : httpd-tools-2.4.39-1.amzn2.0.1.x86_64 5/13
Verifying : httpd-2.4.39-1.amzn2.0.1.x86_64 6/13
Verifying : httpd-filesystem-2.4.39-1.amzn2.0.1.noarch 7/13
Verifying : php-5.4.16-45.amzn2.0.6.x86_64 8/13
Verifying : mod_http2-1.15.1-1.amzn2.x86_64 9/13
Verifying : apr-1.6.3-5.amzn2.0.2.x86_64 10/13
Verifying : mailcap-2.1.41-2.amzn2.noarch 11/13
Verifying : generic-logos-httpd-18.0.0-4.amzn2.noarch 12/13
Verifying : php-common-5.4.16-45.amzn2.0.6.x86_64 13/13
Installed:
httpd.x86_64 0:2.4.39-1.amzn2.0.1 php.x86_64 0:5.4.16-45.amzn2.0.6
Dependency Installed:
apr.x86_64 0:1.6.3-5.amzn2.0.2 apr-util.x86_64 0:1.6.1-5.amzn2.0.2 apr-util-bdb.x86_64 0:1.6.1-5.amzn2.0.2
generic-logos-httpd.noarch 0:18.0.0-4.amzn2 httpd-filesystem.noarch 0:2.4.39-1.amzn2.0.1 httpd-tools.x86_64 0:2.4.39-1.amzn2.0.1
libzip010-compat.x86_64 0:0.10.1-9.amzn2.0.5 mailcap.noarch 0:2.1.41-2.amzn2 mod_http2.x86_64 0:1.15.1-1.amzn2
php-cli.x86_64 0:5.4.16-45.amzn2.0.6 php-common.x86_64 0:5.4.16-45.amzn2.0.6
Complete!
```
However after some time trying to get the AMI user account settings correct it prove too diffcuilt to set up properly
I used this blog to help configure the Vagrant file to the appropriate settings
http://www.thisprogrammingthing.com/2015/multiple-vagrant-vms-in-one-vagrantfile/
https://www.vagrantup.com/docs/cli/up.html
https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html
and thus decided to just use the Virtual Box.
:::info
**Find this document incomplete?** Leave a comment!
:::
#### tags: `Documentation` `cosc349`
Sign in with Wallet
Connect another wallet