Last activity: 13 May 2019 8:29 EDT
Help with creating a repository using an Amazon S3 bucket
I am currently in the process of installing the Pega Deployment Manager and am walking through the steps for doing so. I am at the step where it discusses creating a Repository and the options for doing so. Since we are self hosted, and utilize Amazon for most of our infrastructure needs, it makes the most sense for us to use an S3 bucket to create the repository. In reviewing the documentation, it appears we need 4 pieces of information: The name of the S3 bucket we created, the root path, the access key and the secret key. Upon discussing this with our infrastructure team, they are unsure of a few things:
1. Why do we need the access key and secret key?
2. What purpose do they serve?
3. Is Pega using CLI commands to work with repository or API calls of some sort?
4. It appears that the secret key is really a password field. Is this just the password associated to the access key?
Part of the confusion I think is that since our servers are already in Amazon and these buckets will also be in Amazon why do we need to do this? They feel that they should be able to allow this to happen without the keys since all of this is in the same VPC. We think these keys mean that they need to create a IAM user to allow programmatic access. Is this correct?
What do other people in this circumstance do?
Any help would be appreciated.