AWS DataSync now supports virtual private cloud (VPC) endpoint policies, allowing you to control access to DataSync API operations through DataSync VPC service endpoints and Federal Information Processing Standard (FIPS) 140-3 enabled VPC service endpoints. This new feature helps organizations strengthen their security posture and meet compliance requirements when accessing DataSync API operations through VPC endpoints.
VPC endpoint policies allow you to restrict specific DataSync API actions accessed through your VPC endpoints. For example, you can control which AWS principals can access DataSync operations such as CreateTask, StartTaskExecution, or ListAgents. These policies work in conjunction with identity-based policies and resource-based policies to secure access in your AWS environment.
This feature is available in all AWS Regions where AWS DataSync is available. For more information about FIPS 140-3 at AWS, visit FIPS 140-3 Compliance. To learn more about VPC endpoint policies for AWS DataSync, see the AWS DataSync User Guide.
Categories: general:products/aws-govcloud-us,general:products/aws-datasync,marketing:marchitecture/migration
Source: Amazon Web Services
Latest Posts
- Find your files quickly and easily on Word, Excel and PowerPoint App home pages [MC1249435]
- Retirement of the Semi-Annual Enterprise Channel option in the Office Deployment Service [MC1249427]
- Microsoft Purview compliance portal: Data Security Investigations introduces new soft purge mitigation action [MC1249429]
- Microsoft Teams: Live transcription in Teams Rooms on Android [MC1249432]
![(Updated) Multiple account access to Copilot in Microsoft 365 desktop and mobile apps [MC981462]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-olly-3779524-150x150.webp "(Updated) Multiple account access to Copilot in Microsoft 365 desktop and mobile apps [MC981462] 6")
