Difference between revisions of "AWS Availability Zone (AZ)"
Jump to navigation
Jump to search
| (4 intermediate revisions by 3 users not shown) | |||
| Line 17: | Line 17: | ||
* <code>[[multi_az]]</code> in [[Terraform]] <code>[[aws_db_instance]]</code> | * <code>[[multi_az]]</code> in [[Terraform]] <code>[[aws_db_instance]]</code> | ||
* [[AWS partition]] | * [[AWS partition]] | ||
| + | * <code>[[Invalid length for parameter]]</code> | ||
| + | * [[EBS]] [[replication|replicated]] within its Availability Zone | ||
| + | * [[Resilience in Amazon EKS]] | ||
| + | * [[data.]] | ||
== Activities == | == Activities == | ||
Latest revision as of 11:15, 25 October 2024
An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
aws ec2 describe-availability-zonesaws ec2 describe-instances | grep AvailabilityZoneaws rds describe-db-instances | grep MultiAZ
Related terms[edit]
- AWS region:
us-east-1d - Multi-AZ:
aws rds describe-db-instances | grep MultiAZ - Resource Groups
aws ec2 describe-subnets
- Terraform: availability zone
availability_zoneTerraformaws_instancemulti_azin Terraformaws_db_instance- AWS partition
Invalid length for parameter- EBS replicated within its Availability Zone
- Resilience in Amazon EKS
- data.
Activities[edit]
- Best practices for converting a Single-AZ Amazon RDS instance to a Multi-AZ instance: https://aws.amazon.com/blogs/database/best-practices-for-converting-a-single-az-amazon-rds-instance-to-a-multi-az-instance/
See also[edit]
Advertising:
