This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"Statement": [ | |
{ | |
"Sid": "PackerSecurityGroupAccess", | |
"Action": [ | |
"ec2:CreateSecurityGroup", | |
"ec2:DeleteSecurityGroup", | |
"ec2:DescribeSecurityGroups", | |
"ec2:AuthorizeSecurityGroupIngress", | |
"ec2:RevokeSecurityGroupIngress" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
! -------------------------------------------------------------------------------- | |
! This example configuration shows what WE did to get Amazon VPC working with our | |
! ASAs. We use version 8.3(1). This config has not been reviewed or otherwise | |
! blessed in any way by anyone at Amazon. YMMV. | |
! | |
! It differs from Amazon's supplied config by using two different sets of | |
! crypto maps and ACLs, so it brings both tunnels up simultaneously. | |
! | |
! For the purposes of the example, the physical datacenter network is 172.16.1.0/24 | |
! and the VPC is 10.0.0.0/16. |
NewerOlder