3 Steps To Meeting Your Data Residency Requirements

Organizations around the world must keep data in a particular location for legal, regulatory, contractual or policy requirements. Data residency requirements are paramount to staying compliant and AWS provides edge infrastructure and services that move data processing and analysis as close to the end-point as necessary. Whatever your data residency need, it’s covered by AWS at the Edge, including a hybrid solution, AWS Outposts. 

Read on to discover: 

  • What drives the need for data residency 
  • How to define your data residency requirements and meet security demands 
  • How AWS Outposts can meet your data residency challenges 

Three main data residency drivers

Regulatory requirements: Some businesses and public sector bodies must store or process data in a particular geographical location, to comply with legislative or regulatory demands. 

Contractual requirements: Organizations may have contractual agreements with their customers that require data to be stored or processed in a specific geographical location. 

Corporate policies: Businesses or government organizations might specify that certain data must be stored or processed in a specified location. 

How AWS Outposts meets your data residency needs

Outposts enables you to meet your data residency requirements, while benefiting from AWS services, even in locations where’s there’s no AWS Region. 

Outposts also unlocks many other advantages, including: 

  • Reduced maintenance and management costs, compared to running your own technology. 
  • Consistent experience for developers and operations teams across cloud and on-premises. 
  • AWS-grade security controls, including continuous monitoring and protection with AWS Nitro, plus encryption. 
  • Process workloads locally and keep your sensitive customer data on premises. 

Determining your own data residency requirements

Every organization’s obligations are different, but will either be segmented into personal information (financial, medical etc), or for reasons of national security (critical infrastructure and data in a transportation, utilities or military sense). 

When it comes to securing that data some organizations cite better security as a reason for imposing data residency restrictions. In reality, the physical location of data doesn’t protect against most attacks, since many are carried out over the internet. AWS has a robust set of security infrastructure and services that enable organizations to safeguard their data in the cloud.  

How AWS Outposts addresses local compute, storage and networking needs

Local compute: The AWS Outposts catalog includes options supporting the latest-generation Intel® Xeon® Scalable-powered EC2 instance types, with or without local instance storage. 

Local storage: As well as local instance storage, your organization can store data using either Amazon EBS or S3 within an Outposts environment, giving you the ability to choose where you want data to be kept. 

Local network gateway: Each Outpost provides a new local gateway (LGW), to connect Outpost resources with on-premises networks. LGW enables low-latency connectivity between the Outpost and any local data sources, end users, local machinery and equipment, or local databases — so there’s no need to go via the Region. 

Discover more about AWS Outposts

Discover more about AWS Outposts and data residency requirements, including sector use cases where data residency plays a significant role, in our infographic here.

Source Article