Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
How to configure CloudPoint to use IAM roles
How you configure CloudPoint to use AWS IAM roles depends on how you deploy CloudPoint in the AWS cloud:
If you deploy CloudPoint manually using the Docker image on an EC2 instance, then you must create an IAM role, assign the role with the permissions required by CloudPoint, and then manually attach that role to the CloudPoint instance. After attaching the role, you then configure the AWS plug-in.
If you deploy CloudPoint using the CloudFormation Template (CFT), then you specify the IAM role details as an input parameter in the CFT form. The CFT attaches the IAM role to the CloudPoint instance and configures the Source Account automatically as part of the template-based deployment workflow.
You can either specify an existing IAM role or have the CFT template create a new IAM role for you. If you specify an existing IAM role, you must ensure that the IAM role has all the permissions that are required by CloudPoint. If you do not specify an IAM role in the CFT form, the CFT creates a new IAM role, assigns it with all the permissions that are required by CloudPoint, and then attaches that role to the CloudPoint instance.
If you are upgrading CloudPoint from an older release that did not support IAM roles, the existing key pair-based configuration will continue to work as is even after the upgrade. However, you cannot update the secret key access key pair after the upgrade. If you wish to make any changes to the plug-in configuration, you first create an IAM role that maps to the same AWS user account that was used to create the secret key and access key pair, and then use that IAM role to update the configuration.