By using AWS re:Post, you agree to the AWS re:Post Terms of Use

Code licenced by Apache 2.0 licence with the AWS SDK for Javascript v3, maybe licenced by other licence ?

0

Hi guys,

Hope you are well. I've got a doubt about the AWS Code licence, specifically I've been using fragments of code from de AWS repository for the Javascript SDK v3 interacting with Cognito. In some fragments of code, for example here: https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-cognito-identity-provider/classes/getusercommand.html

The code licence for the Code is the /**

  • Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
  • SPDX-License-Identifier: Apache-2.0 */

This being said, if I want to use this fragment inside my code (more extensive), maybe I'll have to keep this code license ?, but what if I want to licence all code (the fragment of AWS repository and my own code more extensive) with MIT licence, can I do it ?, but in afirmative response, I have to keep the Apache licence in the fragment, isn't it ?, and for example for all the final code can I put the MIT licence ?.

Any recommendation can help me !! thanks in advance !!

asked a year ago342 views
3 Answers
1
  • Hi, On what you have to do precisely:

    Anyone who uses open source software licensed under Apache 2.0 must include the following in their copy of the code, whether they have modified it or not:

    1. The original copyright notice
    2. A copy of the license itself
    3. If applicable, a statement of any significant changes made to the original code
    4. A copy of the NOTICE file with attribution notes (if the original library has one)

    The third requirement listed above is a major differentiator between the Apache License 2.0 and other permissive licenses. If you make any major modifications to the licensed code, you must disclose those changes in any updated version that you distribute.

    However, you do not need to release the modified code under Apache 2.0. Simply including any modification notifications is enough to comply with the license terms.

  • Still from same FOSSA article

    Using the Licensed Code The Apache License 2.0 outlines what users are allowed to do with the licensed code. Under this license, users can:

    1. Use the code commercially: Companies can include the licensed code in proprietary software that they then sell to customers.
    2. Alter the code: Developers are permitted to make modifications to the original code.
    3. Distribute any copies or modifications of the code: An individual or organization is allowed to copy and/or update the code, then make that version available to others (even commercially).
    4. Sublicense the code: A company can distribute their reworked version of the code under a stronger license.
    5. Use patent claims: Under the terms of the Apache License 2.0, contributors to the code explicitly grant patent rights to users (although experts believe that the language of other permissive licenses also grants such rights).
    6. Place warranty: Users of the open source code can place a warranty on the licensed software. And while there are no restrictions on the code, there are a few caveats to keep in mind. For example, the license states that users cannot hold contributor(s) legally liable for any reason. Also, the license does not grant you any rights to use the trademarks of the licensor.
0

Hi Didier,

Thanks for your reply. I've checked all your links, for here, I undestand that I've to licence my code by Apache license 2.0 of the AWS SDK for Javascript v3 ? and I've to add any change or modified part to my source code. As you see I'm a little confused. What does it mean ? From the links I see we need to include the Apache licence advice (and sometimes a NOTICE file) from AWS and we must include the modifications parts we changed ?. Finally, my question was if I licence the all code by MIT license, but will this require to include also the Apache license from AWS ?. Sorry for the inconvenients in my understanding, for this licenses topics I always make a mess. Can you help me more specifically ? Thanks again !

Greetings.

answered a year ago
0

Hi Didier_AWS,

From your first last answer, I think what you mean, I should include then, the Apache 2.0 license and a statement with any major change. The changes I that I am going to introduce are not very significative, anyway I prefer (if it's possible) to include these changes, but in what way can I do it ?, for example in the same file which include the Apache license from AWS and the modified code ?, between comments lines, or how can I do it ? Finally, if I decide to distribute the code with MIT license, again, in what way, is it enough including the license file called "LICENSE" with my copyright ? and the text of the license ? for example:

"MIT License

Copyright (c) 2023 dcorralf

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation, etc ... "

To sum up, the final project will contains the Apache 2.0 License from AWS with a statement in case we add some changes, and this for each file that uses code from AWS, and finally in the resulting code push to my Github repository, and add the MIT license file ? is that so ?

Well Didier_AWS, step by step following your recommendations, I think I´m understanding the topics of code license, and it's cool and awesome !! Thanks again for your comprehension and understanding.

Greetings.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions