Table of Contents
The deployment Elastio is performed in two steps: deploying the Elastio CloudFormation stack and deploying the Cloud Connector. Before starting the deployment, make sure that you have all the required permissions enabled in your AWS account, as well as VPC configurations set up.
Permissions to operate Elastio
During the deployment of the Elastio CloudFormation stack, specific permissions are required for creating the necessary resources for the service, but once the deployment is complete, the Elastio operates based on the principle of least-privilege, meaning only the minimum necessary permissions are required for its operation. All the permissions used to operate Elastio are described here.
Permissions to deploy the Elastio CloudFormation stack
To deploy the Elastio CloudFormation stack, certain permissions are required to create the resources necessary for the Elastio service. These permissions are not used to operate the service, they are used only for the deployment of the service.
To deploy, a user with the following policies attached are needed:
In case the current user lacks any of the permissions, the Elastio CloudFormation deploy might fail, so we recommend extending the permissions or creating a dedicated AWS IAM user to deploy the CFN. The flow of adding a new user and enabling the required permissions is described here.
- Why do I need to deploy this CloudFormation template?
- Why do I need to grant
CAPABILITY_NAMED_IAMwhen deploying Elastio’s CloudFormation template?
- What kind of access to my AWS account does Elastio require?
- How can I audit Elastio’s activity in my account?
- What are the specific Elastio IAM Policies that we use?
- What are the Elastio resources created by the Elastio CFN?