Tag: AWS Transit Gateway

In this post, we explore the complexities of data privacy and controls on Amazon Web Services (AWS), examine how creating a landing zone within which to contain such data is important, and highlight the differences between creating a landing zone from scratch compared with using the AWS Landing Zone Accelerator (LZA) for Healthcare. To aid explanation, we use a simple healthcare workload as an example. We also explain how LZA for Healthcare codifies HIPAA controls and AWS Security Best Practices to accelerate the creation of an environment to run protective health information workloads in AWS.

AWS GovCloud (US) was architected to have isolation (both physically and logically) from other AWS partitions for compliance. For this reason, AWS services, used to privately interconnect virtual private cloud (VPC) hosted resources within the same partition like AWS PrivateLink, Amazon Virtual Private Cloud (Amazon VPC) peering, or AWS Transit Gateway peering, cannot span from AWS GovCloud (US) to commercial Regions natively by design. In this post, we will highlight four connectivity patterns customers can use to interconnect VPC hosted systems cross partition.

Government agencies and public sector organizations in energy and utilities rely on smart solutions to detect, locate, and fix utilities outages faster based on input from their customer contact centers and field crews. One popular outage management solution (OMS) is Schneider Electric’s ArcFM Responder (Responder) OMS. In this post, we discuss how to deploy the Schneider Electric’s Responder environment on AWS.

Public sector customers have been using Amazon Web Services (AWS) within their hybrid cloud environments since AWS was born in 2006. Most customers have resources on-premises, engaging in multi-year journeys of cloud adoption. Often they are seeking to improve connectivity for migration, cloud bursting, backup and disaster recovery, or leveraging cloud-native technologies from on-premises.