They are relatively similar and there is nothing special about an Amazon EC2 server that you can not achieve at home.

However, the two defaults that won't occur (by default) in an ordinary install of, say, CentOS are:

• +Security Groups - By default all external traffic is forbidden. You must set up a 'security group' to allow specific ports and I.Ps. However, allowing all ports and all I.Ps is relatively simple.
• +Key-Pair Authentication - By default it is not possible to log in to an EC2 server with a simple password. You must generate a private key and use that to log-in. Making bruteforcing much less likely.

Of course, there is a clear security negative with the EC2 cloud:

• -Public I.P - All EC2 instances have a public I.P., if you modify the security groups improperly then you're potentially opening yourself up to malicious traffic. Whilst on a local network your server can hide behind a NAT or not be connected to the internet at all.

There are other advantages of EC2 over, say, keeping the server in your bedroom. But these apply more generally to data center vs. bedroom:

• +Physical secutity
• +Safety from Natural Disasters
• +Safety from Power failure
• +etc. etc.

They are relatively similar and there is nothing special about an Amazon EC2 server that you can not achieve at home.

However, the two defaults that won't occur (by default) in an ordinary install of, say, CentOS are:

• +Security Groups - By default all external traffic is forbidden. You must set up a 'security group' to allow specific ports and I.Ps. However, allowing all ports and all I.Ps is relatively simple.
• +Key-Pair Authentication - By default it is not possible to log in to an EC2 server with a simple password. You must generate a private key and use that to log-in. Making bruteforcing much less likely.

Of course, there is a clear security negative with the EC2 cloud:

• -Public I.P - All EC2 instances have a public I.P., if you modify the security groups improperly then you're potentially opening yourself up to malicious traffic. Whilst on a local network your server can hide behind a NAT or not be connected to the internet at all.

There are other advantages of EC2 over, say, keeping the server in your bedroom. But these apply more generally to data center vs. bedroom:

• +Physical security
• +Safety from Natural Disasters
• +Safety from Power failure
• +etc. etc.

They are relatively similar and there is nothing special about an Amazon EC2 server that you can not achieve at home.

However, the two defaults that won't occur (by default) in an ordinary install of, say, CentOS are:

• +Security Groups - By default all external traffic is forbidden. You must set up a 'security group' to allow specific ports and I.Ps. However, allowing all ports and all I.Ps is relatively simple.
• +Key-Pair Authentication - By default it is not possible to log in to an EC2 server with a simple password. You must generate a private key and use that to log-in. Making bruteforcing much less likely.

Of course, there is a clear security negative with the EC2 cloud:

• -Public I.P - All EC2 instances have a public I.P., if you modify the security groups improperly then you're potentially opening yourself up to malicious traffic. Whilst on a local network your server can hide behind a NAT or not be connected to the internet at all.

There are other advantages of EC2 over, say, keeping the server in your bedroom. But these are less technical:

• +Physical secutity - The servers are probably safer from physical break-ins.

They are relatively similar and there is nothing special about an Amazon EC2 server that you can not achieve at home.

However, the two defaults that won't occur (by default) in an ordinary install of, say, CentOS are:

• +Security Groups - By default all external traffic is forbidden. You must set up a 'security group' to allow specific ports and I.Ps. However, allowing all ports and all I.Ps is relatively simple.
• +Key-Pair Authentication - By default it is not possible to log in to an EC2 server with a simple password. You must generate a private key and use that to log-in. Making bruteforcing much less likely.

Of course, there is a clear security negative with the EC2 cloud:

• -Public I.P - All EC2 instances have a public I.P., if you modify the security groups improperly then you're potentially opening yourself up to malicious traffic. Whilst on a local network your server can hide behind a NAT or not be connected to the internet at all.

There are other advantages of EC2 over, say, keeping the server in your bedroom. But these apply more generally to data center vs. bedroom:

• +Physical secutity
• +Safety from Natural Disasters
• +Safety from Power failure
• +etc. etc.