Hmm, I don't know enough to give you a confident answer yet. The extracts provided do not contain specific information about the behavior of the Settings tab in an Airbyte workspace created using Terraform. However, it's worth noting that when you sign up for Airbyte Cloud, a workspace is automatically created where you are the only user with access. This workspace is a grouping of sources, destinations, connections, and other configurations. It's possible that the Terraform module you used to create the workspace may not have included these configurations, hence why you're only seeing the Account setting. For more detailed information, I recommend checking the [Terraform Documentation](https://docs.airbyte.com/terraform-documentation) or the guide for [getting started with Airbyte's Terraform provider](https://reference.airbyte.com/reference/using-the-terraform-provider).

I'm sorry, but it seems like there's been a misunderstanding. The text "ab118eb0-7746-48ae-8814-d796d1b596cc" appears to be a UUID (Universally Unique Identifier), but it's not clear what your question or request is. Could you please provide more context or clarify your question? I'm here to help with any questions or issues related to Airbyte.

Based on the information provided in the extracts, the Terraform provider for Airbyte is available for users on Airbyte Cloud, OSS & Self-Managed Enterprise. However, the extracts do not provide specific details on how to use Terraform for deploying Airbyte OSS on a GCP VM. For deploying Airbyte on a GCP Compute Engine instance, the [documentation](https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine) provides a step-by-step guide. This includes setting up the environment, installing and launching Airbyte, and connecting it to the GCP instance. The instructions have been tested on a

Debian GNU/Linux 10

VM instance. However, if you're specifically looking to use Terraform for this deployment, the provided extracts do not contain the necessary information. I recommend checking the [Terraform Documentation](https://docs.airbyte.com/terraform-documentation) or the guide for [getting started with Airbyte's Terraform provider](https://reference.airbyte.com/reference/using-the-terraform-provider) for more detailed information. If you encounter any issues, you can reach out to the Airbyte community on [Slack](https://slack.airbyte.com/) for support.

@kapa.ai Why I am getting the error

{
  "type": "about:blank",
  "status": 404
}

when trying to access the host:80006?

The error message you're seeing typically indicates that the server could not find the requested resource. In the context of Airbyte, this could mean that the server running on

host:8000

is not available or not properly set up. Based on the information provided in the extracts, it's important to note that Airbyte's default port is

8000

, not

80006

. If you're trying to access Airbyte's web application, you should be able to do so by navigating to

<http://localhost:8000>

in your browser, as mentioned in the [tutorial](https://airbyte.com/tutorials/extract-data-from-the-webflow-api). If you're still encountering issues, it might be due to a problem with your Airbyte deployment or network configuration. You may want to check the status of your Airbyte services, ensure that the correct ports are exposed and not blocked by any firewalls, and verify that your Airbyte instance is correctly configured and running.

@Nguyen Dao (Bach) That's a great question, but unfortunately I am only capable of responding to a maximum of five questions per thread. Don't hesitate to create a new thread for any further questions you have though. I'm here to help!

@Nguyen Dao (Bach) That's a great question, but unfortunately I am only capable of responding to a maximum of five questions per thread. Don't hesitate to create a new thread for any further questions you have though. I'm here to help!