Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I signed up for Amazon AWS's Free Tier instance. Everything works fine so far, but I'm a bit confused how to make sure I won't have to pay for it.
Specifically, I've been billed a bit for "Elastic IP address not attached to a running instance per hour on a pro rata basis".
In the Management Console > Elastic IPs section, I have allocated a new Elastic IP and attached it to my instance. It seems that I can allocate 4 more addresses, but not attach them, this is only possible for one instance. How do I avoid being billed for unattached Elastic IPs? Is there even a way, if I have 5 Elastic IPs assigned to my account, but only have one instance?
I'm also not sure how the traffic usage reports work - I think I'm allowed "*15 GB of bandwidth out aggregated across all AWS services", but only if I use the Public DNS and not the Elastic IP. Is this correct?
Thank you!
Since Amazon has only limited number of IP addresses available, they charge for every unattached Elastic IP address. It's protection against subscribers who allocate limited resources without using them, because they're free.
Conclusion: Allocate elastic IP addresses only for running instances, or accept that you are being billed (the charge is quite reasonable).
You can release addresses you don't need in EC2 Management Console.
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I launched a t1.micro instance running Apache and MySQL servers on Ubuntu. Basically I'm using it to host my photo sharing app that may have huge random spikes in terms of visitors.
How does AWS go about it?
Will the instance automatically upgrade to appropriate horse power to keep up with demand and growing storage demands?
No, you have to manually make your instance more powerful by first making sure it is in the stopped state (this requires EBS volumes or you'll lose your data), then going to the AWS console, right click your instance and select 'Change Instance Type'.
If you are interested in a more automated approach, I suggest an Elastic Load Balancer with an Auto-scaling policy. With Auto-scaling, Amazon will spin up or down new instances based on set points that you provide (i.e. CPU usage reaches 80% for 10 minutes).
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
My portal will be mainly accessed in India and it involves uploading/viewing of images which means good data transfer will be involved.
If I host my portal on servers located in India; surely it will be faster to access the pages. But I want to personally use Amazon web services. Do we have option in Amazon so that we can host our tomcat server and save images on some servers located in India ; or at max. in Singapore so that access is fairly faster.
Amazon Web Services offers several AWS datacenter Regions for most of their Products & Services within their steadily expanding global infrastructure, amongst those the Asia Pacific (Singapore) Region (usually referred to as ap-southeast-1).
Furthermore they do offer even more so called edge locations for Amazon CloudFront, which is their Content delivery network (CDN) alike web service for content delivery.
You can see an overview of the current regions and edge locations on their Global Infrastructure map.
There is an API oriented Regions and Endpoints listing as well, see e.g. those for the Amazon Elastic Compute Cloud (EC2) (please note that not every region does necessarily support every single available product, especially beta offerings are usually available in us-east-1 only initially).
Consequently you should be fine using ap-southeast-1 for your use case, though as usual you might want to give it a try before settling on this, which is fairly easy to do by means of the AWS Free Usage Tier offering.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Using Ejabberd in EC2 as an XMPP server to send real-time information to clients...
How it is possible to set up clustering so that if the load on the server gets too much, Auto Scaling will create a new EC2 instance that is part of the Ejabberd cluster?
The documentation I've read suggests that you must already have the machines and manually configure each new one to be added to the cluster. Surely though you don't have to be running redundant EC2 instances just in case?
You'll need to do this manually, however a single ejabberd server can handle quite a lot of traffic. Each server adds a significant amount of available connections to your cluster, so it's not a common task.
That said, I'd really be careful running ejabberd in EC2. I've been doing it for about a year, and we fight mnesia network partitioning pretty regularly. Clustered ejabberd servers don't work very reliably in the EC2 network.
I am installing an infrastructure based on EC2 + ejabberd and have read this post. Do not you recommend? I planned to use as backend mysqlk (in AWS RDS) for tables that store large amounts of data. What do you think?
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I am not sure I understand the prices for EC2 instances.
Amazon writes:
Pricing is per instance-hour consumed for each instance, from the time an instance is launched until it is terminated.
So I will get billed for 100% a month, unless I terminate this instance completely and lose all the data on the instance-store? This confuses me, as the Amazon cloud is said to be a cheaper alternative. But for a Large instance I end up with about $250/month, which is quite expensive compared to other, non-cloud companies.
you will be billed 24 instance-hours per day if your instance (server) is online 24/7.
This is exactly the same as Windows Azure Web instances.
The be billed just for what I use, it's more about Files and Database, as the server should be always up and running.
If you compare VPS hosting companies with this prices, you will see Amazon/Windows are cheaper, keep in mind that you will have remote access to that server no matter what OS you are using (windows or Linux distro).
You can stop your instance can keep it's volumes. In that case you pay only for the storage while the instance is not running.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
we have a large ec2 instance running in asia pacific region.we want to reserve that particular instance.In aws management console we see an option to purchase a reserved instance but there seems to be no option to change this instance into a reserved one.Are we missing out on something
Reserved instances are a billing feature, not a technical feature.
You can purchase a reserved instance and the discounted hourly rate will apply to already-running instances, without needing to do anything to them.
Just make sure the reserved instances you purchase are:
- in the same availability zone as your already-running instances
- of the same instance type (m1.small, c1.medium, etc) as your already-running instances.
As soon as the reservation cost clears your credit card you will see the discounted hourly rate take effect for your already-running instances.
Amazon's docs could be a lot clearer on this.
http://aws.amazon.com/ec2/reserved-instances/#4
The AWS's official docs state that the availability zone must be the same. The region is, for example, us-east-1. The AZ is us-east-1a. So, according to AWS, it has to be specific to the last letter.
However, some clever folks found a potential work-around that uses EC2 Consolidated Billing and combines the (odd?) feature that one's us-east-1a might be another us-east-1c (I guess the idea there is to enforce some homogeneity around the AZs).