Friday, January 8, 2021

2 common cloud computing predictions for 2021 are wrong

For some reason I’m on the list of every PR firm with a client that needs to have its predictions for the upcoming year heard. Mostly their guesses are obvious and unhelpful, such as “cloud computing will continue to grow” or “cloud security will continue to be a concern.” People are really going out on a limb.

However, I see a few predictions over and over again. I suspect that many out there in the cloud computing market are beginning to believe them, so I need to point out some realities that are often overlooked or misunderstood.

The rise of multicloud to become “cloud agnostic” is the most common—and most concerning—prediction. I especially worry if the perceived benefit is that being cloud agnostic refers to environments that are capable of operating with any public cloud provider with minimal disruptions to a business.

To read this article in full, please click here

Thursday, January 7, 2021

New – AWS Transfer Family support for Amazon Elastic File System

AWS Transfer Family provides fully managed Secure File Transfer Protocol (SFTP), File Transfer Protocol (FTP) over TLS, and FTP support for Amazon Simple Storage Service (S3), enabling you to seamlessly migrate your file transfer workflows to AWS.

Today I am happy to announce AWS Transfer Family now also supports file transfers to Amazon Elastic File System (EFS) file systems as well as Amazon S3. This feature enables you to easily and securely provide your business partners access to files stored in Amazon EFS file systems. With this launch, you now have the option to store the transferred files in a fully managed file system and reduce your operational burden, while preserving your existing workflows that use SFTP, FTPS, or FTP protocols.

Amazon EFS file systems are accessible within your Amazon Virtual Private Cloud (VPC) and VPC connected environments. With this launch, you can securely enable third parties such as your vendors, partners, or customers to access your files over the supported protocols at scale globally, without needing to manage any infrastructure. When you select Amazon EFS as the data store for your AWS Transfer Family server, the transferred files are readily available to your business-critical applications running on Amazon Elastic Compute Cloud (EC2), as well as to containerized and serverless applications run using AWS services such as Amazon Elastic Container Service (ECS), Amazon Elastic Kubernetes Service (EKS), AWS Fargate, and AWS Lambda.

Using Amazon EFS – Getting Started
To get started in your existing Amazon EFS file system, make sure the POSIX identities you assign for your SFTP/FTPS/FTP users are owners of the files and directories you want to provide access to. You will provide access to that Amazon EFS file system through a resource-based policy. Your role also needs to establish a trust relationship. This trust relationship allows AWS Transfer Family to assume the AWS Identity and Access Management (IAM) role to access your bucket so that it can service your users’ file transfer requests.

You will also need to make sure you have created a mount target for your file system. In the example below, the home directory is owned by userid 1234 and groupid 5678.

$ mkdir home/myname
$ chown 1234:5678 home/myname

When you create a server in the AWS Transfer Family console, select Amazon EFS as your storage service in the Step 4 section Choose a domain.

When the server is enabled and in an online state, you can add users to your server. On the Servers page, select the check box of the server that you want to add a user to and choose Add user.

In the User configuration section, you can specify the username, uid (e.g. 1234), gid (e.g 5678), IAM role, and Amazon EFS file system as user’s home directory. You can optionally specify a directory within the file system which will be the user’s landing directory. You use a service-managed identity type – SSH keys. If you want to use password type, you can use a custom option with AWS Secrets Manager.

Amazon EFS uses POSIX IDs which consist of an operating system user id, group id, and secondary group id to control access to a file system. When setting up your user, you can specify the username, user’s POSIX configuration, and an IAM role to access the EFS file system. To learn more about configuring ownership of sub-directories in EFS, visit the documentation.

Once the users have been configured, you can transfer files using the AWS Transfer Family service by specifying the transfer operation in a client. When your user authenticates successfully using their file transfer client, it will be placed directly within the specified home directory, or root of the specified EFS file system.

$ sftp myname@my-efs-server.example.com

sftp> cd /fs-23456789/home/myname
sftp> ls -l
-rw-r--r-- 1 3486 1234 5678 Jan 04 14:59 my-file.txt
sftp> put my-newfile.txt
sftp> ls -l
-rw-r--r-- 1 3486 1234 5678 Jan 04 14:59 my-file.txt
-rw-r--r-- 1 1002 1234 5678 Jan 04 15:22 my-newfile.txt

Most of SFTP/FTPS/FTP commands are supported in the new EFS file system. You can refer to a list of available commands for FTP and FTPS clients in the documentation.

Command Amazon S3 Amazon EFS
cd Supported Supported
ls/dir Supported Supported
pwd Supported Supported
put Supported Supported
get Supported Supported including resolving symlinks
rename Supported (only file) Supported (file or folder)
chown Not supported Supported (root only)
chmod Not supported Supported (root only)
chgrp Not supported Supported (root or owner only)
ln -s Not supported Not supported
mkdir Supported Supported
rm Supported Supported
rmdir Supported (non-empty folders only) Supported
chmtime Not Supported Supported

You can use Amazon CloudWatch to track your users’ activity for file creation, update, delete, read operations, and metrics for data uploaded and downloaded using your server. To learn more on how to enable CloudWatch logging, visit the documentation.

Available Now
AWS Transfer Family support for Amazon EFS file systems is available in all AWS Regions where AWS Transfer Family is available. There are no additional AWS Transfer Family charges for using Amazon EFS as the storage backend. With Amazon EFS storage, you pay only for what you use. There is no need to provision storage in advance and there are no minimum commitments or up-front fees.

To learn more, take a look at the FAQs and the documentation. Please send feedback to the AWS forum for AWS Transfer Family or through your usual AWS support contacts.

Learn all the details about AWS Transfer Family to access Amazon EFS file systems and get started today.

Channy;

Via AWS News Blog https://ift.tt/1EusYcK

Wednesday, January 6, 2021

The shape of edge computing in 2021

In 2019 and 2020, edge computing received a lot of attention because most centralized cloud computing challenges involve latency issues that are difficult to mediate. You can tell the cloud providers to build points of presence closer to your users—and new points of presence continue to show up all the time and all over the world—but latency continues to be a common problem. Why?

A better question is, what’s not happening? New edge computing projects tend to stick processing and data collection closer to the sources and users of the data. However, architects need to do so in a way that is scalable and manageable. Operated individually, the number of edge systems under management will have a clear tipping point where operations and security can not keep up with the complexity of thousands of edge-based systems. The focus must shift from operating each edge-based system individually to setting up management and configuration systems for the whole. 

To read this article in full, please click here

Tuesday, January 5, 2021

The shape of edge computing in 2021

In 2019 and 2020, edge computing received a lot of attention because most centralized cloud computing challenges involve latency issues that are difficult to mediate. You can tell the cloud providers to build points of presence closer to your users—and new points of presence continue to show up all the time and all over the world—but latency continues to be a common problem. Why?

A better question is, what’s not happening? New edge computing projects tend to stick processing and data collection closer to the sources and users of the data. However, architects need to do so in a way that is scalable and manageable. Operated individually, the number of edge systems under management will have a clear tipping point where operations and security can not keep up with the complexity of thousands of edge-based systems. The focus must shift from operating each edge-based system individually to setting up management and configuration systems for the whole. 

To read this article in full, please click here

Tuesday, December 29, 2020

My 2021 cloud computing New Year’s resolutions

Typical New Year’s resolutions focus on personal and professional development—ways to improve. Although I certainly have personal goals of no interest to anyone but myself, I also have some related to the cloud computing profession. I’ll share them in hopes that a few of you will adopt these efforts as well. 

Teach more people about cloud computing. If you have followed me for some time, you understand that I have a passion for education. However, rather than focus on a traditional educational path where most of what you learn is useless, concentrate on specific cloud skills that are very marketable right now, such as storage, architecture, cloud-native databases, security, etc.  

To read this article in full, please click here