By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Availability

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Can't Modify RDS Postgres "R6i" Stand-Alone instance to Multi-AZ, Fails

I am working on some terraform to launch RDS instances. As part of this project I need to import data from another database. The recommended setup from AWS to have a FAST `pg_restore` is to launch the RDS instance in Standalone mode for the import and then modify to Mutli-AZ there after. I have done this process before in my career and the methodology does work quite well. With this project we have chosen the R6i instance types as the match quite well with where we are migrating from. How ever I feel that we have found a bug in the AWS provisioning system. If you launch an RDS Postgres `db.r6i.24xlarge` instance type in the Stand-Alone Configuration and the modify it to be Multi-AZ you get the following error in the Web Console RDS - Log & Events Tab. ``` Instance type db.r6i.24xlarge in availability zone us-east-1c is unsupported; putting database instance into available ``` We know that to be false since the Main DB launched just fine. I have tested using the AWS Web Console instead of the Terraform code and I can reproduce this. I have also found via the Web Console that you can get a Multi-AZ DB, but only if you start with that configuration. So the steps to reproduce: 1. Launch a, RDS Postgres `db.r6i.24xlarge` instance in Stand-Alone. 2. After Completion; Modify the instance to be Multi-AZ. The process with take a little over 30 min, but then you will get the above error. My question: Is this a Bug?, and how can we get past it? Update: I also Attempted the same tests in the Default VPC. In the Default both Starting as a Mutli-AZ AND Starting as a Stand-Alone and Modify failed. :-(
1
answers
0
votes
30
views
asked 11 days ago

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
0
answers
1
votes
51
views
asked a month ago

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
0
answers
0
votes
42
views
asked 2 months ago