1 回答
- 最新
- 投票最多
- 评论最多
0
That sounds like an IAM permission error: You don't have the appropriate permissions to do that - check what permissions have been assigned to you via roles, groups or directly to you as a user.
I'm logged in as root user.
If you're operating in a complex environment where the VPC is shared with you (or you're sharing it with another account) and the EC2 instances isn't in the same account then that's something you might trip across. If you're in a "simple" environment then this is a good time to create a support case as they can look at the resources for you and determine why the association is failing.
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 8 个月前
Hello, I encounter the same behavior.
I explain my context : I deployed an sFTP instance (AWS Transfer Family) and I configured this one to use the VPC integration (endpoint) to allow to have a private ip address. Through my private network I connect well to the private ip of the sFTP server. Now I need to allow to connect to this sFTP server through a public access. So I created an elastic ip and I want to associate this one to the network interface (attached to the VPC endpoint) of the sFTP server.
But the association not work, I encounter the error "An error occurred (AuthFailure) when calling the AssociateAddress operation: You do not have permission to access the specified resource".
I tried with the aws cli command and through the AWS console and I have the same error / behaviour.
If anyone has encountered the same thing and fixed this one, I would be really interested !
My problem came from the configuration of my sFTP Transfer Family instance, I encountered this error because the association between my elastic ip and the network interface must be do at the moment when we change on the sFTP server (AWS Transfer Family) the access from "Internal" to "Internet Facing". At this time you can link the elastic ip to the subnet id.