- 27 Dec 2021
- 4 Minutes to read
HOWTO: Configure Feeds for Amazon S3
- Updated on 27 Dec 2021
- 4 Minutes to read
How to Configure a New Feed to use Amazon S3
ProGet can use Amazon's S3 Cloud to store your package files instead of using your server's disk drive. This not only helps ensure you never run out of disk space but simplifies disaster recovery: everything will already be stored on the cloud.
This article will walk you through how to create a S3 bucket and then use it to store packages in a new feed in ProGet
This guide walks through creating a new feed. If you have an existing feed that you would like to migrate to Amazon S3, check out our migrating an existing feed docs.
Step 1: Login or Create an Amazon AWS Account.
Sign up or login to your Amazon AWS account.
Step 2: Create an S3 Bucket
If you already have an S3 Bucket setup, than you can skip this step.
Navigate to the buckets tab inside of Amazon S3. If your having trouble finding it try searching "bucket" in the search bar at the top.
Click on create bucket and fill out the relevant fields. After you finish, you should see your bucket name, region, and access displayed. In this example we have named our bucket "kramerica" and set the region to US East (Ohio) us-east-2.
Step 3: Create Access Key/ Secret Access Key
After setting up your bucket, you will need to create an access and secret access key that will be used in ProGet later. Navigate to the Identity and Access Management (IAM) in AWS or simply click here to go straight to your access keys.
Click the blue botton labeled Create New Access Key and select the blue drop down arrow labeled Show Access Key to see your Access Key and Secret Access Key.
Copy or write down both your Access Key and Secret Access Key as you will need to enter them into ProGet during step 5.
Step 4: Create a New Feed
To create a new feed, navigate to the banner at the top of the page and click on feeds. Next select Create New Feed.
You will then need to select the type of feed you would like to setup. In this guide we will be setting up a NuGet feed, but the steps should be nearly the same for any feed. Select the feed you wish to setup and fill in the relevant fields.
Step 5: Change Your Feed’s Package Store Location
By default ProGet stores packages files on disk, so your feed will need to be configured to instead store packages on Amazon S3. From your feed click on Manage Feed> Storage & Retention and then select change next to Storage.
After clicking change you will be asked to configure your feed package store. Choose Amazon S3 when prompted.
Step 6: Configure Package Store Location to Use Your Amazon S3 Bucket
After selecting Amazon S3 storage as your package store location you will be presented with the following configuration options:
Since we are setting up a NuGet feed to use an Amazon S3 bucket, we will only configure the options necessary for that.
- Access Key & Secret Access Key: Enter the Access key and Secret access key that you created in step 3.
- Region Endpoint: Enter the region endpoint that you setup in step 2. For our example our region endpoint is us-east-2.
- Bucket: Enter the name of the bucket you created. For our example we named the bucket kramerica.
Thats all you need to configure a new feed to use an Amazon S3 bucket! For details on all the configuration options, check out our docs on Cloud Package Stores.
If you are struggling to find something, usually a quick google should suffice, but just in case here's some help with common items users have trouble locating:
- Access key: Your access keys can be found here.
- Region Endpoint: Using the navigation pane on the left side of your screen in Amazon S3 go to Buckets> Bucket Overview> AWS Region.
Issue: Amazon S3 is not a storage option
If you arrived at Step 5 only to discover there was no option to select Amazon S3, most likely the Amazon AWS extension is not installed.
To install the Amazon AWS extension:
- Please click on the gear icon in the banner
- Navigate to Integrations & Extensibility -> Extensions
- Click the Amazon extension under Available Extensions
- Click the "Install"
Error: The package could not be installed
If you get an error that says "The package could not be installed." when trying to add/push a package, this normally indicates that ProGet recieved an error connecting to the Amazon S3 bucket. Please check the following:
- Verify the Access Key and Secret Access Key are properly set from the Identity and Access Management (IAM) console
- Verify the Region Endpoint is correct. (Ex: if your bucket says
US East (Ohio) us-east-2, the value should be
- Verify Bucket is set to the same name as your S3 bucket (In our example we named our Bucket