# Use S3 as data source 2022

**URL:** https://discourse.greatexpectations.io/t/use-s3-as-data-source-2022/1137
**Category:** Archive
**Tags:** help-wanted
**Created:** [November 10, 2022, 1:09am UTC](https://discourse.greatexpectations.io/t/use-s3-as-data-source-2022/1137 "2022-11-10T01:09:05Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ncastrog](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@ncastrog](https://discourse.greatexpectations.io/u/ncastrog)
#### Post date: [November 10, 2022, 1:09am UTC](https://discourse.greatexpectations.io/t/use-s3-as-data-source-2022/1137/1 "2022-11-10T01:09:05Z")

</div>

I have problems to connect to our AWS S3 bucket.

I have followed the manual and have this configuration file

```auto
enaible_yaml = f"""
name: enaible_s3_datasource
class_name: Datasource
execution_engine:
    class_name: PandasExecutionEngine
data_connectors:
    default_runtime_data_connector_name:
        class_name: RuntimeDataConnector
        batch_identifiers:
            - default_identifier_name
    default_inferred_data_connector_name:
        class_name: InferredAssetS3DataConnector
        bucket: enaible-public-data
        prefix: data_quality/final
        default_regex:
          pattern: (.*)/(.*)\.parquet
          group_names:
            - prefix
            - data_asset_name
"""
print(example_yaml)

```

But get this error when I test the yaml file.

```auto
ValueError: S3 query may not have been configured correctly.

```

I need to load parquet files also rather than csv.  
great\_expectations, version 0.15.29

Any enlightenment will be appreciated.

Thanks in advance

---

<div class="post-metadata">

### Author: ![c\_m](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@c\_m](https://discourse.greatexpectations.io/u/c_m)
#### Post date: [November 16, 2022, 5:12pm UTC](https://discourse.greatexpectations.io/t/use-s3-as-data-source-2022/1137/2 "2022-11-16T17:12:47Z")

</div>

I can’t offer a solution but have you tried testing this against a newly created empty S3 bucket?

See: [great\_expectations/util.py at 5c21d539dd5f280fa0afb55a506b1e51d871bfbf · great-expectations/great\_expectations · GitHub](https://github.com/great-expectations/great_expectations/blob/5c21d539dd5f280fa0afb55a506b1e51d871bfbf/great_expectations/datasource/data_connector/util.py#L462)

which seems to indicate that the S3 bucket might be misconfigured. I successfully connected to an S3 bucket with the same configuration to yours with no error with GE 0.15.32