Questions tagged with Pricing
Content language: English
Sort by most recent
Do GSI not projected attributes use WRU?
I'm new to AWS and NoSQL/DynamoDB. I was wondering if having a GSI with projection type KEYS_ONLY whould use WRU or incur in extra cost when modifying non-key attributes in the original table. For example if a table with PK "id" and GSI-PK "email" would get extra WRU used or cost added when modifying the attribute "city" in the original table. Thank you in advance.
How much for manual snapshot RDS?
Hello everybody, Example: - I have RDS MySQL allocate 20GB. - I will need manually snapshot manual RDS 4 times / 1 month. Will the price of manual snapshot RDS be 20 * $0.095(Region Tokyo) for each time? Or manual snapshot RDS is 20 * $0.095(Region Tokyo) for the first time. Subsequence time, How much will I price pay? I have researched on document RDS Pricing but I don't understand it. Please help me explain the price of Manual snapshot RDS MySQL. Thank everybody.
AWS Amplify Cognito Pricing: What is a sync operation
At the bottom of this page: https://aws.amazon.com/cognito/pricing/, a "sync operation" is mentioned. Questions: 1. What is the exact definition of a "sync operation"? 2. Whenever I update/read the attributes of a user, does that count as a sync operation?
Elasticache vertical scale up strange behaviour
Hi community! In my application, ElastiCache (Cluster mode disabled) is used in two scenarios, daily: 1. Intense usage, for about 3 hours, in which we need an improved network performance, and is run with cache.m6g.2xlarge 2. Light usage, for the rest of the day, in which a cache.m6g.large would be more than enough. We now use the 2xlarge 24/7, but would be nice to be able to vertically scale up and down during the intensive hours. However, when we do a scale up (large ⇾ 2xlarge) right before the heavy process, the behavior of the instance is not the same if we don't scale (keep 2xlarge for the whole day). Just for comparison, the first graph shows the Network Bytes In when there is a scale up right before the process, and the same metric when there isn't: ![With scale up, from cache.m6g.large to cache.m6g.2xlarge, reaching a max of 13Gb per minute](/media/postImages/original/IMox_zRCrAQyqlKEXGQo_Ixg) With scale up, from cache.m6g.large to cache.m6g.2xlarge, reaching a max of 13Gb per minute ![No scale up, instance cache.m6g.2xlarge reaches a max of 24Gb per minute](/media/postImages/original/IMkONubqtMS2SW_dQK_FAOAQ) No scale up, reaches a max of 24Gb per minute Note that the cache process only starts after the cluster Status is set to available. This drop in the Network Bytes In rate shouldn't be happening, and it is making the scale option to be impracticable to us. What is the point in giving an online scaling feature that does not work as it should after the scaling? Has anyone experienced something similar, and do you know of any alternatives to accomplish our goal, to provide performance only during the cache hours, keeping our costs reasonable? Thanks.
Service for storing frequently changing bitmap
I have a problem where I have a bitmap that is displayed to users on a webpage, each user can change the colour of a singular pixel. I intially thought about using S3 to store the bitmap and then using a lambda to get the bitmap, update one pixel and override the pervious bitmap, but it seems this will generate a pretty large cost due to lots of PATCH/PUT's. The updates to the bitmap will be streamed to each client (not the entire bitmap, just the pixel location and new colour) The bitmap will be read everytime the user loads the page to display the current state, and it **must** be the most recent version (will be a bit of a mess if the clients get all out of sync). I thought about putting this data into a DynamoDB but then its pretty expensive to retrieve all of the pixels and generate a bitmap (bitmap is 128x160 which makes for 20,480 entries!) Is there a service that I am overlooking (*highly likely)* that fits this need pretty well ***TLDR***: Is there a service that is good (cost wise) for frequently (max 10 times per second) changing files
Get spot instance cost by costExplorer get-cost-and-usage cli
I created a spot instance, and after a day, I use costExplorer get-cost-and-usage to get real cost of this instance. But I got the cost is the same with on demand pricing. I'm starting to doubt my instance is spot or not. I can see my instance "Lifecycle" is "Spot" in ec2 console. And I can see this instance in "Spot Requests" list. If we confirm the instance is spot, so my question is whether costExplorer api can get spot instance cost and how to get it? Thanks, Mingtong
Upgrading RDS SQL Server from db_m4 to db_m5, but worth it?
Hi Friends, I'm considering moving from RDS SQL Server databases DB.m4 to DB.m5, but I do not have a clear idea of what to expect when I push the button. Could you please advise me on what to expect If I remain in DB.m4 machines? What am I missing? Thank you, Best Regards,
Calculation for Compute Savings Plan
Hi, question about Compute Savings Plan calculation: I try to come up with some numbers and I'm not sure if I'm doing this right, so it would be great if someone could confirm. Let's say for example I have m5.xlarge instances that are all on-demand, and I pay currently $3000 per month for them. I'd like to purchase a Compute Savings Plan, 3 years, no upfront for them and commit $1 per hour. According to https://aws.amazon.com/savingsplans/compute-pricing/ m5.xlarge has 40% savings over on-demand for that. On-Demand cost 3 years: $3000 * 36 = $108000 Commit $1: $1 * 24 * 30.5 * 36 = $26352 $108000 * 0.6 = $64800 $64800 - $26352 = $38448 $38448 * (10/6) = $64080 $64080 + $26352 = $90432 Meaning over 3 years, I pay $90432 instead of $108000, because the m5.xlarge instances are billed with only 60% of their on-demand cost until my committed $1/h is used up. Is that correct or did I misunderstand how that's supposed to work? Thanks, Marc
Device Farm: Run stuck on a pending/stopping device forever
I started two runs on the Google Pixel 6 Pro (Unlocked) device and I had to stop them, I mean, I clicked on the "Stop run" button in the AWS Device Farm console. To my surprise, after many minutes without changing the status, both runs are still "Stopping". One of these devices finished the tests correctly but was unable to Tear Down and finish, so I had to hit "Stop Job" but even so, it is still "Pending". Can anyone help me? What is the implication of this platform failure on my minutes billing?
Comprehend Endpoint Pricing - Clarification
The comprehend end point pricing says it is based on the active seconds. [https://aws.amazon.com/comprehend/pricing/]() > "Endpoints are billed on one second increments, with a minimum of 60 seconds. Charges will continue to incur from the time you start the endpoint until it is deleted even if no documents are analyzed." Is it something like I create the end point now and i didn't use it for 1 day. Will it billed for 24 * 60 * 60 * 0.0005 = 43.2$/day, even though i didn't used it for analysis ? This cost seems to be very high, is my understanding correct ? Can someone clarify the "active" part in the pricing statement ? Thank you.
Monthly SMS Volume for Toll-Free Number Registration
I'm in the process of registering a toll-free number. What impact does the estimated number of SMS messages sent each month have on the bill? Is there a chart showing how much it costs per message for, say, 10,000 messages per month versus 1,000 per month? Also, can I change the estimated monthly volume later?