Vous trouverez ici un excellent tutoriel qui explique aussi les rouages internes et les problèmes que vous pourriez rencontrer en essayant de configurer un serveur FTP sur une instance d'Amazon EC2. Il explique également pourquoi l'ouverture du port 21 sur le pare-feu d'Amazon ne fonctionne pas. L'exemple utilise le serveur ftp gratuit filezilla et le client, mais tout peut être utilisé.
http://me-ol-blog.blogspot.com/2011/03/how-to-install-ftp-server-on-amazon-aws.html
Modifié (24 sep-2013):
Parce que les meilleures pratiques de politique stackoverflow dit de ne pas compter sur les liens, j'ai copié les informations de mon blog ici:
Comment installer un serveur FTP sur amazon AWS EC2
This seems to be a big issue as people usually waste a lot of time on this.
The problem lies with 2 elements: the security group settings & the ftp server settings.
FTP is not considered a good solution for passing files between EC2 instances and your computer as it is not firewall "friendly" - you can't just open port 21/TCP on the amazon security group settings because the server is actually sitting on a NAT address and when an ftp client connects to an FTP server using PASV mode then the server tells the client which port and which address to use for the data stream (like directory listing).
If you want an alternate easy solution for transferring files between yourself and the EC2 instance then setup a dropbox on both machines - it doesn't get easier than this... :)
If you still want to set up an FTP server on your EC2 instance then read on...
Typically, people just try to open port 21 and then try to connect and get something similar to:
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Response: 425 Can't open data connection.
The solution is (and for this example I will explain how to perform the setting on FileZilla FTP server on windows):
1. FileZilla FTP server: Edit-> settings -> Passive mode settings:
(x) Retrieve external IP from:
http://ip.filezilla-project.org/ip.php
[ this tells the ftp server to perform a 'whatismyip' and give that to the ftp client, you can also specifically put the address DNS name you use in your remote desktop in the "Use the following IP:", e.g., ec2-6-100-129-60.compute-1.amazonaws.com ]
(x) Use custom port range:
1024-1048
[ these are the ports that will be given to the ftp client - we will open them in the following step in the Firewall ]
2. Amazon security groups: open ports -
a. Custom TCP rule , Port range:21
b. Custom TCP rule, Port range:1024-1048
3. Turn off the windows firewall on the EC2 machine (you don't need it - you have the amazon firewall)
That's it, and just as side note, you don't need to use Elastic IP feature for this to work.
Also don't forget to set your client to use PASV mode (which is typically the default).
You can verify this works by reading the answer the server gives the client when it enters PASV mode:
Command: PASV
Response: 227 Entering Passive Mode (174,149,71,102,4,7)
This response means: "Yo FTP client, use 174.149.71.102 and port 4*256+7=1031"
c'est aider FUL – Arsalan
De plus, comme la question est centrée sur AWS, ne pas oublier ceci: Connectez-vous à la gestion EC2 console, accédez aux groupes de sécurité, sélectionnez le groupe de sécurité auquel appartient votre instance, cliquez sur l'onglet entrant, créez une nouvelle règle TCP personnalisée, autorisez le port 21. Sinon la méthode vidéo ci-dessus ne fonctionnera jamais car le pare-feu Amazon remplacera le pare-feu Windows. – Zeeshan
Et après que je suis bloqué à: 'Statut: \t Le serveur a envoyé la réponse passive avec l'adresse unroutable. En utilisant l'adresse du serveur instead.' 'Commande: \t list' ' Réponse: \t 150 Ouverture données en mode BINARY connection.' 'Réponse: \t 550 canaux de données chronométré out.' ' Erreur: \t Impossible de récupérer le répertoire listing' – Zeeshan