Unanswered Questions tagged with Pricing
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
Amazon GameLift now supports support for AWS Local Zones
Hello GameLift Devs, Today, the GameLift team is excited to announce the general availability of AWS Local Zones. With this update, you can seamlessly provide gameplay experiences across 8 new AWS Local Zones in Chicago, Houston, Dallas, Kansas City, Denver, Atlanta, Los Angeles, and Phoenix. Along with the updated support for Local Zones, we are adding new instance types specifically supported in the various Local Zone Regions, including C5d and R5d instance types. Additionally we are adding support for the next generation [C6a](https://aws.amazon.com/ec2/instance-types/c6a/) and [C6i](https://aws.amazon.com/ec2/instance-types/c6i/) instance types. Amazon EC2 C6i instances are powered by 3rd Generation Intel Xeon Scalable processors and deliver up to 15% better price performance compared to C5 instances for a wide variety of workloads and are ideal for highly scalable multiplayer games. You can find updated pricing on the [GameLift pricing page](https://aws.amazon.com/gamelift/pricing/) as well as in the [AWS Pricing Calculator](https://calculator.aws/#/addService/GameLift). For more information, please refer to our [Release Notes](https://docs.aws.amazon.com/gamelift/latest/developerguide/release-notes.html#release-notes-summary) and [What’s New post](https://aws.amazon.com/about-aws/whats-new/2022/08/amazon-gamelift-supports-aws-local-zones/). Mark Choi, GameLift PM
Which Opensearch instance type to choose for a new webapplication with little data?
Amazon recommends running an opensearch domain that contains 3 regular nodes and 3 master nodes distributed accross 3 AZ zones. The lowest instance type that is still suitable for a production environment is the `t3 medium.search` instance type. I've run this setup for about 1.5 days, using `t3 small.search` instead of `medium`. When i looked at the bill afterwards i could see that running such an instance for merely 1.5 days already costs 9 dollars. That's way too expensive for me. According to the [amazon cost calculator](https://calculator.aws/#/addService/OpenSearchService) the monthly cost for this setup would have been well over 350 dollars. My web application will use the open search server only for serving autocomplete suggestions and finding documents whose coordinates reside within a certain geographical area. When the webapplicatoin is launched the open search server will start out with only 5 indexes containing only a small number of documents, no more then 200 mb in total. Of these only one index is used to preform geospatial queries on. I don't think i need a t3 medium instance for this. So my question is: With what kind of open search instance can i start out with? The setup needs to be economical because it will take a while before my web application starts making money. I was thinking about setting up a `t2 micro.search` domain service with 2 micro master instances and 2 micro worker instances. That would cost me about 50 dollars a month in total. Could this be a good setup to start with? If so then i would like to know how i can setup a domain that uses `t2 micro.search` instances. When i go to the domain creation page in my aws console i'm not able to select `t2 micro.search` from the instance type list. The smallest i can select is `t3 small.search` but thats already too expensive for me because i want to run nodes in atleast two availability zones. I could opt for running only one `t3 small.search` master node and one worker node, which would cost 50 dollars a month as well, but then the domain service is no longer highly available. If the availability zone it sits in crashes then i can't serve autocomplete suggestions anymore, nor can i return documents based on their coordinates. I'd love to hear your opinions on this. Thank you
AWS Spot Pricing Specifics
Hi, for my purposes I am using AWS Batch with EC2 spot to run multiple jobs created every 15 minutes with each lasting ~2-10 seconds for computation. From my understanding AWS Batch creates an instance for each job, where Spot prices a minimum of one minute's charge for each, although I am uncertain of the exact instance type chosen by the "optimal" selection's logic with best-fit. As a result of my low duration workload, I was planning to create a load-balancing system that combines jobs (Each is calculated independently and are not easily multi-processed) before submitting them to AWS Batch, choosing a specific instance type instead of the "optimal" selection to reach the 1 minute time for a given instance consistently to avoid wasted time (However I still want the work to be computed in parallel over multiple instances whenever otherwise possible). I was wondering if there were any faults in my understand of AWS Batch and Spot above, perhaps where AWS Batch packages the jobs similarly to how I was planning?
codecommit pricing question (multiple roles for each IAM User)
my client has around 400 repositories, there are 2 roles for each repository (so around 800 roles), the client has 700 users (so 700 IAM users) that access these repos, on average each user access around 7-8 repos, so each user reach these repos with around 15 different roles. it's unclear to me how the pricing apply.. is my client going to pay for 700 users, or is going to pay for 700 users * 15 average roles = 10,500 ?? thanks.