![]() Supported instance type for Aurora Multi-Master is db.r4.xlarge only. Name of the compute and memory-capacity class of the database instance. If the database instance is not in a multiple Availability Zone deployment, choose "false." Not applicable for Aurora Serverless. For descriptions of the other options, see. ![]() With provisioned databases (the default), you provision and manage the server instance sizes. To see supported Aurora features by Regions and engine versions, see. ![]() Currently Multi-Master is available only for Aurora-MySQL5.6.10a, Serverless is available only for Aurora-MySQL5.6.10a and Aurora-MySQL5.7-2.07.1. Number of days (1 to 35) that automatic database snapshots are retained. To enable automatic minor version upgrades, choose "true." Aurora Serverless supports port 3306 only.ĭatabase automatic minor version upgrades Port on which the DB instance listens for connections. Must include 1 uppercase, 1 lowercase, 1 number, 1 symbol (not / " '). To rotate the password on a schedule (every 89 days), choose "true."Īdministrator password for the database account. Database configuration Parameter label (name)Īdministrator user name for the database account. You must enable TCP forwarding to test the deployment as described in the deployment guide. To enable TCP forwarding, choose "true." This setting enables only the capability it doesn’t set up any traffic forwarding. With TCP forwarding on the bastion host, you can set up traffic forwarding to resources in private subnets. A key pair consists of a private key and a public key.Īllowed CIDR block for external SSH access. Name of the existing key pair for connecting to your EC2 instance. If you do not want to create a Linux bastion stack, choose "false." You must have a bastion host to test the deployment as described in the deployment guide. Linux bastion configuration Parameter label (name) The logical order of your selections is preserved.ĬIDR block for private subnet 1 located in Availability Zone 1.ĬIDR block for private subnet 2 located in Availability Zone 2.ĬIDR block for the public subnet 1 located in Availability Zone 1.ĬIDR block for the public subnet 2 located in Availability Zone 2. This deployment uses two Availability Zones. Network configuration Parameter label (name)Īvailability Zones to use for the subnets in the VPC. Parameters for deploying into a new VPC Table 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |