AWS Storage Blog
Tag: AWS Config
Migrate to Amazon S3 account regional namespaces
Since its launch in 2006, Amazon S3 has used a global namespace where bucket names must be unique across all AWS accounts and AWS Regions. This design has served customers well at scale, but organizations managing multiple accounts and environments often encounter naming collisions. When a bucket is deleted, its name returns to the global […]
Enforcing organization-wide Amazon S3 bucket-tagging policies
In today’s complex cloud environments, maintaining consistent resource tagging is a critical challenge faced by organizations of all sizes. Proper resource tagging is essential for cost allocation, security compliance, operational management, and maintaining governance at scale. However, enforcing tagging standards across distributed teams and numerous resources can be difficult, especially when dealing with rapid deployment […]
Prevent IOPS over-provisioning by monitoring striped Amazon EBS volumes within EC2 instance limits
Enterprises are always looking for ways to optimize storage performance to support their performance-intensive applications and workloads. One technique is data striping, which involves segmenting data across multiple storage volumes to aggregate maximum logical capacity and increase performance. The technique is useful for workloads that require high levels of input/output operations per second (IOPS) and/or […]
Validate your disaster recovery solution and simplify compliance reporting on AWS
Data protection is a key element of compliancy, and organizations must deploy controls to manage the protection of their data and handle operational disruptions. With ongoing configuration and resource changes within IT infrastructure, it can be challenging to continuously and efficiently validate, maintain, and report on compliance to ensure that internal policies and regulatory standards […]
Automate Amazon S3 Versioning using AWS Config rules
Different enterprises and organizations have different data compliance requirements and regulations that they must adhere to for legal, security, safety, and best practice reasons. Historically, customers with data in Amazon S3 have manually performed remediation actions on non-compliant buckets. This includes writing and maintaining scripts running on regular intervals to check for non-compliant S3 buckets […]




