Deployment Methods

Available Deployment Methods

• AWS Elastic Container Service (ECS) Task
• Google Cloud Scheduled Function
• Docker Deployment Methods
• Kubernetes Deployment Method
• Local Deployment

Picking a Deployment Method

After successfully completing Provider Setup, choose a deployment method to run the cloud connector on a schedule.

The Censys Unified Cloud Connector can be deployed in a variety of ways. The following table provides a high-level overview of the different deployment methods available.

Deployment Method	Description	Pros	Cons
AWS ECS Task	Run the connector in an AWS ECS Task.	- Easy to deploy and maintain. - Leverage the power of AWS ECS. - Can be deployed to AWS.	- Requires an AWS account. - Requires the providers.yml file and the secrets directory to be stored in AWS Secrets Manager.
Google Scheduled Function	Run the connector in a Google Scheduled Function.	- Easy to deploy and maintain. - Leverage the power of Google Cloud Functions. - Can be deployed to Google Cloud.	- Requires a Google Cloud account. - Requires the providers.yml file and the secrets directory to be stored in Google Secret Manager.
Docker	Run the connector in a Docker container.	- Easily deployable on any server with Docker installed.	- Requires Docker to be installed on the server. - Requires the providers.yml file and the secrets directory to be mounted as volumes.
Kubernetes	Run the connector in a Kubernetes cluster.	- Leverage the power of Kubernetes CronJobs. - Can be deployed to a variety of cloud providers.	- Requires a Kubernetes cluster to be deployed.
Local Deployment	Run the connector in a local environment.	- Good for testing. - Doesn’t require external infrastructure.	- Not scalable. - Doesn’t make use of IaaS best practices.

Confirm Results

Visit the Seed Data Page and the Storage Buckets Page to confirm that you’re seeing seeds and storage buckets from your cloud provider(s).