# Problem: Configuration file not found issue
<a name="problem-configuration-file-not-found-issue"></a>

## Resolution
<a name="resolution-config-file-not-found"></a>

When S3 buckets are used for configuration files, you might receive the following error:

 `error | accelerator | ENOENT: no such file or directory, open '/codebuild/output/src437/src/s3/01/accounts-config.yaml'` 

Ensure that the configuration zip file uploaded to the S3 config bucket does not contain a top-level directory. Once the zip file has been unzipped, it should contain the solution configuration `yaml` files and other resource policy related folders at the root. Refer to the [Update the configuration files](step-3.-update-the-configuration-files.md) section for more information about the proper structure of the zip archive configuration files.