Merge pull request #3787 from geoffreywiseman/master

Avoid Referencing Providers
This commit is contained in:
Philipp Muens 2017-06-13 16:59:39 +01:00 committed by GitHub
commit 427d0df28f
3 changed files with 3 additions and 3 deletions

View File

@ -28,7 +28,7 @@ to review a PR, the faster we can review and merge it.
Examples:
* serverless.yml - Fully functioning to easily deploy changes
* Screenshots - Showing the difference between your output and the master
* AWS CLI commands - To list AWS resources and show that the correct config is in place
* Cloud Configuration - List cloud resources and show that the correct configuration is in place (e.g. AWS CLI commands)
* Other - Anything else that comes to mind to help us evaluate
-->

View File

@ -62,7 +62,7 @@ This example will generate scaffolding for a service with `AWS` as a provider an
will be generated in the current working directory.
Your new service will have a default stage called `dev` and a default region inside that stage called `us-east-1`.
The provider which is used for deployment later on is AWS (Amazon web services).
The provider which is used for deployment later on is AWS (Amazon Web Services).
### Creating a named service in a (new) directory

View File

@ -16,7 +16,7 @@ The Serverless Framework needs access to your cloud provider's account so that i
Here we'll provide setup instructions for different cloud provider accounts. Just pick the one for your provider and follow the steps to get everything in place for Serverless.
At this time, the Serverless Framework supports only Amazon Web Services, but support for other providers is in the works.
This guide is for the Amazon Web Services (AWS) provider, so we'll step through the process of setting up credential for AWS and using them with Serverless.
[Watch the video on setting up credentials](https://www.youtube.com/watch?v=HSd9uYj2LJA)