Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

349
Views
¿Impacto de migrar a Signature Version 4 en AWS SES donde usamos las credenciales SMTP de AWS SES para enviar correos electrónicos en la aplicación PHP?

Recientemente hemos recibido un correo electrónico de Amazon.

 Hello, Amazon Web Services currently supports Amazon SES API requests that are signed using Signature Version 3 and Signature Version 4 processes. Signature Version 4 further enhances the security around authentication and authorization of Amazon SES customers by using a signing key instead of your secret access key. To improve the security for our customers, beginning October 1, 2020, Amazon Signature Version 3 will be turned off (deprecated) in Amazon SES in favor of Signature Version 4. Amazon SES customers who are still using Signature Version 3 must migrate to Signature Version 4 by September 30, 2020. After that, Amazon SES will only accept requests that are signed using Signature Version 4. For more information, see Signature Version 4 signing process [1]. What Happens if I Don't Make Updates? Requests signed with Signature Version 3 that are made after September 30, 2020 will fail to authenticate with Amazon SES. Requesters will see errors stating that the request must be signed with Signature Version 4. References: [1] https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210

Tenemos varias aplicaciones PHP Codeigniter en las que usamos las credenciales SMTP de Amazon SES para enviar correos electrónicos. no utilizamos la clave de acceso y la clave secreta de AWS para enviar correos electrónicos. Así que asumo que esta migración a Signature Version 4 no afectará nuestra aplicación. ¿Alguien me puede asegurar que si mi suposición es correcta?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

Si está utilizando SMTP para enviar correos electrónicos usando SES, sigv4 no debería afectarlo, es solo para llamadas api sendemail o sendrawemail.

over 4 years ago · Santiago Trujillo Report

0

Si está utilizando las credenciales SES SMTP para enviar correos electrónicos mediante SMTP, es posible que aún se vea afectado. Las credenciales de SES SMTP están firmadas y, antes de febrero de 2019, AWS usaba SignatureV2 al generar credenciales a través de la consola de SES. Una publicación en el foro de un empleado de AWS confirma esto:

Si se refiere a la comunicación enviada a algunos clientes para migrar de las credenciales V2 a las credenciales V4 para Smtp, sí, incluso si no usa el SDK, debe hacerlo.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!