Sponsored Content
Full Discussion: Securing code in Amazon EC2
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Securing code in Amazon EC2 Post 302343788 by zefflyn on Thursday 13th of August 2009 03:11:05 PM
Old 08-13-2009
Use really strong passwords and private keys so no one can hack your box. Set the firewall rules to allow only your specific IP addresses to connect.

Do whatever you'd normally do to prevent hackers from getting into one of your machines and stealing code.
 

4 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Running MySQL on Amazon EC2 with Elastic Block Store

Here is an excellent article on Running MySQL on Amazon EC2 with Elastic Block Store. Amazon Web Services Developer Connection : Running MySQL on Amazon EC2 with Elastic Block Store (0 Replies)
Discussion started by: Neo
0 Replies

2. Virtualization and Cloud Computing

CEP as a Service (CEPaaS) with MapReduce on Amazon EC2 and Amazon S3

Tim Bass 11-25-2008 01:02 PM Just as I was starting to worry that complex event processing community has been captured by RDBMS pirates off the coast of Somalia, I rediscovered a new core blackboard architecture component, Hadoop. Hadoop is a framework for building applications on large... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. Virtualization and Cloud Computing

anyone running SELinux on amazon EC2?

Hi, Has anyone enabled SELinux on Amazon EC2? I tried to enable SELinux using a CentOS image, and the steps in the following post, but it didn't work!! Amazon Web Services Developer Community : Has anyone successfully enabled SELinux ... The steps i took: 1)I started with CentOS 5.3 base... (5 Replies)
Discussion started by: fun_indra
5 Replies

4. Shell Programming and Scripting

Ec2 login prompt script

Hey guys, trying to create a script that will run in the background until a user logs in and then present them with different options to proceed further. It is on an Ubuntu 10.04 Amazon ec2 system. The system runs 24/7 as it is and just needs to feed the prompt to whoever logs in. Is this... (3 Replies)
Discussion started by: 3therk1ll
3 Replies
ipkungfu(8)						      System Manager's Manual						       ipkungfu(8)

NAME
ipkungfu - An iptables-based firewall for Linux SYNOPSIS
ipkungfu [ -c ] [ -t ] [ -d ] [ -h ] [ -v ] [ --quiet ] [ --panic ] [ --no-caching DESCRIPTION
ipkungfu is an iptables-based Linux firewall. The primary design goals are security, ease of use, and performance, in that order. It takes advantage of advanced features of iptables, tcpwrappers, and the Linux kernel. It also simplifies the configuration of internet connection sharing, advanced routing, and other networking needs. OPTIONS
-c (or --check) Check whether ipkungfu is loaded, and report any command line options it may have been loaded with. -t (or --test) Runs a configuration test, and displays the results. Note that this does not test or display all configuration options. This gives you an opportunity to verify that major configuration options are correct before putting them into action. -d (or --disable) Disables the firewall. It is important to know exactly what this option does. All traffic is allowed in and out, and in the case of a gateway, all NATed traffic is forwarded (the option retains your connection sharing options). Custom rules are not implemented, and deny_hosts.conf is ignored. -f (or --flush) Disables the firewall COMPLETELY. All rules are flushed, all chains are removed. Any port forwarding or internet connection sharing will cease to work. -h (or --help) Displays brief usage information and exits. -v (or --version) Displays version information and exits. --quiet Runs ipkungfu with no standard output --panic Drops ALL traffic in all directions on all network interfaces. You should probably never use this option. The --panic option is available for the highly unusual situation where you know that an attack is underway but you know of no other way to stop it. --failsafe If ipkungfu fails, --failsafe will cause all firewall policies to revert to ACCEPT. This is useful when working with ipkungfu remotely, to prevent loss of remote access due to firewall failure. --no-caching Disables rules caching feature. FILES
/etc/ipkungfu/ipkungfu.conf /etc/ipkungfu/advanced.conf /etc/ipkungfu/accept_hosts.conf /etc/ipkungfu/deny_hosts.conf /etc/ipkungfu/custom.conf /etc/ipkungfu/log.conf /etc/ipkungfu/redirect.conf /etc/ipkungfu/services.conf /usr/sbin/ipkungfu /usr/share/doc/ipkungfu/AUTHORS /usr/share/doc/ipkungfu/README /usr/share/doc/ipkungfu/FAQ /usr/share/doc/ipkungfu/ChangeLog /usr/share/doc/ipkungfu/COPYING SEE ALSO
iptables(8). January 2003 ipkungfu(8)
All times are GMT -4. The time now is 04:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy