Hi, Yes, it is possible to build an AWS Cost Explorer source using Airbyte's connector builder. You can use the low-code framework to build a source connector for the AWS Cost Explorer API. Here's an overview of the process: 1. Generate the API key or credentials for the AWS Cost Explorer API. 2. Set up the project on your local machine. 3. Set up your local development environment. 4. Use the connector builder UI to define the connector YAML manifest and test the connector. 5. Specify stream schemas. 6. Add the connector to the Airbyte platform. For a step-by-step tutorial, refer to the [Getting Started tutorial](https://docs.airbyte.com/connector-development/config-based/tutorial/getting-started) or the [video tutorial](). Once you have built the connector, you can export it and make it part of the regular Airbyte connector catalog. Follow the instructions in the [Connector Builder Overview](https://docs.airbyte.com/connector-development/connector-builder-ui/overview) for exporting the connector. Keep in mind that you might need to adapt the process to the specific requirements of the AWS Cost Explorer API. Good luck with building your AWS Cost Explorer source connector!

But this is definitely a valid use case - could you open an issue here: https://github.com/airbytehq/airbyte/issues/new?assignees=&labels=type%2Fenhancement%2Cneeds-triage&projects=&template=6-feature-request.yaml to capture your use case? This will help us prioritizing the feature

You can however use the python cdk to build such a connector with python (it's a more complex process than using the connector builder though): https://docs.airbyte.com/connector-development/cdk-python/