The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Amplify CLI version 5.0.0 includes two major changes:
AWS Amplify CLI now supports IAM permission boundaries to limit Amplify-generated IAM roles. The AWS Amplify CLI is a command line toolchain that helps frontend developers create app backends in the cloud that include IAM roles controlling access to AWS resources. With IAM permissions boundaries, Amplify-generated IAM roles can perform only the actions that are allowed by both the roles’ policies and permissions boundary.
With today’s launch, IT admins can ensure that their developers and Amplify backends have access only to the services that they need. In addition, organizations that require every IAM role to have a permissions boundary assigned can now adopt AWS Amplify CLI. Learn more about how to setup IAM permissions boundaries for Amplify-generated IAM roles in the Amplify documentation.
Amplify has updated the way Lambda layer versions are managed with Amplify CLI version 5.0.0. Amplify CLI enables you to configure Lambda layers to pull common code & assets for your Lambda functions into a centralized location.
In order to take advantage of the newest features and bug fixes, a one-way migration is required for layers created with an older Amplify CLI version. All developers working on a common Amplify project and any CI/CD pipelines should upgrade to the latest version of Amplify CLI.
Any update to an existing Lambda layer triggers a migration for that layer upon amplify push
. Once the layers are migrated, the layers CANNOT be used with Amplify CLI below version 5.0.0.
Starting with the Amplify CLI version 5.0.0 and above, the following changes are coming to Lambda layers:
package.json
or Pipfile
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
amplify push
(#7174) (d28dd1c)amplify push
(#7174)" (#7306) (78854eb), closes #7174 #7306
amplify push
(#7174) (d28dd1c)amplify push
(#7174)" (#7306) (78854eb), closes #7174 #7306
amplify push
(#7174) (d28dd1c)amplify push
(#7174)" (#7306) (78854eb), closes #7174 #7306
amplify push
(#7174) (d28dd1c)amplify push
(#7174)" (#7306) (78854eb), closes #7174 #7306
amplify push
(#7174) (d28dd1c)amplify push
(#7174)" (#7306) (78854eb), closes #7174 #7306
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
This release introduces S3 Server-Side-Encryption by default for all S3 buckets created by the CLI. This has no impact on putting and getting objects from the buckets so there is no impact to existing applications. It does require the s3:PutEncryptionConfiguration
permission on the IAM Role / User used to deploy with the CLI.
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by aws-amplify-ops over 3 years ago
Published by edwardfoyle over 3 years ago
Published by edwardfoyle over 3 years ago
Published by edwardfoyle over 3 years ago
Published by edwardfoyle over 3 years ago