Commit Graph

24 Commits

Author SHA1 Message Date
Thordur Bjornsson
f3a86114ae Fixup aws_security_group doc example.
Both to_ and from_ port must be zero to use protocol -1.
2015-06-03 11:02:16 +02:00
ketzacoatl
addb43deae Correct to_port in egress example
When using `-1` for the protocol, both `from_port` and `to_port` must be `0`, or so says AWS thru Terraform:

```
* from_port (0) and to_port (65535) must both be 0 to use the the 'ALL' "-1" protocol!
```
2015-05-28 21:37:46 -04:00
Paul Hinze
f0e6d0f97e docs: fix cidr_block on aws SG egress
fixes #1936
2015-05-13 18:41:41 -05:00
Clint Shryock
70984526a4 Merge remote-tracking branch 'ctiwald/ct/fix-protocol-problem'
* ctiwald/ct/fix-protocol-problem:
  aws: Document the odd protocol = "-1" behavior in security groups.
  aws: Fixup structure_test to handle new expandIPPerms behavior.
  aws: Add security group acceptance tests for protocol -1 fixes.
  aws: error on expndIPPerms(...) if our ports and protocol conflict.
2015-05-07 17:13:21 -05:00
Josh Bleecher Snyder
fa2e89a381 website: update aws security description docs 2015-05-06 10:08:30 -07:00
Clint Shryock
885efa0837 provider/aws: Add Security Group Rule as a top level resource
- document conflict with sg rules and sg in-line rules
- for this to work, ingress rules need to be computed
2015-05-05 16:56:39 -05:00
Clint Shryock
e9b08cf31f revert the required part 2015-05-05 16:23:26 -05:00
Clint Shryock
b145ce88b7 Document Egress+VPC change, update link 2015-05-05 16:23:26 -05:00
Christopher Tiwald
2526379cf0 aws: Document the odd protocol = "-1" behavior in security groups. 2015-05-05 00:04:21 -04:00
Thomas Lovett
baf1625485 security_groups field expects a list of Security Group Group Names, not IDs 2015-04-13 14:23:11 -05:00
Paul Hinze
de3735bd6f docs: move aws SG tags from rules to resource
fixes #1479
2015-04-10 14:29:31 -05:00
Daisuke Fujita
236d3af646 Remove owner_id argument from document 2015-04-07 16:16:04 +09:00
Michael H. Oshita
1979d9b792 fix indent
align indentation with the rest of the code.
2015-03-19 03:45:32 +09:00
Kevin Yi
0e3f1a865e protocol value for all traffic should be -1
If it is all traffic instead of all tcp traffic , protocol should be equal -1 , otherwise indicate all tcp not all traffic
2015-03-03 10:33:54 +11:00
nevins-b
b7238ca6f2 adding documentation 2015-02-17 13:23:10 -05:00
Mitchell Hashimoto
577e2420b0 Revert "docs: consistent use of array configuration syntax"
This reverts commit 4893eb8b55.
2015-01-14 09:28:25 -08:00
Emil Hessman
4893eb8b55 docs: consistent use of array configuration syntax
The Terraform configuration syntax defines what arrays are.
Use the word array consistently throughout the documentation
instead of list.

The corresponding JSON datatype is called array as well, and
since the Terraform configuration syntax is interoperable with
JSON it makes sense to use the term array to describe them.
2015-01-13 06:59:12 +01:00
Armon Dadgar
38697d6b4c aws: Making security group ingress rules optional 2014-12-07 23:52:04 -08:00
Seth Vargo
073a0f76c5 Add meta descriptions to all pages 2014-10-21 23:21:56 -04:00
Long Nguyen
eef3197ba0 Added security group tagging 2014-10-14 17:11:09 -04:00
Mitchell Hashimoto
dbc890e401 providers/aws: add self to ingress [GH-219] 2014-09-30 14:19:16 -07:00
Hector Castro
1420e261d7 Add required description attribute to aws_security_group example. 2014-08-02 22:41:00 -04:00
Jack Pearkes
9c02e41e73 website: document security group description requirement 2014-07-30 17:59:09 -04:00
Armon Dadgar
e4ff3e7d13 website: Docs for VPC, subnet, sec group 2014-07-23 16:32:33 -04:00