I have subscribe amazon EC2 for testing purpose. Everything is ok and most of normal tools to create instance.
However, i have created Linux instance CentOS 6 x86-x64. everything is understandable and changeable. but i m stuck at the Networking point.
My question is do i need to configure my linux instance etho which is under /etc/sysconfig/network-scripts/ifcfg-eth0
Currently its like this
My confusion is, normally we setup VPS static IP here and did the same and lost my instance access. i don't want to lose this instance again.
Basic question is, how can i configure it on static IP ? amazon instance give me one 1 IP and i added additional IP for nameserver purpose. they also given me Public DNS which is like "ec2-22-13-30-18.eu-west-2.compute.amazonaws.com"
Anyone have experience please help me to understand this as their documents are not human brain friendly.
If I remember correctly AWS EC2 instnaces by default will pull its internal IP information from DHCP server. The public IP is not set on the individual instances, a form of NAT is used as traffic cross into the public realm. To ensure you're public IP remains the same, you need to purchase an Elastic IP and assign to the instance, you do not need to set this elastic IP on the instance itself. If you do not purchase an elastic IP then if I remember correctly the public IP assigned is returned to the pool and may be reassigned elsewhere.
You don't need to edit eth0 configuration. As Matt said, they use DHCP to pull server's private IP from their internal network. For public access, you have to add a elastic IP from their interface and assign to your instance ( http://docs.aws.amazon.com/AmazonVPC...Guide/EIP.html ). Note that be very careful when you remove the particular elastic IP from your account and make sure you will not use it for any specific purposes. The elastic IP you assign will be NATed automatically to the assigned instance.
It is just like a VPS. You mean you want to fork a task from shell , then disconnect? If so, any tasks associated with the disconnected shell will be terminated until nohup is used. That is how Linux works and there is no difference with EC2 as well. if you want to run something in back ground and check the result back later, use "screen" utility. ( http://www.tecmint.com/screen-comman...nux-terminals/ )
Well, my tasks are not from command line, they are more graphical and running from windows programs. For example I am using World Machine, which generates surfaces, but it is running to long on my PC and additionally I want to avoid heating and ruining my PC. So I would just simply run these tasks on remote PC and come back later to get results. Is Amazon EC2 allowing this to do? This is why I need RDP, not VPS.