More Info:

S3 buckets should use DNS-compliant bucket names in order to adhere to AWS best practices and to benefit from the new S3 features such as S3 Transfer Acceleration, to benefit from operational improvements and to receive support for virtual-host style access to buckets.

Risk Level

Low

Address

Operational Maturity, Security

Compliance Standards

CBP

Triage and Remediation

Remediation

Sure, here are the step-by-step instructions to remediate the misconfiguration in AWS:

  1. Log in to your AWS Management Console.
  2. Navigate to the S3 service.
  3. Select the bucket that is non-compliant with DNS naming conventions.
  4. Click on the “Properties” tab.
  5. Scroll down to the “Static Website Hosting” section.
  6. In the “Static website hosting” section, click on the “Edit” button.
  7. In the “Edit static website hosting” dialog box, select the “Use this bucket to host a website” checkbox.
  8. In the “Index document” field, enter a valid index document name (e.g. index.html).
  9. In the “Error document” field, enter a valid error document name (e.g. error.html).
  10. Click on the “Save changes” button.

Once you have completed the above steps, your S3 bucket will be compliant with DNS naming conventions. It is important to note that you should choose a bucket name that is unique, easy to remember and relevant to your organization.

Additional Reading: