4 ms·
The ones that I noticed in my eval of rackspace 1) internal traffic between boxes at rackspace is on the public network unless you setup ipsec/ssl http://serv
by anthony_barker 15y ago
The ones that I noticed in my eval of rackspace
1) internal traffic between boxes at rackspace is on the public network unless you setup ipsec/ssl
http://serverfault.com/questions/184655/suggestions-for-vpn-solution-between-backend-servers http://serverfault.com/questions/184655/suggestions-for-vpn-...
2) Definite lack of firewalls and no deep packet inspection
3) No free micro tier for testing/dev
Others:
a) I don't like all the naming conventions of AWS - reminds me of Starbucks where a small is "tall"
b) Neither seem to offer IDS out of the box and/or outgoing firewalls although one can set-up snort/sourcefire (AWS offers this)
https://aws.amazon.com/solution-providers/isv/sourcefire https://aws.amazon.com/solution-providers/isv/sourcefire
c) No two factor authentication services out of the box for application authentication(need to use yubikey/duo security)
- Cloven 15y ago1) no, rackspace boxes have two networks; an internal (inside the cloud) and an external (public)