Skip to content
This repository was archived by the owner on Sep 17, 2021. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/iam_gcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,12 @@ To restrict which permissions Security Monkey has to your projects, we'll create

![Add User to Service Account](images/add_user_to_service_account.png "Add User to Service Account")

Enable IAM API
---------------

For each GCP project you would like Security Monkey to access, you'll need to enable the IAM API. Visit the [IAM API page](https://console.cloud.google.com/apis/api/iam.googleapis.com/overview) page in the web console
and click 'Enable API' at the top of the screen. When dealing with many projects, you might prefer to do this with the gcloud command. For details on how to enable services with gcloud, visit the
[service-management](https://cloud.google.com/service-management/enable-disable#enabling_services) page. The IAM service name is 'iam.googleapis.com'.

Next:
-----
Expand Down
6 changes: 3 additions & 3 deletions docs/instance_launch_gcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,11 @@ Create an instance running Ubuntu 14.04 LTS using our 'securitymonkey' service a
Navigate to the [Create Instance page](https://console.developers.google.com/compute/instancesAdd). Fill in the following fields:

- **Name**: securitymonkey
- **Zone**: If using GCP Cloud SQL, select the same zone here.
- **Zone**: If using GCP Cloud SQL, select the same zone here. [(Zone List)](https://cloud.google.com/compute/docs/regions-zones/regions-zones#available)
- **Machine Type**: 1vCPU, 3.75GB (minimum; also known as n1-standard-1)
- **Boot Disk**: Ubuntu 14.04 LTS
- **Service Account**: securitymonkey
- **Firewall**: Allow HTTPS Traffic

Click the *Create* button to create the instance.

Expand All @@ -23,9 +24,8 @@ Connecting to your new instance:

We will connect to the new instance over ssh with the gcloud command:

$ gcloud compute ssh <USERNAME>@<PUBLIC_IP_ADDRESS> --zone us-central
$ gcloud compute ssh securitymonkey --zone <ZONE>

Replace the first parameter `<USERNAME>` with the username you authenticated gcloud with. Replace the last parameter `<PUBLIC_IP_ADDRESS>` with the Public IP of your instance.

Next:
-----
Expand Down
6 changes: 3 additions & 3 deletions docs/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,9 +110,9 @@ If you're using the bleeding edge (develop) branch, you will need to compile the
/usr/lib/dart/bin/pub build

# Copy the compiled Web UI to the appropriate destination
mkdir -p /usr/local/src/security_monkey/security_monkey/static/
/bin/cp -R /usr/local/src/security_monkey/dart/build/web/* /usr/local/src/security_monkey/security_monkey/static/
chgrp -R www-data /usr/local/src/security_monkey
sudo mkdir -p /usr/local/src/security_monkey/security_monkey/static/
sudo /bin/cp -R /usr/local/src/security_monkey/dart/build/web/* /usr/local/src/security_monkey/security_monkey/static/
sudo chgrp -R www-data /usr/local/src/security_monkey
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We had previously chown'd the /usr/local/src/security_monkey directory to ourselves:

sudo chown -R `whoami`:www-data /usr/local/src/security_monkey

So is it really required that we use sudo on these three commands?


### Configure the Application

Expand Down