Skip to main content
AmazonWebServices u/AmazonWebServices avatar

AWS

u/AmazonWebServices

Feed options
Hot
New
Top
View
Card
Compact


AWS Compiled #007 - AWS CLI v2
AWS Compiled #007 - AWS CLI v2
$ git checkout -b AWS_Compiled_007
$ git commit -a -m 'AWS Developer content and news, curated by AWS'
$ git checkout main
$ git merge AWS_Compiled_007

Share your thoughts to better fit your needs by leaving comments or emailing us: aws-developer-newsletter-feedback@amazon.com. You can also find additional developer news here.

TECH SPOTLIGHT

This week's Tech Spotlight is on the AWS CLI v2, which was released earlier this year. The AWS CLI is a unified command line tool that make it easy to interact with the AWS services and APIs. This allows you to easily create, modify, or delete resources in your AWS account. When developing version 2, we focused in making it more interactive per our user feedback. This new version has a few new tricks up its sleeve, like being able to auto-complete server-side resources, allowing a developer to quickly interact with resources with tab-completion such as

aws dynamodb update-table —table-name MyTable<TAB>

No more copy pasting resource names or making typos! There are also in-built wizards that you can use when creating resources, instead of copy/pasting in all the parameters, 

aws dynamodb wizard new-table

There are wizards available for the configure, dynamodb, iam and lambda commands, and a good place to get started using the AWS CLI would be run the configure wizard to help you set up your credentials. Have a look at the configuration quickstart guide. There are few more features for you to explore and use in your daily workflow, we recommend you take a look at this video from last year’s re:Invent session.

Amazon EC2 Metadata API v2

Not everyone is familiar with the metadata API available on each EC2 instance via `http://169.254.169.254/`. This API contains details about the EC2 instance, from the AMI that was used to launch it, the IAM role and even the user data values. This allows for interesting workflows where you read the data after launching the instance to make decisions, like bringing up 4 instances with a single CLI command and using the ami-launch-index value to have the first instance be the primary DB instance, with the 3 subsequent ones be replicas, but with different replication interval. Dig into this example for more details.

Dive Deeper

AWS CLI v2 Changelog
Instance metadata categories


Hello,

I'm sorry to hear your account verification has been unresolved for over a month and that your support cases haven't received correspondence. Send us your case ID via private message, and I'll get this raised to our Support team on your behalf.

- Jabu M.


Hello,

I understand the urgency here. You can send us your case ID via private message, so I can raise this with our Support team.

- Jabu M.


Hello,

I can understand your concern with the unexpected cost jump. I'd recommend opening a billing support case, so our Support team can take a closer look at this for you: http://go.aws/support-center.

- Jabu M.


Hello,

Default quotas assigned to an account can be updated based on factors like regional availability, payment history, and quota increase approvals. You can learn more about Bedrock quotas here: https://go.aws/3QzBwRk.

To get this resolved, submit a service quota increase request through our Support Center: http://go.aws/request-quota-increase.

/- Jabu M.


Hi, sorry to hear you're having trouble completing phone verification for your account. To get this resolved, open a support case directly through our Support Center: http://go.aws/support-center.

- Jabu M.


Hi, this article provides insight on troubleshooting mismatches between your registrar and your Route 53 name servers: https://go.aws/487qMiY.

- Jabu M.