We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attaching a rule to a security-group involving an sg from a Peering VPC is failing
This works using aws cli:
aws ec2 authorize-security-group-ingress \ --group-id <my-sg-id> \ --protocol tcp \ --port 80 \ --source-group sg-0102a4361b6df7762
But this fails:
aws_security_group("my-sg") do inbound_rules 'sg-0102a4361b6df7762' => 80 end
with the following message Chef::Resource::AwsSecurityGroup[sg-0102a4361b6df7762] does not exist!
Chef::Resource::AwsSecurityGroup[sg-0102a4361b6df7762] does not exist!
sg-0102a4361b6df7762 is setup in a separate AWS VPC for which a Peering Connection has been established
2.1.0
CentOS
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Attaching a rule to a security-group involving an sg from a Peering VPC is failing
This works using aws cli:
But this fails:
with the following message
Chef::Resource::AwsSecurityGroup[sg-0102a4361b6df7762] does not exist!
sg-0102a4361b6df7762 is setup in a separate AWS VPC for which a Peering Connection has been established
Gem Version
2.1.0
Platform Version
CentOS
The text was updated successfully, but these errors were encountered: