I have reached the maximum number of instance in US-EAST region, Will it cost more If I put my resource in another region?
You can request to have the limit increased here:
http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
You can also use the AWS Simple Monthly Calculator costs in different regions:
https://calculator.s3.amazonaws.com/index.html
Related
I was trying to estimate AWS lambda using AWS pricing calculator, but I am confused.
If I estimate Provisioned concurrency section than is Service settings section mandatory to estimate ?
If your Lambda functions exceed the provisioned concurrency, the excess executions will be charged at the normal rate (ie. the rates shown in the Service settings section). You don't need estimations in both sections if you plan to keep everything within your provisioned concurrency limits. However if you only provision at a certain baseline and your function is expected to scale beyond that, your estimate should include the excess executions in the Service settings section.
I've been combing through my AWS bills and noticed something strange - Cloudwatch bills a very small amount for every available region with a charge it lists as $0.01 per 1,000 metrics requested using GetMetricData API - Asia Pacific (Singapore) (or insert region here).
In my main region (US East) I see billing as expected - a few bucks total for PutLogEvents and GetMetricData calls, as you'd expect from normal use.
But in every other region I also have these costs - a few cents each - for GetMetricData calls in that region. Does anybody know the source of these costs?
please take a look to https://aws.amazon.com/cloudwatch/pricing/?nc1=h_ls
The Costs for GetMetricData and GetMetricWidgetImage is not applicaple for the free tier, you will have on your AWS account.
Do you deploy something in your account, which collects data from all your regions or you did not restrict the values for those metrics? E.g. if you are using 3rd party services like NewRelic, Datadog, etc. and collect those metrics, this API call is used to receive the list of all available metrics.
I have seen the term, "per account per region" at many places in AWS documentation e.g. at https://aws.amazon.com/lambda/faqs/
No. AWS Lambda is designed to run many instances of your functions in parallel. However, AWS Lambda has a default safety throttle for the number of concurrent executions per account per region (visit here for info on default safety throttle limits). You can also control the maximum concurrent executions for individual AWS Lambda functions, which you can use to reserve a subset of your account concurrency limit for critical functions, or cap traffic rates to downstream resources.
What does it mean?
My understanding is that it is the sum of accounts per region e.g. Let's say your org has three accounts in two regions and two accounts in one region, the total will be 3x2 + 2x1 = 8
Is it the correct understanding?
It effectively means that the limits are enforced in each region separately.
It is also enforced at the Account level, so limits in your account don't impact limits in my account. Same if you control multiple accounts.
Does anywhere officially or unofficially document what the true maximums are for all AWS quotas?
I am new to AWS, and am trying to figure out the maximum values for certain quotas.
For example, the default value for S3 Access Points supports a maximum of 1000 per account.
but in the AWS quota console it says it is Adjustable, and the docs suggest I can request a quota increase.
You can create a maximum of 1,000 access points per AWS account per Region. If you need more than 1,000 access points for a single account in a single Region, you can request a service quota increase. For more information about service quotas and requesting an increase, see AWS Service Quotas in the AWS General Reference.
I'd like to know what the true maximums are across the board for IAM and S3 resources, to ease design of features I'm working on, without having to do a request to increase resources I may not actually use, if appropriate resource limits can't be requested.
After discussing with AWS support, some quota changes aren't reflected in this console at this time (e.g dynamoDb quota changes)
Haven't tried it, but possibly using aws-limit-checker may show the real limits
AWS says that everything is "pay as you use". But are there any hidden costs or "NOT obvious" costs on AWS ?
Costs which generally are ignored by people and can give shock:
It is recommended that we deploy our application in Multi AZ for High availability. We assume that data transfer between these servers will be free as this is like intranet; but that is not true. There are charges ( around 10% of internet bandwidth charges ) for data transfer across AZ in same region.
Data transfer within AWS and across AWS regions is also charged.
On AWS Aurora; by default provisioned IOPS are enabled which leads to a huge bill.
If Versioning is enabled on S3; then u need to pay for all versions of every object.
These are not hidden charges but can give you a shock:
Even on other RDS; if u use provisioned IOPS it leads to a huge bill depending on usage.
I think one of the most confusing parts of AWS is the 'EC2-Other' cost category. Most of these costs are based on utilization and can get out of control quickly. I did a write up on how to break down EC2-Other here: EC2-Other Cost Breakdown