Differences

This shows you the differences between two versions of the page.

--- installing_lucy_in_amazon [2016/11/17 10:57] – [Problems with sensing mails within Amazon's environment] lucy
+++ installing_lucy_in_amazon [2020/08/20 11:06] – lucy
@@ Line 1: / Line 1: @@
 ===== PREPARATION =====
-  * **Instance Type:** The LUCY AMI theoretically works on t1.micro. But in order to run with 600 Mybte Memory the system needs to be manually adjusted that LUCY will have more that 100 Mybte Idle Memory. Therefore **t1.micro is not recommended**. Rather install it on m1.small, m1.medium, c3.large and c1.medium instances. The best performance will be on c3.large, but using m1.small and m1.medium will be enough even for attacks with many thousands of recipients.
+  * **Instance Type:** The LUCY AMI requires at least 2 GB RAM  for 1000 recipients or less, 4 GB RAM for 5000 recipients or less and 8 GB RAM for 10'000 recipients or less. The minimal HDD is 100 GB (recommended is 250 GB). Please find your instance type here: https://aws.amazon.com/ec2/instance-types/
   * VPS Configuration: You need to enable “enableDnsHostnames” in your VPC configuration in Amazon: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html#vpc-dns-updating. Otherwise you will experience an apache configuration failure due to a missing IP address in /etc/hosts. If you start new instances you need to check your VPC configuration in https://console.aws.amazon.com/vpc/home to verify that this setting is enabled.
@@ Line 16: / Line 16: @@
   * **STEP 1: Download the AMI Image**: The AMI is available publicly via your Amazon account (use Ireland). In the AWS Management Console, open the **EC2** Dashboard. To choose an Amazon Machine Image (AMI), select the Community AMIs tab on the left hand side of the screen and search by name "**lucy**" (see the screenshot).
-{{ 78.jpg?600 }}
+{{ :comunity.png?600 |}}
   * **STEP 2: Launch the instance**:
-{{ aws1.png?600 }}
+{{ :launch.png?600 |}}
-  * **STEP 3: Choose an Instance Type**: there are many instance types available. Please scroll down to see them all. t2.micro is the smallest and will do with campaign with less than 1000 users.
-{{ aws3.png?600 }}
+  * **STEP 3: Choose an Instance Type**: there are many instance types available. Please scroll down to see them all. t2.medium matches with minimal hardware requirements.
+However, if you are not planning to have more than 1000 recipients, t2.small will do as well.
+{{ :4gb.png?600 |}}
   * **STEP 4: Review Instance, Set Security group and launch**: Click on "edit security group"
-{{ aws4b.png?600 }}
+{{ :review_aws.png?600 |}}
@@ Line 44: / Line 44: @@
   * **STEP 5: Create a key pair to connect**: Create a new public/private key pair for the SSH authentication and click "Download Key Pair".
-{{ aws5.png?600 }}
+{{ :select_existing_pair_of_keys.png?600 |}}
@@ Line 54: / Line 54: @@
   * **STEP 6: Connect to LUCY via the public IP**: After you have launched an EC2 instance, you can connect to LUCY’s public IP through SSH in order to configure the System. The public IP is visible as described in the screenshot below.
-{{ aws7.png?600 }}
+{{ :public_ip_aws.png?600 |}}
-  * **STEP 7: login as admim**: After the login type "sudo su" and press enter
+  * **STEP 7: login as admin**: After the login type "sudo su" and press enter
 {{ aws8.png?600 }}
+  * **STEP 8**:  Start the image and initiate the [[setup_script_tutorial|installation script]]. If you already have a domain name for LUCY, please make sure that you specify it within the setup script as the certificate for the administration will be based on that domain name.
-  * **STEP 8: Start Setup Script**: Initiate the Setup script to set up the System: python /opt/phishing/current/tools/setup/setup.py. This will initiate the Basic Setup where you can define the IP address, Web Logins, etc. The description of this script can be found here: [[setup_script_tutorial|Introduction]].
+  * **STEP 9**:  [[lucy_weblogin|Login]] to LUCY with a Webbrowser. Continue the setup in the browser using the credentials provided in the setup script. If you want to install a commercial version, please provide us with the [[how_to_activate_lucy|workstation ID]].
+  * **STEP 10**: Define your [[mail_delivery_methods_in_lucy|default mail delivery method]] in LUCY. In case you use the build in mail server: set the [[set_hostname_for_smtp_communication|hostname]] for the mail server.
+  * **STEP 11**: Setup a [[domain_configuration|domain]] in LUCY. This domain can be used for phishing simulations (landing pages) or the e-learning portal.
+  * **STEP 12**: Create a [[ssl_configuration|trusted certificate]] for the administration of LUCY.
-  * **STEP 9: Connect via HTTPS**:
+  * **STEP 13**: Create all the required administrators [[user_management|users]] in LUCY.
-Once the configuration is done you can connect to LUCY's public IP via the [[lucy_weblogin|web browser]] with the given password from the setup script.
+  * **STEP 14**: [[download_templates|Download]] all of the latest templates
+  * **STEP 15**: [[update_lucy|Update]] LUCY to the latest version
+  * **STEP 16**: Consider implementing additional [[security_considerations|security layers]]
+  * **STEP 17**: Give LUCY a [[white_label_lucy_-_custom_branding|custom branding]]
+  * **STEP 18**: Once you are all set you can try to [[create_your_first_phishing_campaign|setup your first campaign]]
+===== Installation problem? Contact our support =====
+In case you are planning to purchase LUCY or you are already a commercial client you can contact support@lucysecurity.com to open a ticket. We will get in touch with you within 24 hours.
 ===== Problems with sending mails within Amazon's environment =====
-In EC2 environments we have clients reporting that there is a limitation in the amount of outbound SMTP traffic. It seem that Amazon now has removed the EC2 limitations. See https://aws.amazon.com/forms/ec2-email-limit-rdns-request. But if you cannot send mails from LUCY from your EC2 environment we recommend uses Amazon's SES: https://aws.amazon.com/ses/
+In EC2 environments we have clients reporting that there is a limitation in the amount of outbound SMTP traffic. The limit is 200 mails a day and 1 email per second.
+More details here: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/limits.html
+Also, AWS does not support phishing simulations through SES as this is risky for Amazon public IP to get blacklisted. To avoid the limit and send not more than 200 mails per day, please use the [[scheduler|Scheduler]] which helps to distribute the sending messages over a longer period of time.