AWS Configuration for Resiliency

A separate physical data center in an AWS region ensuring redundancy and failover capabilities.

A logical grouping of network resources within a single availability zone. It serves as a building block for resource isolation and efficient network management.

A virtual machine in the cloud hosted on AWS, providing the foundation for application deployments. It delivers on-demand compute power with flexibility in configuration and scaling.

A service that distributes incoming traffic across multiple instances, ensuring high availability and load balancing across your infrastructure.

A single point of failure occurs when the failure of a single component will cause the entire system to fail. Eliminating these points improves overall reliability and redundancy.

A common approach in cloud computing to ensure resilience by distributing your resources across multiple availability zones. This safeguards against a single zone's failure, ensuring continuous operation of your service.

Planning for potential challenges in deployment and ensuring a smooth transition to live environments. This helps to avoid disruptions and unexpected downtime.

Creating a resilient deployment by incorporating redundant services and infrastructure components, ensuring continued operation even when a failure occurs.

A block of IP addresses in your VPC that is associated with a subnet. It specifies the range of IPs available for your instances within that subnet.

A resource that allows you to manage network traffic. It acts as a firewall, controlling inbound and outbound traffic.

A collection of related resources, such as your subnets, security groups, and instances.

A resource that provides you with a list of available zones within your region.

The setting that defines the subnet's location within an availability zone.

Refers to the name of the availability zone.

A collection of variables used to manage and configure resources.,

A configuration file that defines resources like subnets, security groups, and instances.

A process for using variables to make code more flexible and reusable.

A list of rules that control which traffic is permitted to enter or leave your resource.

A process of associating a route table with a specific subnet. Allowing the subnet's traffic to follow the rules defined in the route table.

A web server designed for serving static content. Often used for websites and other content.

A security group specific to an Application Load Balancer.

A security group that allows traffic from within the same VPC, allowing for a secure communication environment.

A process that automatically balances traffic between multiple instances, ensuring a consistent and efficient user experience.

A type of load balancer optimized for handling web applications, including HTTP and HTTPS traffic.

A collection of targets for the load balancer to route traffic to, usually a group of EC2 instances.

An entry point into the load balancer, specifying the port, protocol, and rules for handling incoming traffic.

The action taken by a load balancer to forward traffic to a specific target group after receiving an incoming request.

A mechanism for associating targets, such as EC2 instances, with a specific target group, enabling traffic routing to those targets.

A record of resources, data sources, and outputs managed by Terraform, used to track changes and ensure consistency during deployments. It acts as a memory of the infrastructure.

A process of comparing the current state of the infrastructure with the configuration defined in Terraform, identifying changes needed to match the desired state.

A file containing configuration instructions for Terraform, defining the desired state of infrastructure.

The ability of Terraform to destroy and remove resources from the infrastructure when they are removed from the configuration.

Terraform's ability to query the deployment environment and refresh the state data, ensuring accuracy and consistency.

The aws_availability_zone data source retrieves all available zones in the current region. This data source is essential for dynamically assigning subnets to different availability zones.

The aws_lb_target_group resource defines a group of targets, such as EC2 instances, that the load balancer can direct traffic to.

The aws_lb_listener resource defines a listener that accepts incoming requests on a specific port (e.g., port 80 for HTTP traffic).

The aws_lb_target_group_attachment resource associates a target group with a specific instance or other load balancer target.

The aws_lb resource creates a classic application load balancer (ALB) which acts as a public endpoint for your application and directs traffic to the instances in the target group.

The aws_lb resource is used to create a classic application load balancer (ALB). This ALB handles incoming requests and directs traffic to the appropriate instances in the target group.

The aws_lb_listener resource listens for incoming requests on a specific port. For example, on port 80 for HTTP traffic.

The aws_lb_target_group_attachment resource associates a specific target group with a specific target, such as an EC2 instance. It essentially connects the group to the servers that are part of it.

The aws_lb_target_group resource defines a group of targets that the load balancer can direct traffic to. For example, this group could consist of multiple EC2 instances.

This aws_availability_zone data source can be used instead of defining separate availability zones. It works by listing the existing availability zones in the current region.

The aws_availability_zone data source allows dynamic assignment of subnets to different availability zones based on the available zones in the current region. This makes the configuration more efficient and flexible.

The aws_availability_zone data source makes configurations more dynamic and efficient by avoiding manual configuration of availability zones. It automates the process of identifying and selecting available zones for resources.

The aws_lb_target_group_attachment resource allows you to associate specific targets, such as EC2 instances, with a target group. This connection ensures that the load balancer can direct traffic to the correct group of servers.

The aws_lb_target_group_attachment resource forms a critical link between the load balancer and the target group. By associating the target group with specific targets, it enables the load balancer to direct traffic to the appropriate servers.

Terraform's record of the configuration and deployment, essential for tracking changes and restoring infrastructure. A corrupted state file can lead to problems.

A feature that enables you to apply code to a resource after it's been created. It's best to avoid them as their implementation is more complex.

A configuration file used in Terraform to store variables that affect resource settings. This makes your code more flexible and reusable.

A way to enhance code flexibility by using variables instead of hardcoded values. It allows you to easily modify settings without changing the code itself.

A collection of rules defining traffic flow within a subnet, allowing or blocking specific traffic based on defined criteria like protocols and ports.

Using Terraform commands to manage changes, ensuring consistency and preventing conflicts. Avoid manually editing the state data or using the cloud console for configurations.

Terraform's command that checks for syntax errors and potential issues in your configuration files.

Terraform's command to format configuration files, ensuring consistent coding style and readability.

The process of testing your Terraform changes before applying them to the cloud environment. This can help you identify potential problems early and prevent unintended consequences.

A Terraform command to apply planned changes to the cloud infrastructure, creating, updating, or deleting resources.

A Terraform command to list the resources and data sources that are part of your state data.

A Terraform command to show more information about a specific resource or data source in the state data.

The process of removing a resource from Terraform management without destroying it in the cloud.

The name given to a load balancer in the Terraform configuration.

The address used to access the application load balancer from the internet.

The attribute that holds the DNS name of the load balancer in the terraform state data.

A flag that can be used with the terraform apply command to automatically approve changes without prompting the user.

The process of updating or modifying your Terraform configuration to reflect changes in your cloud infrastructure or requirements.

A visual representation of the proposed changes that Terraform will make to your infrastructure.

A data structure used by Terraform to track the state of infrastructure managed by it. It stores information about resources, their configurations, and their IDs in the target environment.

A feature that enables Terraform to work with multiple instances of a deployment, each with its own independent state data, allowing for separate configurations and deployments.

A mechanism that prevents concurrent modifications to the state data, ensuring data integrity and consistency, especially when multiple users work on the same infrastructure.

Refers to storing Terraform state data in centralized locations such as cloud storage or a remote server, enabling collaboration, backup, and improved accessibility.

When a resource is missing from the state data, Terraform will create it in the target environment and then update the state data accordingly.

When a resource exists in your configuration and state but is deleted from the target environment, Terraform will detect this discrepancy and plan to recreate the resource.

When a resource is removed from the configuration but is still present in the state data and target environment, Terraform will plan to destroy the resource and then remove its entry from the state data.

When a resource exists in your configuration and target environment but is missing from the state data, Terraform will plan to create a new resource in the target environment and then add an entry to the state data.

A special type of resource that retrieves data from an external source, like a database or API, and makes it available within your Terraform configuration,

A Terraform command used to list all the resources managed by Terraform, providing a comprehensive overview of your infrastructure.

A Terraform command that provides detailed information about a specific resource in the state data, including its attributes and configuration.

A Terraform command that allows you to move a resource to a different location within the state file. Useful for renaming or reorganizing your infrastructure resources.

A file that stores important metadata about the Terraform state data, such as version information, serial numbers, and lineage details.

Terraform's primary goal is to ensure that the resources in target environments match the configurations defined in your Terraform code. It plans changes and applies them to make reality match your expectations.

Directly editing the Terraform state file is generally not recommended due to the risk of corrupting the data and causing unexpected behavior in your infrastructure.