To show you what I mean, let's experiment with a more complex stack using a template that comes from the AWS documentation samples. But how you're expected to get that information through the CLI might, at first, not appear so obvious. If you do choose to go with the AWS CLI – something I highly recommend – you'll need a way to gather key information about other account resources. You may also know that you can mange your CloudFormation stacks both through the AWS Management Console and, as I discuss in my new Pluralsight course, Create and Manage Stacks with AWS CloudFormation Using the Command Line Interface, using the AWS CLI. The CloudFormation templates that define those stacks can be shared, edited, and launched anywhere, giving you predictable and reliable cloud application environments wherever and whenever you need them. You may already know that Amazon's CloudFormation service exists to let you manage your application infrastructure by organising it into stacks of your AWS account resources. With that, we'll all set to get down to work in the next clip. Just to confirm it all worked, I'll list all the S3 buckets in my account. The format won't be an issue so I'll leave it as default. If you like you can then choose a default AWS region and output format. With your credentials in hand, you can run "aws configure." You'll be prompted to enter your access key ID and the secret key itself. You access the security credentials page from the drop-down account menu at the top of any page on the console. I'm sure you understand the problem with that. Now, the CLI has a "create-access-key" command that'll generate a new key, but that's only possible once I've authenticated. You see, to authenticate the CLI to your account you'll need a valid access key. The next step will require one quick trip to the management console. I'll run aws -version to confirm everything worked as it was supposed to. That'll create a new directory called aws that'll contain a install script, which I can run using sudo to get admin privileges. To get it done, I'll paste the curl command from the Amazon page into my Linux shell that'll download the package and write it to a local zip file, which I'll then unzip. I'm working with Linux so that's where I'd head next. Right now they're pushing us towards version 2 of the CLI and I haven't seen any reason not to go along. The best way to get it done is to head over to the AWS installation guide and follow instructions for your OS. Installing the AWS CLI is actually quite simple. How to get exactly the account and environment information you need to manage your AWS account using just the AWS CLI
0 kommentar(er)
