📄️ AWS IAM policies
A policy in AWS IAM declares a set of permissions on a specific AWS resource. After creating a policy, you need to attach it to an IAM role or user. As such, the IAM role or user is assigned the permissions declared in the policy to access the specified AWS resource.
📄️ Create a cross-account IAM role
You need to create a cross-account IAM role, which will be referenced in a deployment credential, either from the Cloud settings page in the CelerData Cloud BYOC console before you create a deployment or as part of the workflow of creating a deployment.
📄️ Create a security group
You need to create a security group, which will be referenced in a network configuration, either from the Cloud Settings page in the CelerData Cloud BYOC console before you create a deployment or as part of the workflow of creating a deployment.
📄️ Create a service IAM role for EC2
You need to create a service IAM role for EC2, which will be referenced in a data credential, either from the Cloud settings page in the CelerData Cloud BYOC console before you create a deployment or as part of the workflow of creating a deployment.
📄️ Create a VPC and related resources
You can attach an existing VPC to your deployment or create a new one, either from the Cloud Settings page in the CelerData Cloud BYOC console before you create a deployment or as part of the workflow of creating a deployment.
📄️ Create a VPC endpoint
You can optionally create your own service powered by AWS PrivateLink, known as an endpoint service, to enable direct, secure connectivity between CelerData's VPC and your own VPC.
📄️ Connect to an EC2 instance using SSH
You can connect via SSH to the Amazon EC2 instance that hosts your CelerData cluster.
📄️ View associated AWS Cloud resources
CelerData launches AWS Cloud resources, namely, EC2 instances and placement groups, that you must pay for, during deployment.