Hi Leo, thanks for getting in touch. There are several reasons why this might be working out for you and we have actually changed our recommendations to no longer include using the AWS account ID to grant access. Details are available in this changelog item: https://devcenter.heroku.com/changelog-items/353
If you still have questions about this (and I realize it's been a year since you posted this), then feel free to get in touch with Heroku support: https://help.heroku.com/ Michael On Tuesday, December 7, 2010 3:24:41 PM UTC-8, sslguy wrote: > > I'm trying to open up my Amazon Ec2 security group so that Heroku apps > can access some mysql servers in our EC2 account > > I've looked around and determine that this is the command that is > recommended: > > ec2-authorize default -P tcp -p 3306 -u 098166147350 -o default > > This command from what I understand instructs EC2 to let the default > security group owned by Heroku to have access to tcp port 3306 in our > default EC2 group. > > However, it's just not working. I see the command has executed > correctly and the Heroku account 098166147350 appears to have > permission. However, the data connection is not being established. But > when I temporarily open the port to everyone for a few minutes, the > connection can occur so I know it's not the app settings. Is there an > update Heroku accnt number? Or has someone found another way? > > Thanks. > > Leo -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
