> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/networking/cloud-provided-services.md). # Cloud-provided services You can run almost anything you need directly in your Release-managed Kubernetes cluster. But sometimes you'll also want to integrate with other cloud services that are not within the cluster, such as database services (RDS, CloudSQL), data stores (Elasticache, Memorystore), data analytics solutions (Redshift, BigQuery), and others. To allow your Release clusters to communicate with other cloud services, you need to: * Ensure that the other services are running in the same VPC as your Release clusters. * Ensure that you have the correct security groups (AWS) or firewall rules (GCP) set up. This means that any customer or public traffic will enter your VPC through your ingress, and your software running in your cluster will be able to connect to other services, as shown in the diagram below. ![diagram showing ingress and security group](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-3306599175e67a649b40c1da112a8a0145431633%2Fcloud-native-diagram.png?alt=media\&token=e8744ffc-309c-4b5d-a5c2-3f64263fd618) ## Find the correct AWS security group and assign it to new cloud services When Release creates a new node group in your AWS account, it also creates a default security group that all nodes in that group belong to. You can find this security group using the following steps: * Log in to your Release account and navigate to the Cluster Info page. * Note the context, node group name, and region of your cluster. You can see where to find the cluster context and node group name in the image below. ![Get cluster and node group name](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-6fb91eee5712fa17649377f08f7a79276571f54e%2Fflask-rds-cluster-nodegroup-name.png?alt=media) Log in to your AWS console, and: * Navigate to the EC2 dashboard for the same region as your cluster. * Use the cluster context and node group name to find a worker node. * Go to **Actions** -> **Security** -> **Change security groups** and look for the security group that also contains the cluster context. You can see an example of a worker node and how to navigate to the security groups in the image below. ![Finding the security group](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-f511969e17baafb311de11af8373a5c954331719%2Fflask-rds-get-security-group-ec2.png?alt=media) ## Create a new cloud service When you create a new cloud service, you need to: * Set the VPC to the same one used by your Release cluster. * Assign the security group you identified above. Because the security group allows traffic from any services with the same group assigned, the code running in your cluster will be able to connect to these services. ## Create new node groups Note that whenever you create a new node group through Release, all nodes in that group will be assigned to a **new** security group. You'll therefore have to follow these steps and add the new security group to any cloud services each time you create a new node group in Release. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/reference-documentation/networking/cloud-provided-services.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.