AWS Provisioning enables you to create AWS services from within POS. These services include:
- An IAM account for the organization.
- An S3 bucket for media file storage.
- A CloudFront distribution for accessing media files.
Provisioning needs to be done only once for an organization. The Setup Guide makes it easy to perform this provisioning; however, if you know AWS is already provisioned, you can skip this step.
The provisioning details are handled by POS. You only need to enter a few fields within this page to provision the services:
You can skip provisioning (e.g. during setup) if you know that provisioning has already been performed.
However, it is not a problem to run provisioning multiple times.
Access Key ID & Secret
These values are the AWS access credentials for a Fusion administrator account. The credentials are not the organization credentials, and must require higher permission levels given that the process will create and configure various AWS services.
The Fusion administrator credentials are used only during the provisioning process, and are not stored.
Select the AWS Region where AWS services should be provisioned for the tenant.
The region should be the same as the EC2 and RDS instances that hosts the client’s cloud tenant and database.
Alternate S3 Bucket
This field is optional, and should not be used unless necessary. It can be used to specify a non-standard name for the S3 bucket name that is created.
The auto-generated name follows the format fusion-rms-orgid (e.g. fusion-rms-xmsqa1), based on the organization ID
As S3 bucket names are global across all AWS customers, there is a chance that the auto-generated name will already be used by another AWS customer. You can use the AltBucketName to work around the conflict.
After provisioning runs, it may take a few minutes to build the CloudFront distribution.
You can view the creation status – and generated domain name – by reviewing the distribution using the AWS Console web UI at https://console.aws.amazon.com/cloudfront/home.