archive-gh-me/serverless
1
0
Fork 0
mirror of https://github.com/serverless/serverless.git synced 2026-02-01 16:07:28 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #4525 from serverless/add-tip-resource-names

Browse Source 
Added hint to docs on how to determine generated resource names easily
This commit is contained in:
Takahiro Horike 2017-12-05 21:02:57 +09:00 committed by GitHub
commit abad61876e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/providers/aws/guide/resources.md
View File

@ -63,6 +63,9 @@ All resource names that are deployed by Serverless have to follow this naming sc
We're also using the term `normalizedName` or similar terms in this guide. This means dropping any characters that aren't allowed in resources names, e.g. special characters.
_Tip:_
If you are unsure how a resource is named, that you want to reference from your custom resources, you can issue a `serverless package`. This will create the CloudFormation template for your service in the `.serverless` folder (it is named `cloudformation-template-update-stack.json`). Just open the file and check for the generated resource name.
| AWS Resource | Name Template | Example |
|--- |--- | --- |
| S3::Bucket | S3Bucket{normalizedBucketName} | S3BucketMybucket |