iSharkFly-Docs/Packer-Cn
2
0
Fork 0
mirror of https://github.com/hashicorp/packer.git synced 2026-09-22 07:51:39 -04:00
Code Issues Packages Projects Releases Wiki Activity

upate standalone docs examples in amazon index file

Browse Source
This commit is contained in:
Megan Marsh
2020-07-17 13:59:51 -07:00
parent 51bc7da964
commit 19089bd074
1 changed files with 38 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/pages/docs/builders/amazon/index.mdx
+38 -4
View File
@@ -67,15 +67,32 @@ explained below:
Static credentials can be provided in the form of an access key id and secret.
These look like:
<Tabs>
<Tab heading="JSON">
```json
{
"builders": {
"type": "amazon-ebs"
"access_key": "AKIAIOSFODNN7EXAMPLE",
"secret_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",
"region": "us-east-1",
"type": "amazon-ebs"
}
```
</Tab>
<Tab heading="HCL2">
```hcl
source "amazon-ebs" "basic-example" {
access_key = "AKIAIOSFODNN7EXAMPLE"
secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
region = "us-east-1"
}
```
</Tab>
</Tabs>
### Environment variables
You can provide your credentials via the `AWS_ACCESS_KEY_ID` and
@@ -110,14 +127,31 @@ The format for the credentials file is like so
You may also configure the profile to use by setting the `profile`
configuration option, or setting the `AWS_PROFILE` environment variable:
<Tabs>
<Tab heading="JSON">
```json
{
"builders": {
"type": "amazon-ebs"
"profile": "customprofile",
"region": "us-east-1",
"type": "amazon-ebs"
}
```
</Tab>
<Tab heading="HCL2">
```hcl
source "amazon-ebs" "basic-example" {
profile = "customprofile"
region = "us-east-1"
}
```
</Tab>
</Tabs>
### IAM Task or Instance Role
Finally, Packer will use credentials provided by the task's or instance's IAM