Secondary DNS zone on aws route 53

Question

Domain Name System

I have a freebsd 8.2 server running BIND and several zones supported by it.
He has a slave server from the provider, which stores the secondary zones.
There is a domain with which you can play as much as you like.
The question is actually how to transfer the secondary zones from the provider's server to the Amazon's ns server (I suspect that this can be done somehow since there is a route 53 service), I don’t have enough thought to figure out how to do this ...
Theoretically, I imagine it as follows :
go to route 53 - start the necessary zone there, in the zone records we get automatically created 2 records
1) soa record - with the data of the server that stores authoritative information about the domain zone
2) ns record with ns Amazon servers
at the registrar in the admin panel, I specify the delegation of the domain zone to my server with BIND and 4 ns of the Amazon
when adding the zone to BIND, I also specify, in addition to the test A record (will issue a stub upon entry), ns of the Amazon server.
The preparation seems to be completed, now in order for Amazon to receive data from my BIND, we replace the standard soa entry in the route 53 panel with the data from my server, and here I don’t know what to do next, according to BIND’s idea, when updating the zone using notify, I should send data to Amazon servers (serial to bind I change to a larger one compared to the one that was specified when changing the soa record, ip addresses are added to the allowed ones).
In fact, the above action, when requesting data from Amazon ns, I don’t see any additional records other than the standard type=ns records and the soa I changed, I understand that it takes time to update the data and I survived these time frames before writing here.
Maybe someone did something similar? Or, where did I go wrong, please tell me.

Answer 1

At the official forum from a representative on September 14, 2012.

Thanks for all the feedback; we understand that secondary DNS is an important feature for our customers. While we don't support this yet, there are third party tools that can help such route53d: https://code.google.com/p/route53d/
Secondary DNS is on our roadmap, but we don't have any firm dates to share. In the meantime, if you have feedback on how you would want Route 53-specific things such as ALIAS or latency-based routing records to be transferred, it is much appreciated.