AWS Architecture Blog

Category: Networking & Content Delivery

One to Many: Evolving VPC Design

Since its inception, the Amazon Virtual Private Cloud (VPC) has acted as the embodiment of security and privacy for customers who are looking to run their applications in a controlled, private, secure, and isolated environment. This logically isolated space has evolved, and in its evolution has increased the avenues that customers can take to create […]

An example of submarine cable composition.. S

New Zealand Internet Connectivity to AWS

Update, August 2022: The Southern Cross Next Cable Network is now online, adding an additional network with a capacity of 72 terabits per second (tbps) to Aotearoa-New Zealand’s international connectivity. Amazon Web Services (AWS) serves more than a million private and public sector organizations all over the world from its extensive and expanding global infrastructure. Like […]

Updates to Serverless Architectural Patterns and Best Practices

September 8, 2021: Amazon Elasticsearch Service has been renamed to Amazon OpenSearch Service. See details. As we sail past the halfway point between re:Invent 2018 and re:Invent 2019, I’d like to revisit some of the recent serverless announcements we’ve made. These are all complimentary to the patterns discussed in the re:Invent architecture track’s Serverless Architectural […]

Ministry of Justice Landing Zone

Building an AWS Landing Zone from Scratch in Six Weeks

In an effort to deliver a simpler, smarter, and more unified experience on its website, the UK’s Ministry of Justice and its Lead Technical Architect, James Abley, created a bespoke AWS Landing Zone, a pre-defined template for an AWS account or infrastructure. And they did it in six weeks. Supporting 33 agencies and public bodies, […]

Migration hub

Optimizing a Lift-and-Shift for Security

This is the third and final blog within a three-part series that examines how to optimize lift-and-shift workloads. A lift-and-shift is a common approach for migrating to AWS, whereby you move a workload from on-prem with little or no modification. This third blog examines how lift-and-shift workloads can benefit from an improved security posture with […]

Cost effectiveness

Optimizing a Lift-and-Shift for Cost Effectiveness and Ease of Management

Lift-and-shift is the process of migrating a workload from on premise to AWS with little or no modification. A lift-and-shift is a common route for enterprises to move to the cloud, and can be a transitionary state to a more cloud native approach. This is the second blog post in a three-part series which investigates […]

performance

Optimizing a Lift-and-Shift for Performance

Many organizations begin their cloud journey with a lift-and-shift of applications from on-premise to AWS. This approach involves migrating software deployments with little, or no, modification. A lift-and-shift avoids a potentially expensive application rewrite but can result in a less optimal workload than a cloud native solution. For many organizations, a lift-and-shift is a transitional […]

Scale Your Web Application — One Step at a Time

I often encounter people experiencing frustration as they attempt to scale their e-commerce or WordPress site—particularly around the cost and complexity related to scaling. When I talk to customers about their scaling plans, they often mention phrases such as horizontal scaling and microservices, but usually people aren’t sure about how to dive in and effectively scale […]

Running Multiple HTTP Endpoints as a Highly Available Health Proxy

Route 53 Health Checks provide the ability to verify that endpoints are reachable and that HTTP and HTTPS endpoints successfully respond. However, there are many situations where DNS failover would be useful, but TCP, HTTP, and HTTPS health checks alone can’t sufficiently determine the health of the endpoint. In these cases, it’s possible for an […]

Doing Constant Work to Avoid Failures

Amazon Route 53’s DNS Failover feature allows fast, automatic rerouting at the DNS layer based on the health of some endpoints. Endpoints are actively monitored from multiple locations and both application or connectivity issues can trigger failover. Trust No One One of the goals in designing the DNS Failover feature was making it resilient to […]