This comment appears to misunderstand the control plane/data plane distinction of AWS. AWS does have limited access to your control plane, primarily for things like enabling your TAMs to analyze your costs or getting assistance from enterprise support teams. They absolutely do not have access to your dataplane unless you specifically grant it. The primary use case for the latter is allowing writes into your storage for things like ALB access logs to S3. If you were deep in a debug session with enterprise support they might request one-off access to something large in S3, but I would be surprised if that were to happen.

▲

resters 4 days ago | parent [-]

If that is the case why create a separate govcloud and HIPAA service?

	▲	thedougd 4 days ago \| parent \| next [-]
		HIPAA services are not separate. You only need to establish a Business Associations Addendum (BAA) with AWS and stick to HIPAA eligible services: https://aws.amazon.com/compliance/hipaa-eligible-services-re... GovCloud exists so that AWS can sell to the US government and their contractors without impacting other customers who have different or less stringent requirements.
	▲	everfrustrated 3 days ago \| parent \| prev [-]
		Product segmentation. Certain customers self-select to pay more for the same thing.