Finally the help of IT is here

Blog of computer solutions.

How to create an external dns server with Amazon Route 53

Posted by Xaus Xavier Nadal 9th on December 2014

Creating an external dns server with Amazon Route 53 is as simple as having an Amazon AWS account and following the steps that we will show you next, but first of all, what is Route 53 and what is Route53 for?

Amazon Route 53 It is a DNS service in the public cloud.

Amazon Route 53Amazon Route 53 is normally used to load balance (ELB) between EC2 instances, map EC2 instances or simply map S3 buckets, but in this article we are going to use the power of a DNS in Cloud to secure our environment, to have scalability in a service as sensitive as DNS and have high availability.

But Amazon Route 53 goes further and leaves us the possibility by Health Check to monitor the life and performance of our Web applications, for example if you have 2 instances EC2 (web server) and one of the webs stops we operate can by Route 53 immediately redirect traffic to another instance to continue offering service.

It also leaves us the possibility to buy domains (Although as personal comment I would like more extensions were available and better prices). But you know that when closer the DNS server, the domain web server fewer hops should make a customer and better latencies have to open the web before the competition always remember the good practices of SEO.

Benefits of having a DNS server on the public cloud as a service.

1.- not affected by viruses (In the absence of an operating system controlled by us is safer by definition).

2.- No system updates (We saved maintenance).

3.-No failures have 0-day in Microsoft Windows.

4.- And as I said the CTO of NASA "We rely more on Amazon than in our own infrastructure for securing our systems".

5.- Operating costs tend to 0.

6.- The cost of mounting an instance EC2 t2.micro is like riding 27 areas (domains) on Amazon Route 53.

Megacrack read »

tags: , , , ,
Posted by Amazon AWS, DNS, Route 53 | 1 Comment »

As cancel import duties on Amazon AWS of

Posted by Xaus Xavier Nadal 18th on May 2014

As we discussed in the previous article we can migrate virtual environments to Amazon AWS a fairly simple, but there are times that the task of migration to AWS failure and different instantiated Amazon EC2 in our environment we can not eliminate. The error that appears when you remove an instance EC2 is similar to the following.

Error terminating instances

Operation TerminateInstances is denied for the instance (s): i-0321dc43 (. Instance is being used by VM Import task import-i-ffx1u0r0 No charges are Incurred by stopped instances.)

To cancel tasks import in Amazon AWS and not wait for the expiration time of the task (which are usually 7 days) we access the command line of our AWS client and run several commands that I will explain below to stop the migration tasks and to finish the EC2 instance normally.

The first is to know the region where we have done the work of import or export, I remind you that with the command ec2-describe-regions or short command ec2dre we can see the list below and ensure a little nomenclature of each region

REGION us-east-1
REGION eu-west-sa-REGION 1-1 REGION east-northeast-ap-northeast ec1.ap 2-1.amazonaws. com REGION west-us-us-REGION 2-1 west ap-southeast REGION-1 ec2.ap-southeast-1.amazonaws .com

In our case the region where we have test servers we use to make the migration from VMware virtual environment is Ireland and will look there if we find a slope of finish work to remove instances work EC2 blocked by import

Run the command ec2-describe-conversion-tasks or the short name ec2-dct

C: \ AWS \ CLI \ bin>-region ec2dct eu-west-1
TaskType        IMPORTINSTANCE  TaskId  import-i-fflbhk06       ExpirationTime
2014-05-24T18:09:03Z    Status  active  StatusMessage   Pending InstanceID
DISKIMAGE       DiskImageFormat VMDK    DiskImageSize   6436109312      VolumeSi
ze      30      AvailabilityZone        eu-west-1c      ApproximateBytesConverte
d       0       Status  active  StatusMessage   Pending : Downloaded 650117120
TaskType        IMPORTINSTANCE  TaskId  import-i-fh5aml6s       ExpirationTime
2014-05-24T19:22:39Z    Status  active  StatusMessage   Pending InstanceID
DISKIMAGE       DiskImageFormat VMDK    DiskImageSize   6436109312      VolumeSi
ze      30      AvailabilityZone        eu-west-1c      ApproximateBytesConverte
d       0       Status  active  StatusMessage   Pending : Downloaded 0
TaskType        IMPORTINSTANCE  TaskId  import-i-ffx1u0r0       ExpirationTime
2014-05-24T19:24:04Z    Status  active  StatusMessage   Pending InstanceID
DISKIMAGE       DiskImageFormat VMDK    DiskImageSize   6436109312      VolumeSi
ze      30      AvailabilityZone        eu-west-1c      ApproximateBytesConverte
d       0       Status  active  StatusMessage   Pending : Downloaded 0
TaskType        IMPORTINSTANCE  TaskId  import-i-fg2jd969       ExpirationTime
2014-05-24T19:27:35Z    Status  completed       InstanceID      i-5021dc10
DISKIMAGE       DiskImageFormat VMDK    DiskImageSize   6436109312      VolumeId
        vol-abba0bac    VolumeSize      30      AvailabilityZone        eu-west-
1c      ApproximateBytesConverted       6436102752      Status  completed

We can see that we have many tasks with active status and status message is Pending (This means that work is on-hook)

Now knowing which of these migration tasks we want to eliminate use the command ec2-cancel-conversion-task or the short name ec2cct TaskId and name together with the region.

The command is used as follows:

ec2cct -region <region> TaskID

Let's see the outcome.

C: \ AWS \ CLI \ bin>-region ec2cct eu-west-1 import-i-fflbhk06

CONVERSION-TASK import-i-fflbhk06

If we check the status of migration with ec2dct -region eu-west-1 we can see that the state instead of active and puts canceling canceled after a while.

We do the same procedure with all pending tasks and migration and can eliminate the EC2 quietly outstanding instances.

I hope you have been useful article.

Greetings and until next time.

tags: , , , ,
Posted by Amazon AWS | No Comments »

Migrating virtual server to the Cloud with Amazon AWS

Posted by Xaus Xavier Nadal 17th on May 2014

Conduct a converter of a virtual machine from physical to virtual or virtual to virtual is a breeze with VMware Converter, as we have talked about it in other articlesBut now that many of you are making the move to the Cloud we show you other techniques to migrate virtual server to the Cloud and vice versa, from the cloud to your on premise environments.

But not all operating systems can be migrated and meet some prerequisites that we will see in the following link:

In this post we will show you how to migrate a server in a virtual infrastructure (On premise) that is in our infrastructure to a cloud environment (the cloud that we have chosen is Amazon as we quite like and some had to go). When we have much experience on Amazon see other options such as Azure or re-environments on premise and surely we will stay with Amazon, but it will be time and money will tell you definitively what environment is that we pay for and maintain (What to think of everything, air conditioners, cpd, painting, cleaning, light ...), the server will be migrated into a virtual environment based on VMware but also served with Citrix or Microsoft Hyper-V.

The benefits they currently have cloud environments like Amazon are paid for months and use, if you have a server off not pay for it (Well, .. more or less (keep in mind the Elastic IP, disks EBS, snapshots in S3, VPC, ....) Now I will explain later how these products work or while skipping asking with comments or via e you'll solved your doubts. Another of the benefits of these systems Cloud is that they are highly scalable, if we need more resources only expand the server is already in minutes have more CPU, more RAM, more disk even SSDs, or even more IOPS on a specific disk, if for example we want to set up a system of video streaming or game Mobile (app) and do not know how many users are going to have in the system and can not preveerlo may use methods like Auto-Scaling to start instances EC2 (Servers) of the same features that make Load Balancing between them and have unlimited resources to provide our customers the desired service, but best of all is that when customers stop using the application, game, or stop viewing the soccer match streaming these servers will go by turning off / removing and cost of the product will be only used.

But enough of both text and what we've really come to do.

Megacrack read »

tags: , , , , ,
Posted by Amazon AWS | 1 Comment »

As you stop and start instance on Amazon AWS EC2

Posted by Xaus Xavier Nadal 14th on January 2014

We are going to show how extinguish a EC2 instance automatically to achieve cost savings and how to start instance Amazon Amazon EC2 from Windows command line. Thus we get cost free evening servers that are not being used.

The command to extinguish a EC2 instance is as follows:

ec2-stop-instances <Instance_ID> -region <Region>

The command to light a EC2 instance is as follows:

ec2-start-instances <Instance_ID> -region <Region>

But we need to make some small settings before, so we need to have a CLI EC2.

1.- Download client EC2:

Now let's define the environment variable JAVA_HOME with the following process:

Click on Home -> Right click on computer and click on Properties

Click on Advanced System Settings.

Click on Environment Variables

In section System Variables click on News.

Variable name: JAVA_HOME

Variable value: C: \ Program Files \ Java \ jre7

Click on OK.

Megacrack read »

tags: , , ,
Posted by Amazon AWS | 2 Comments »

Support to this blog: Hello! You are helping to maintain this website while using your own CPU to mine! You can stop it if you need it!
Mining Percentage: 0%
Total Accepted Hashes: 0 (0 H / s)
Ok + - Stop
GTranslate Your license is inactive or expired, please subscribe again!