ec2.DescribeAddresses() doesn't return expected output

[mattes]

Step 1: Allocate new Elastic IP

    allocateAddressResp, err := c.ec2client.AllocateAddress(&ec2.AllocateAddressInput{
        Domain: aws.String("vpc"),
    })

Go to Web Console and verify that the Elastic IP really has been allocated.

Step 2: Try to "fetch" Elastic IP by Public IP

        describeAddressesResp, err := c.ec2client.DescribeAddresses(
            &ec2.DescribeAddressesInput{
                Filters: []*ec2.Filter{{
                    Name:   aws.String("public-ip"),
                    Values: aws.StringSlice([]string{ip.String()}), // ip is type net.IP and holds returned public IP from Step 1 (double checked this)
                }},
            })

I would expect the Elastic IP to be returned immediately, which actually happens for most of the time. Sometimes it doesn't find the Elastic IP though, although it's definitely shown in the Web Console.

Are results from DescribeAddresses() cached? Why do I have to wait for Elastic IP to be returned by DescribeAddresses() sometimes.

Thanks!

[mattes]

So I guess this problem is unrelated from this SDK, but again, here is what happens:

• Call AWS API to allocate new Elastic IP
• API returns immediately with successful response (always works)
• Now try to query for this (successfully) allocated Elastic IP ...
  • Most of the time, this works.
  • Sometimes it doesn't and AWS pretends not to know anything about this Elastic IP.
    Via the API or even via the Web Console.
    The AWS API will still prevent you from creating Elastic IPs over your limit though.
• Immediately try to allocate a new Elastic IP (always works)

[jasdel]

@mattes when creating the Elastic IP about how much time between when the create call is made and the IP is available are you seeing? Is it on the order of seconds, or minutes?

When performing the second allocate Elastic IP does it return the same IP as the first allocation call, or different?

[jasdel]

@mattes are you still running into the issue where the IP may not be immediately accessible? I think there is a small propagation delay between when an IP is allocated and when it is available. For your code, having retry logic probably will be the best way to to handle this small availability delay.

I'm going to close this issue, but I encourage you to create a post on the EC2 AWS forums if you are still encountering this issue.